Bug 570105 - Cannot resume from suspend to disk (S4)
Summary: Cannot resume from suspend to disk (S4)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.5
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Lenny Szubowicz
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-03 10:10 UTC by Yolkfull Chow
Modified: 2013-08-15 13:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-15 13:22:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
hardware information (18.50 KB, text/plain)
2010-03-04 05:28 UTC, Yolkfull Chow 		no flags Details
View All

Description Yolkfull Chow 2010-03-03 10:10:53 UTC 
Description of problem:
Got following error message during resume:

host system error, PCI problems?
host controller halted, very bad!

I also tested this on 2.6.18-186, works fine.

Version-Release number of selected component (if applicable):
2.6.18-190

How reproducible:
Everytime

Steps to Reproduce:
1. echo disk > /sys/power/state
2.
3.
  
Actual results:
Host hang when try to resume from suspend to disk

Expected results:
can resume from suspend to disk

Additional info:
Comment 1 Yolkfull Chow 2010-03-03 10:11:44 UTC 
Add keyword 'regression' because it doesn't happen on 2.6.18-186.
Comment 2 Matthew Garrett 2010-03-03 14:17:00 UTC 
What hardware is this?
Comment 3 Yolkfull Chow 2010-03-04 05:28:42 UTC 
Created attachment 397721 [details]
hardware information

Please see hardware info from attachment.
Comment 4 Matthew Garrett 2010-03-04 12:42:49 UTC 
Sorry, I should have been clearer. What vendor and model is this?
Comment 5 Yolkfull Chow 2010-03-12 07:54:01 UTC 
Dell Optiplex 755
Comment 7 Lenny Szubowicz 2013-08-15 13:22:52 UTC 
Given how long this problem has gone unresolved, it's relatively low severity, and the lifecycle stage that RHEL 5 is currently in, the problem reported will not be fixed in RHEL 5.

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