Bug 472142 - KMS:RS482:Xpress 200M resume from hibernation problems
Summary: KMS:RS482:Xpress 200M resume from hibernation problems
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 13
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Airlie
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-18 22:48 UTC by Don Zickus
Modified: 2011-06-27 14:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 14:02:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg log after resuming (47.31 KB, text/plain)
2009-02-19 03:07 UTC, Don Zickus
no flags Details
xorg.0.log after resuming (48.98 KB, text/plain)
2009-02-19 03:09 UTC, Don Zickus
no flags Details

Description Don Zickus 2008-11-18 22:48:58 UTC
Description of problem:
So I did a pm-hibernate on my laptop.  Opening it back up and pressing the on-button thawed it back into its original state.  At least until I tried to read the screen.  All the characters were turned into black squares across all the apps and desktop.  Over time some of the chars became readable but not all.  It is very weird to look at, the rest of the desktop is fine, the mouse looks ok, the windows look ok, I can even see the fedora logo in the lower left corner of my desktop.  Just the characters are screwed up.

Version-Release number of selected component (if applicable):
still fails on 2.6.27.5-105.f10.x86_64

How reproducible:
always

Steps to Reproduce:
1. pm-hibernate
2. resume
3. look at the screen
  
Actual results:
funny looking alien characters

Expected results:
english looking characters

Additional info: 
I think my suspend to memory has issues too but that is different and I haven't tested with the latest kernel yet.

Comment 1 Dave Jones 2008-11-18 22:58:22 UTC
radeon xpress is generally a disaster recently.  There are a number of other bugs related to modesetting.  This may be a dupe of one of them.

Comment 2 Bug Zapper 2008-11-26 05:35:04 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 François Cami 2009-02-16 15:04:17 UTC
Don,
Could you add full dmesg and /var/log/Xorg.0.log as uncompressed text/plain attachments to this bug please ?
Also, could you try booting with nomodeset and report.

Thanks

---
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 4 Don Zickus 2009-02-19 03:07:08 UTC
Created attachment 332494 [details]
dmesg log after resuming

Comment 5 Don Zickus 2009-02-19 03:09:56 UTC
Created attachment 332495 [details]
xorg.0.log after resuming

Comment 6 Don Zickus 2009-02-19 03:12:44 UTC
I have attached the requested logs.  For the last 3 months I have been using nomodeset successfully.  Note the attached logs are created with the power cord plugged in.  Doing the same test off battery only produces different results (at least for the successful case - scrambled screen).

Comment 7 Don Zickus 2009-10-06 14:46:25 UTC
Using the latest F12 rawhide, I still have this issue.  Switching to a gnome desktop makes it easier to reproduce.  Just close lid, wait for machine to hibernate, then open lid, press button to turn on, watch screen become seriously out of sync and then reboot to get the sanity back.

Comment 8 Bug Zapper 2009-11-18 08:54:00 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  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 '10'.

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 10'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 10 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

Comment 9 Don Zickus 2009-11-18 15:24:16 UTC
Just updating the bug to reflect this issue still affects f12

Comment 10 Vedran Miletić 2010-03-24 00:05:09 UTC
Is this still an issue with F13 Alpha?

Comment 11 Don Zickus 2010-03-24 13:56:12 UTC
Let me go dust off the laptop and give it a try when I get home tonight.

Comment 12 Don Zickus 2010-03-25 13:36:56 UTC
so resume from hibernation is still an issue with f13's 2.6.33.1-24.f13 kernel (which just sits on top of a standard f12 distro).

Though I get vsync?? problems instead of black squares.

Comment 13 Vedran Miletić 2010-03-25 18:52:20 UTC
Thank you for reporting back.

Comment 14 Bug Zapper 2011-06-02 18:24:08 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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

Comment 15 Bug Zapper 2011-06-27 14:02:08 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.


Note You need to log in before you can comment on or make changes to this bug.