From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RIPGk-0006FV-QI for garchives@archives.gentoo.org; Mon, 24 Oct 2011 18:29:06 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2072421C06C; Mon, 24 Oct 2011 18:28:56 +0000 (UTC) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by pigeon.gentoo.org (Postfix) with SMTP id 9BC9921C039 for ; Mon, 24 Oct 2011 18:27:59 +0000 (UTC) Received: (qmail invoked by alias); 24 Oct 2011 18:27:58 -0000 Received: from p5B0820C5.dip.t-dialin.net (EHLO pc.localnet) [91.8.32.197] by mail.gmx.net (mp025) with SMTP; 24 Oct 2011 20:27:58 +0200 X-Authenticated: #13997268 X-Provags-ID: V01U2FsdGVkX1+I0hZTZRaI+mAlbwmA3IVvVK1lVY9dIyOfSBcPtM QD/tmby/9yViJt From: Michael Schreckenbauer To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Kernel Panic fglrx Date: Mon, 24 Oct 2011 20:27:52 +0200 Message-ID: <29994191.oZlcPYoW24@pc> User-Agent: KMail/4.7.2 (Linux/2.6.38-gentoo; KDE/4.7.2; x86_64; ; ) In-Reply-To: <4EA58E41.7000302@gmail.com> References: <4EA577D0.50408@gmail.com> <2405702.c3XAKe8b4k@pc> <4EA58E41.7000302@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Y-GMX-Trusted: 0 X-Archives-Salt: X-Archives-Hash: 9cf656a1daa8ae4ed8c0ac45833f194e Am Montag, 24. Oktober 2011, 18:11:45 schrieb 4k3nd0: > On 10/24/11 17:31, Michael Schreckenbauer wrote: > > Hi, > > > > Am Montag, 24. Oktober 2011, 16:36:00 schrieb 4k3nd0: > >> hi guys, > >> > >> somehow my fglrx is unstable. Got sometime a crashing fglrx that > >> pulling down the hole system. Someone maybe a idea to fix this? > >> > >> http://pastebin.com/izFnWD7N > > > > [fglrx] ASIC hang happened > > > > is a message indicating a deadlock in a compute-kernel (shader, > > GPGPU), which in almost all cases is a userspace bug or the timeout > > in fglrx is too low for the kernel in question. I'm no expert in > > tweaking fglrx, but afaict there's nothing you can do except wait > > for an update of the driver. You could also try the > > opensource-drivers (I think r600 in your case), cause those do > > their own heuristics to determine hanging or deadlocked compute- > > kernels. > > > > Best, Michael > > Thank you. Do you think using a newer version of xserver would help? Always worth a try imo. But I wouldn't expect too much from doing this. The driver thinks, that a compute-kernel hangs or is deadlocked. If this assumption is correct, the userspace app needs a fix otherwise the driver is faulty. Is this problem related to running a special app or DE? Or does it happen "always"? Best, Michael