Bug 493626
Summary: | [Radeon] Freeze on resume under KMS (radeon mobility 9600) | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Pantelis <pktoss> | ||||||||||||||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||
Severity: | medium | Docs Contact: | |||||||||||||||||
Priority: | low | ||||||||||||||||||
Version: | 11 | CC: | jglisse, kernel-maint, vedran | ||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||
Target Release: | --- | ||||||||||||||||||
Hardware: | i586 | ||||||||||||||||||
OS: | Linux | ||||||||||||||||||
Whiteboard: | |||||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||
Last Closed: | 2010-06-28 11:39:33 UTC | Type: | --- | ||||||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||||||
Documentation: | --- | CRM: | |||||||||||||||||
Verified Versions: | Category: | --- | |||||||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||
Embargoed: | |||||||||||||||||||
Attachments: |
|
Description
Pantelis
2009-04-02 12:51:17 UTC
Created attachment 337797 [details]
lspci -nn -v
Created attachment 337798 [details]
Xorg.log
Created attachment 337799 [details]
plain dmesg
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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping 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 https://fedoraproject.org/wiki/BugZappers 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping 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. |