Bug 457053

Summary:	kernel-2.6.25.11-60.fc8.x86_64 breaks S3 suspend/resume Dell D820
Product:	[Fedora] Fedora	Reporter:	Ed Hill <ed>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-01-09 06:42:00 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:

Description Ed Hill 2008-07-29 13:45:53 UTC

Description of problem:

On a Dell D820 laptop, kernel-2.6.25.11-60.fc8.x86_64 breaks S3 suspend-resume.
This is a regression relative to:

kernel-2.6.24.3-50.fc8.x86_64
kernel-2.6.24.4-64.fc8.x86_64
kernel-2.6.24.5-85.fc8.x86_64
kernel-2.6.24.7-92.fc8.x86_64
kernel-2.6.25.4-10.fc8.x86_64
kernel-2.6.25.6-27.fc8.x86_64
kernel-2.6.25.9-40.fc8.x86_64
kernel-2.6.25.10-47.fc8.x86_64

which have all worked rather well using S3.


How reproducible:

The S3 resume stage fails about half of the time.


Additional info:

The system is a Dell D820 laptop (Intel GMA graphics) and its running a 
stock Fedora kernel with NO 3RD PARTY kernel modules.  The following 
suspend quirks have been used with all of the above kernels:

  pm-suspend --quirk-vbe-post --quirk-vbemode-restore

and it has worked nicely for all of them except the recently released 
kernel-2.6.25.11-60.fc8.x86_64.

Does anyone have suggestions or possible work-arounds?  I'll be happy 
to provide hardware info, etc.  Thanks!!!

Comment 1 Bug Zapper 2008-11-26 11:03:22 UTC

This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  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 '8'.

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 8'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 8 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 2 Bug Zapper 2009-01-09 06:42:00 UTC

Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 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.