Bug 35374

Summary: nouveau: nv50, regression "GPU lockup - switching to software fbcon" introduced in 2.6.38-rc8
Product: xorg Reporter: Michał Lipski <tallica>
Component: Driver/nouveauAssignee: Nouveau Project <nouveau>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: doug.hunley, EoD, ghutzl, nigel
Version: 7.4 (2008.09)   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg log, 2.6.38 with commit 73412c3854c877e5f37ad944ee8977addde4d35a reverted
none
dmesg log, 2.6.38-rc7, no GPU lockup information
none
dmesg log, 2.6.38-rc8, GPU lockup
none
As suggested, dmesg log 2.6.38 with drm.debug=14 3 none

Description Michał Lipski 2011-03-16 16:42:33 UTC
Created attachment 44527 [details]
dmesg log, 2.6.38 with commit 73412c3854c877e5f37ad944ee8977addde4d35a reverted

There's a regression introduced in kernel >=2.6.38-rc8. It's in nouveau/master (commit 7972f91c24bb66643d76cf635faea78eb184e6b6) as well. Dmesg shows: "GPU lockup - switching to software fbcon". I've done a git bisect. The problematic commit is: 73412c3854c877e5f37ad944ee8977addde4d35a "drm/nouveau: allocate kernel's notifier object at end of block". I reverted that commit on top of the 2.6.38 to confirm the issue.

Reproducible: always
Comment 1 Michał Lipski 2011-03-16 16:44:28 UTC
Created attachment 44528 [details]
dmesg log, 2.6.38-rc7, no GPU lockup information
Comment 2 Michał Lipski 2011-03-16 16:45:17 UTC
Created attachment 44529 [details]
dmesg log, 2.6.38-rc8, GPU lockup
Comment 3 Michał Lipski 2011-03-18 10:56:19 UTC
Created attachment 44589 [details]
As suggested, dmesg log 2.6.38 with drm.debug=14 3
Comment 4 EoD 2011-04-21 18:27:42 UTC
I can confirm a similiar bug. But my system completely locks up, that's why I can't provide you with a proper dmesg log (I could make a picture though).

I also did a bisect and ended up with the same commit 73412c3854c877e5f37ad944ee8977addde4d35a. I got an AGP GeForce 7600 GT (NV40 - not NV50!).

Do you require further information?
Comment 5 EoD 2011-04-21 19:48:11 UTC
Nevermind, this bug has been fixed by a18d89ca026140eb8ac4459bf70a01c571dd9a32 (2.6.39-rc2+).
Comment 6 Marcin Slusarz 2011-04-22 07:36:32 UTC
*** Bug 36248 has been marked as a duplicate of this bug. ***
Comment 7 Marcin Slusarz 2011-04-22 07:37:10 UTC
*** Bug 36330 has been marked as a duplicate of this bug. ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.