[Bug 60251] New: Resume after suspend-to-RAM crashes in kernel module radeon
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Sun Jun 30 06:16:28 PDT 2013
https://bugzilla.kernel.org/show_bug.cgi?id=60251
Summary: Resume after suspend-to-RAM crashes in kernel module
radeon
Product: Drivers
Version: 2.5
Kernel Version: 3.8.8, 3.9.8, drm-next from 2013-06-29
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri at kernel-bugs.osdl.org
ReportedBy: birger.retterstol.olaisen at gmail.com
Regression: No
I have an older HP Compaq dc5750 Microtower with an ATI Radeon XPRESS 1150
chipset and an integrated ATI Radeon X300 graphic card (RS482/RS485 [Radeon
Xpress 1100/1150]). For more detailed info on the system see
http://h10010.www1.hp.com/wwpc/us/en/sm/WF06a/12454-12454-64287-321860-3328896-3252512.html?dnr=1
. This is an x86_64 machine.
When doing suspend-to-RAM with pm-suspend, the system suspends nicely (screen
and fan turns off, and the power led starts pulsing) but when I try to resume
the system, it stops after just a couple of seconds, and I have to do a hard
reboot to start the system. /var/log/pm-suspend.log contains no lines from the
resume, only from the suspend.
The distribution I'm using is Linux Mint 15, based on Ubuntu 13.04, and I've
used DebuggingKernelSuspend from the Ubuntu Wiki
(https://wiki.ubuntu.com/DebuggingKernelSuspend) to try to debug the problem.
After recompiling the kernel with CONFIG_PM_TRACE, /sys/power/pm_trace pointed
to radeon kernel module as the source of the problem.
As suggested on the Ubuntu Wiki page, I also tested two mainline kernels
(drm-next from 2013-06-29 and v3.9.8) from
http://kernel.ubuntu.com/~kernel-ppa/, and they cashed on resume the same way
as the Ubuntu 3.8 kernel.
I attach the pm-suspend.log.
With regards,
Birger Retterstøl Olaisen
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
More information about the dri-devel
mailing list