[Bug 60523] New: Lockup with radeon DPM on Radeon HD5770 (Juniper)
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Fri Jul 5 09:57:40 PDT 2013
https://bugzilla.kernel.org/show_bug.cgi?id=60523
Bug ID: 60523
Summary: Lockup with radeon DPM on Radeon HD5770 (Juniper)
Product: Drivers
Version: 2.5
Kernel Version: 3.10-drm-next-3.11
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri at kernel-bugs.osdl.org
Reporter: tdroste at gmx.de
Regression: No
Created attachment 106814
--> https://bugzilla.kernel.org/attachment.cgi?id=106814&action=edit
dmesg | grep -iE "drm|radeon|power|uvd" after starting a video with mplayer
I have some not always reproducible lockup with the latest DPM code.
There are 2 scenarios:
1. PC boots, DPM is active and reports different power states and levels in
dmesg, but does not change the power level (it's always at power level 2)
2. mplayer is started and plays a video with UVD. DPM switches the power state
to UVD and switches between powerlevel 0 and 2 while playing the video
3. When closing mplayer there are 2 possible outcomes:
a) DPM switches the power state back to performance and stays in power level 0
or 1. This will stay until something triggers it to switch to power level 2
again. As soon as it's in power level 2 again it's never changing back.
b) PC locks up, display is black and VT switch doesn't work until I
SysRq+REISUB to reboot the machine
Scenario b is harder to trigger but it happened at least 2 times today.
dmesg | grep -iE "drm|radeon|power|uvd"
--
You are receiving this mail because:
You are watching the assignee of the bug.
More information about the dri-devel
mailing list