Bug 42639 - Kernel warns about a possible deadlock in Radeon PM
Summary: Kernel warns about a possible deadlock in Radeon PM
Status: RESOLVED PATCH_ALREADY_AVAILABLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(Other) (show other bugs)
Hardware: All Linux
: P1 low
Assignee: drivers_video-other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-23 15:22 UTC by Alexandre Demers
Modified: 2012-01-25 15:49 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.3.0-rc1
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Dmesg: Error message beginning at line 1156 (74.04 KB, text/x-log)
2012-01-23 15:22 UTC, Alexandre Demers
Details
Kern.log: error message beginning at line 1156 (122.11 KB, text/x-log)
2012-01-23 15:29 UTC, Alexandre Demers
Details

Description Alexandre Demers 2012-01-23 15:22:57 UTC
Created attachment 72172 [details]
Dmesg: Error message beginning at line 1156

When booting, I have a deadlock message about radeon power management. I'll be adding some logs soon. Usually, after some time (count many minutes or even hours), the screen will freeze before showing a hang error message in the driver. Then, I have to reboot the computer.
Comment 1 Alexandre Demers 2012-01-23 15:29:24 UTC
Created attachment 72173 [details]
Kern.log: error message beginning at line 1156

Pretty much the same thing as dmesg. However, I noticed something more at the bottom (2 last lines) about a conflict.
Comment 2 Alexandre Demers 2012-01-23 15:30:21 UTC
I don't have time to bisect it for now, but I may try somewhere this week.
Comment 3 Alexandre Demers 2012-01-23 16:18:33 UTC
By the way, I'm using a Radeon HD6950.
Comment 4 Jérôme Glisse 2012-01-24 03:53:39 UTC
The error message in log are just warning about lock.

The last 2 line are from virtual memory, about a conflict. What desktop are you using ? KDE ? Gnome-shell ?

What would be helpful is the message you see at hang time, it doesn't make to the log i guess.
Comment 5 Alexandre Demers 2012-01-24 04:34:04 UTC
I'm using Gnome-shell for now. And you are right about the error message not making to the log. Next time, I'll try to write it from my tablet when I'll have it on screen. Indeed, that would be usefull.

Either way, I was not seeing the conflict nor the deadlock warning using kernel 3.2, so I'm digging and bisecting.
Comment 6 Jérôme Glisse 2012-01-25 15:39:46 UTC
Don't worry about the deadlock stuff i sent a patch to silence out this false warning. For the other issue my guess is the vm patch (GPU virtual memory support v22)
Comment 7 Alexandre Demers 2012-01-25 15:49:46 UTC
OK, i'll close this one, but I'll keep an eye on the vm patch, since I also reported a bug related to it (rendering error, bisected to that patch, but fixed since). Thanks.

Note You need to log in before you can comment on or make changes to this bug.