Bug 522904
Summary: | KMS:RS480:X200M suspend/resume GPU lockup | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tomasz Chrzczonowicz <t.chrzczonowicz> | ||||||
Component: | xorg-x11-drv-ati | Assignee: | Dave Airlie <airlied> | ||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 14 | CC: | awilliam, jglisse, lovenemesis, mcepl, t.chrzczonowicz, xgl-maint | ||||||
Target Milestone: | --- | Keywords: | Reopened, Triaged | ||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2012-08-16 21:44:22 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
Tomasz Chrzczonowicz
2009-09-12 03:36:22 UTC
probably the same as 522393 or 522070... -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers My screen doesn't flash, so not likely to be 522393 Also, it doesn't restore properly, so not likely to be 522070 Can I set this bug to blocker? Not really. We wouldn't hold the release for a suspend failure, I'm afraid. we're not near 100% success rate for suspend/resume :/ -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers This is a know bug, i have the same issue on my x200, the hang happen in GPU post function while reprogramming the GPU clock. I haven't yet found how to make it works i need to spy the video bios. Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf, if available), /var/log/dmesg, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance. This should work now with lastest fedora kernel (112 or newer). Please test and report back. Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions). Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you. If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.] I believe this bug is now fixed, so closing it, reopen if you experience this issue with newer kernel like -127 I checked it with -127 in F12 stable and it still hangs when restoring from suspend. KMS is disabled. Created attachment 373538 [details]
/var/log/dmesg
Created attachment 373542 [details]
/var/log/Xorg.0.log
Also, after an unsuccessful restore from suspend, the laptop won't boot-up properly on power-cycling (display doesn't turn on, nothing seems to happen), unless I unplug it from the wall... tomek: have you checked with KMS enabled? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Please test with KMS we are focusing on KMS issues. How do I force enable KMS in F12 to test this? It seems to be disabled by default now, even though it wasn't before. (maybe because of bug 498457). oh, yeah, probably. but you can test with: radeon.modeset=1 if that leads to the _other_ bug, please let us know, so we can prioritize appropriately. thanks! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers It now suspends with KMS but hangs when restoring, just like when KMS is disabled. And yes, KMS hangs the system soon after GDM is started (it can be before, during or slightly after logging in). OK, thanks. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Anymore luck after updating fedora 12 to all the lastest package and with kernel from : http://koji.fedoraproject.org/koji/buildinfo?buildID=150696 Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you] Similar problem was noticed on an Compaq Laptop with X200M: http://www.smolts.org/client/show/?uuid=pub_06467131-6181-47eb-9fb6-c1c397da53b2 ATI driver with KMS enabled: kernel-2.6.35.4-28.fc14.i686 xorg-x11-server-Xorg-1.9.0-9.fc14.i686 xorg-x11-drv-ati-6.13.1-0.3.20100705git37b348059.fc14.i686 The laptop hangs when resuming from suspend. The harddisk and power LEDs keep on (not blinking). No mouse nor keyboard input is accepted. Screen is completely black,too. This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 The problem persists on Fedora 14, too. May someone change the affected version number to 14, please? This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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 |