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 1RIMWH-0003Xb-JD for garchives@archives.gentoo.org; Mon, 24 Oct 2011 15:32:57 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BBF4121C057; Mon, 24 Oct 2011 15:32:46 +0000 (UTC) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by pigeon.gentoo.org (Postfix) with SMTP id 93523E03E4 for ; Mon, 24 Oct 2011 15:31:47 +0000 (UTC) Received: (qmail invoked by alias); 24 Oct 2011 15:31:46 -0000 Received: from p5B0820C5.dip.t-dialin.net (EHLO pc.localnet) [91.8.32.197] by mail.gmx.net (mp037) with SMTP; 24 Oct 2011 17:31:46 +0200 X-Authenticated: #13997268 X-Provags-ID: V01U2FsdGVkX1/7zSo8qRP7sRyz7iS902EL3jZ9FxecNYBcPI08fI YsclWD5tHHhfOy From: Michael Schreckenbauer To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Kernel Panic fglrx Date: Mon, 24 Oct 2011 17:31:45 +0200 Message-ID: <2405702.c3XAKe8b4k@pc> User-Agent: KMail/4.7.2 (Linux/2.6.38-gentoo; KDE/4.7.2; x86_64; ; ) In-Reply-To: <4EA577D0.50408@gmail.com> References: <4EA577D0.50408@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: cd66a01e3313d7a2ffe10b86c81743e8 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