Bug 629282 - After suspend & resume, system cannot properly shut down, but at some point hangs
Summary: After suspend & resume, system cannot properly shut down, but at some point h...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-01 14:06 UTC by A. Folger
Modified: 2011-06-28 13:36 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-28 13:36:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
excerpt from var/log/messages (193.40 KB, application/octet-stream)
2010-09-05 20:26 UTC, A. Folger
no flags Details

Description A. Folger 2010-09-01 14:06:37 UTC
Description of problem:
After suspend & resume, system cannot properly shut down, but at some point hangs. KDE begins shutting down orderly, but then, after the screen goes dark, and I expect any moment to see the Fedora logo while the message appears "shutting down" or "restarting," the screen remains dark (though backlit), and a one pixel red border is visible at the edge of the screen, all around (should I say all asquare, or better, all arectangle? ;-)). This happens every time, provided the computer had previously been suspended and resumed.

Version-Release number of selected component (if applicable):
Fedora 13 with all updates applied, on an x86_64.

How reproducible:
Always

Steps to Reproduce:
1. Start computer, wait for Window manager to come up.
2. Suspend.
3. Resume
3. Select shutdown or poweroff or whatever your window manager setup calls it, or even restart.

Actual results:
After beginning to shut down the WM in an orderly fashion, screen goes blank, and a thin red border appears all around the edge of the screen; the computer hangs.

Expected results:
Proper, failure free shutdown or restart, respectively.

Additional info:


Some more data:
# rpm -q kernel
kernel-2.6.33.5-124.fc13.x86_64
kernel-2.6.33.6-147.fc13.x86_64
kernel-2.6.33.6-147.2.4.fc13.x86_64
# dmidecode
<SNIP>
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
        Manufacturer: ASUSTeK Computer INC.
        Product Name: M4A88T-M
<SNIP>
Handle 0x0004, DMI type 4, 40 bytes
Processor Information
        Socket Designation: AM3
<SNIP>
#

Comment 1 Mads Kiilerich 2010-09-03 21:07:51 UTC
If you have are using Radeon video controller then please try 2.6.34.6-49 from http://koji.fedoraproject.org/koji/buildinfo?buildID=193317 or later and verify if it solves your problem.

Comment 2 A. Folger 2010-09-05 11:36:01 UTC
I just tried it, and resume simply failed. Once the machine resumed, it was unresponsive, and only ever showed a blank screen. What now?

Comment 3 Mads Kiilerich 2010-09-05 18:28:58 UTC
I guess /var/log/dmesg and perhaps a smolt profile would be helpful.

Comment 5 A. Folger 2010-09-05 20:26:51 UTC
Created attachment 443194 [details]
excerpt from var/log/messages

Comment 6 A. Folger 2010-10-18 21:58:28 UTC
This problem has disappeared, after I switched from using a VGA cable to using DVI. My problem in this bug also disappeared: https://bugzilla.redhat.com/show_bug.cgi?id=538486

I would be interested in learning why there are these problems with the VGA setup but not with DVI, though.

Comment 7 Mads Kiilerich 2010-10-18 22:25:48 UTC
Perhaps the display and the video controller has communication problems which have strange consequences?

What happens if you use another VGA cable and/or another VGA display?

Comment 8 A. Folger 2010-10-18 22:31:11 UTC
I don't have either available. My other computer is a laptop. I do have an old and a new video card, and the VGA problem is present in both. DVI may work perfectly on the old card, but since it has been mothballed, it is impractical to check that.

Thanks.

Comment 9 Bug Zapper 2011-05-31 14:48:28 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 10 Bug Zapper 2011-06-28 13:36:25 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.