Red Hat Bugzilla – Bug 501252
KMS:M6 LY:Mobility Radeon 7000 on resume from suspend corrupt screen and no keyboard response
Last modified: 2010-06-28 08:35:15 EDT
Created attachment 344399 [details]
dmesg after resume without modsetting
Description of problem:
when resuming from suspend the screen is blue with a few vertical stripes. there is no response from the keyboard, no caps light, ctrl+alt+del and magic sysrq keys ignored. have to hold power button to escape. sometimes the mouse will move a bar around the screen.
if i boot with nomodeset then resume works fine
Version-Release number of selected component (if applicable):
up to date rawhide
Linux localhost.localdomain 220.127.116.11-140.fc11.i586 #1 SMP Tue May 12 10:30:21 EDT 2009 i686 i686 i386 GNU/Linux
everytime (unless i boot with nomodeset)
Steps to Reproduce:
stuck on corrupt screen
back to my desktop/password box
Created attachment 344400 [details]
xorg log after resume with nomodset
Created attachment 344402 [details]
Xorg.0.log.old, should be the one that failed to resume
i dont know if this is related but also the backlight does not go out when i suspend with KMS.
also i probably should have put this is the description
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY
Created attachment 344405 [details]
dmesg before suspend with KMS
Created attachment 344406 [details]
screen on resume
also one time i have seen the screen just be blank on resume. some times i get a flash of the desktop or password box on resume before it gets to the corrupt screen.
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:
I can confirm that on a Thinkpad T60 with ATI M52 [Mobility Radeon X1300] graphics chip. In some cases, VT switching is still possible, but screen corruption does not disappear without rebooting the machine. I'm running a fresh and up-to-date Fedora 11 x64 install without any modifications.
kernel version: 18.104.22.168-191.fc11.x86_64
xorg version: 22.214.171.1241
version of xorg-x11-drv-ati: 6.12.2
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. For packages from updates-testing repository you can use command
yum upgrade --enablerepo='*-updates-testing'
Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .
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.]
My X31 has sadly died. unless the poster of #7 is still experiencing this feel free to close it. thanks
I can confirm this bug on an up-to-date F12 system (hardware is IBM X31 like the original submitter).
Linux 126.96.36.199-174.fc12.i686 #1 SMP Mon Dec 21 06:24:20 UTC 2009
I can confirm this on my Thinkpad T42 on F12.
kernel-188.8.131.52-127.fc12.x86_64 / 184.108.40.206-127.fc12.x86_64 #1 SMP Sat Nov 7 21:11:14 EST 2009
(I would try a later kernel package, but they seem to crash before I can even make it to suspending and resuming, with or without KMS. I'll file another bug if I can get more information).
I'll try with the F13 alpha at some point if I get a chance.
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 Bugzappers volunteer triage team
[This triage is part of collective effort done by students of University of
Rijeka Department of Informatics.]
I've run into this under Fedora 13, kernel-220.127.116.11-124 - suggest bumping Version to 13.
Does anyone know of an upstream bug for this?
(In reply to comment #14)
> I've run into this under Fedora 13, kernel-18.104.22.168-124 - suggest bumping
> Version to 13.
> Does anyone know of an upstream bug for this?
Could you please file a new bug about it ... this bug seems to be abandoned by its original reporter and I guess it should be put out of misery.
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.