From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 42678] [3.3-rc1] radeon stuck in kernel after lockup
Date: Tue, 3 Apr 2012 19:38:39 GMT
Message-ID: <201204031938.q33Jcdfu001473@bugzilla.kernel.org>
References: <bug-42678-2300@https.bugzilla.kernel.org/>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org>
Received: from bugzilla.kernel.org (bugzilla.kernel.org [198.145.19.204])
	by gabe.freedesktop.org (Postfix) with ESMTP id 7A39E9E7F8
	for <dri-devel@lists.freedesktop.org>;
	Tue,  3 Apr 2012 12:38:39 -0700 (PDT)
Received: from bugzilla.kernel.org (localhost [127.0.0.1])
	by bugzilla.kernel.org (8.14.5/8.14.5) with ESMTP id q33Jcd5S001474
	for <dri-devel@lists.freedesktop.org>; Tue, 3 Apr 2012 19:38:39 GMT
In-Reply-To: <bug-42678-2300@https.bugzilla.kernel.org/>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/dri-devel>
List-Post: <mailto:dri-devel@lists.freedesktop.org>
List-Help: <mailto:dri-devel-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=subscribe>
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org

https://bugzilla.kernel.org/show_bug.cgi?id=42678





--- Comment #11 from Torsten Kaiser <just.for.lkml@googlemail.com>  2012-04-03 19:38:37 ---
> Is 3.4 still affected?

I don't know, but I suspect it.
Because since the fix of my underlying GPU hang in 3.3-rc3 there wasn't a need
for a recovery or a change to hang X again.

As I tried to explain in comment #8 there where 3 kernel bugs involved for me.
1.: a GPU lockup that happened since 3.1 and was fixed in 3.3-rc3
2.: a regression 3.2 -> 3.3-rc1 in the mutex locking, fixed in 3.3-rc2
3.: a regression 3.2 -> 3.3-rc1 that prevents X to recover from the GPU lockup.

3. was visible in 3.3-rc2 (see comment #3) as 2. was already fixed, but 1. was
still happening.
But after 3.3-rc3 1. has been fixed, so 3. no longer triggers for me, but I
suspect that the GPU lockup recovery is still broken, because I did not see any
patch that claimed to fix it.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.