Bug 31782
Summary: | nouveau: lockdep spew | ||
---|---|---|---|
Product: | Drivers | Reporter: | Johannes Berg (johannes) |
Component: | Video(DRI - non Intel) | Assignee: | drivers_video-dri |
Status: | CLOSED CODE_FIX | ||
Severity: | normal | CC: | akpm, dev, florian, maciej.rutecki, rjw, tim |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://johannes.sipsolutions.net/files/nouveau-lockdep.txt | ||
Kernel Version: | 2.6.38 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 27352 | ||
Attachments: |
slight lock reordering from Ben
fix in nouveau tree |
Description
Johannes Berg
2011-03-24 09:51:40 UTC
Kernel version is unclear. Is this a 2.6.37->2.6.38 regression, or a post-2.6.38 regression? Thanks. I think this problem was introduced by 6f70a4c3d19e8e8e1047a4dbf0ca910fed39f619. This commit fixes a real problem, so it shouldn't be reverted, but still this issue needs to be fixed. It seems Ben isn't registered here at kernel bugzilla. I will drop him a mail about this. Created attachment 52722 [details]
slight lock reordering from Ben
Could you please test the attached patch? It should fix the problem, but as I'm physically away from my nvidia machine I could not test it myself.
Sorry for being unclear, it's a regression from 2.6.37 to 2.6.38. Compiling a kernel with the patch now. Patch doesn't help, lockdep output looks the same as before (to me anyway, same locks involved and same complaint). Created attachment 54522 [details]
fix in nouveau tree
Could you please try the attached patch? It is already in nouveau tree and should hopefully fix the issue. Just want to make sure if we can close this bug.
I'm now on 2.6.39-rc3 and while the issue persists, the patch doesn't apply. Actually, that was wrong -- I wasn't booting the kernel I was compiling, 2.6.39-rc3 doesn't work at all, I only get a garbled screen :-( The Patch from comment #6 has been merged in 2.6.39-rc5. Can you retest with that? Sorry, I must've missed your email earlier -- I'm now on 2.6.39-rc7 and it doesn't seem to have this issue any more. |