Bug 42639
| Summary: | Kernel warns about a possible deadlock in Radeon PM | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Alexandre Demers (alexandre.f.demers) |
| Component: | Video(Other) | Assignee: | drivers_video-other |
| Status: | RESOLVED PATCH_ALREADY_AVAILABLE | ||
| Severity: | low | CC: | glisse |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 3.3.0-rc1 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
Dmesg: Error message beginning at line 1156
Kern.log: error message beginning at line 1156 |
||
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.
I don't have time to bisect it for now, but I may try somewhere this week. By the way, I'm using a Radeon HD6950. 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. 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. 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) 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. |
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.