Bug 278491

Summary:	System hangs when suspending
Product:	[Fedora] Fedora	Reporter:	Andreas Thienemann <andreas>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7	CC:	chris.brown
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-01-13 19:18:26 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 Andreas Thienemann 2007-09-05 14:08:43 UTC

Description of problem:
With the current kernel from updates-testing the system in question, a hp nx5000
notebook does not suspend anymore.

The screen shows "Stopping Tasks" at which time the system stops being
responsive and hangs.

Unfortunately, I'm not seeing any more information about the system state at
that time.

Version-Release number of selected component (if applicable):
kernel-2.6.22.5-71.fc7

How reproducible:
Always

Additional info:
Booting the system with kernel-2.6.22.2-57.fc7 enables working suspend again.

Comment 1 Christopher Brown 2007-10-01 15:02:07 UTC

Hello,

I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the fedora kernel.

http://fedoraproject.org/wiki/KernelBugTriage

I am CC'ing myself to this bug and will try and assist you in resolving it if I can.

There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?

If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.

Comment 2 Christopher Brown 2008-01-13 19:18:26 UTC

As indicated previously there has been no update on the progress of this bug
therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue
still occurs for you and I will try to assist in its resolution. Thank you for
taking the time to report the initial bug.