Red Hat Bugzilla – Bug 493626
[Radeon] Freeze on resume under KMS (radeon mobility 9600)
Last modified: 2010-06-28 07:39:33 EDT
Created attachment 337796 [details]
Description of problem:
When booting a modesetting (KMS) kernel, the laptop freezes on resume.
This happened with the radeon test day livecd and with the kernel released just after as well.
Version-Release number of selected component (if applicable):
Linux localhost.localdomain 18.104.22.168-37.rc1.fc11.i586 #1 SMP Wed Apr 1 08:57:13 EDT 2009 i686 i686 i386 GNU/Linux
Steps to Reproduce:
1. Boot fedora's latest radeon test day livecd or even one with the newer kernel released just after.
2. suspend in any way (from gui, pm-suspend, echo mem > /sys/power/state, anything)
3. Press the power button to resume
Frozen system. Ssh connection dead, no keyboard/mouse, blank screen, does not even respond to pings.
Correctly resumed system.
Smolt hardware profile:
1. Suspend/resume work fine with 'nomodeset'.
2. The radeon suspend test: 'cat /debug/dri/0/radeon_suspend_test' successfully resumes, with latest kernel no more drm oops. Relevant dmesg output attached.
3. Attached lspci -nn, lcpci -nn -v, dmesg, dmesg with drm.debug=1, dmesg with drm debugging enabled only during the suspend test.
4. Xorg.0.log attached too just in case it has any interesting info, though the same problem happens regardless whether the suspend / resume is from console or X.
5. Other information / patch testing happily provided on demand.
Created attachment 337797 [details]
lspci -nn -v
Created attachment 337798 [details]
Created attachment 337799 [details]
Created attachment 337801 [details]
dmesg during suspend test with drm.debug enabled
echo 1 > /sys/module/drm/parameters/debug &&
cat /debug/dri/0/radeon_suspend_test &&
echo 0 > /sys/module/drm/parameters/debug
An additional (hopefully helpful) clue:
1. When I compile just a vanilla 2.6.29 + drm-next + drm-modesetting-radeon + drm-radeon-reorder-bm patches, resume no longer freezes completely.
The display stays blank, but at least I can now ssh in. (KMS is still enabled)
I 'm attaching the config of the "almost working" kernel and a dmesg with verbose PM messages and also with drm.debug enabled during the suspend/resume.
Created attachment 337862 [details]
dmesg from an "almost working" session
This is a dmesg with verbose PM messages from a suspend/resume session that doesn't freeze (just no display). It should at least show the order things are suspended / resumed.
drm.debug is also enabled during the suspend/resume cycle.
Created attachment 337863 [details]
.config of "almost working" kernel
It seems the "almost working" kernel can become "fully working"
if I use pm-suspend --quirk-vbestate-restore
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
Can you test with fedora 12 livecd and report if it works with it.
I will try as soon as I can but it will take some time since I am nowhere near that laptop right now. At worst I 'll be able to test around christmas when I get home.
Can you rather retry with F13 Alpha?
Fedora Bugzappers volunteer triage team
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.