Bug 193984

Summary:	class driver suspend failed for cpu0
Product:	[Fedora] Fedora	Reporter:	Kevin Larkin <hondaman>
Component:	kernel	Assignee:	Dave Jones <davej>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5	CC:	pfrields, wtogami
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:	2006-11-24 23:01:58 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 Kevin Larkin 2006-06-03 22:16:51 UTC

When the laptop is booted on battery power, and I login to gnome, then close the
lid, I get the following error on a black screen (it appears to exit gnome?)

stopping tasks:==================================================:
class driver suspend failed for cpu0
could not power down device <NULL>: error -22
some devices failed to power down.

This is a dell inspiron 1000 with a sis 650 chipset

No pcmcia cards are plugged in, and no usb devices are present.

This error ONLY occurs when the laptop has been booted on battery power.  If the
laptop is booted on AC power, and I close the lid, I get a login screen to gnome.

[root@hondalap1 ~]# uname -a
Linux hondalap1 2.6.16-1.2122_FC5 #1 Sun May 21 15:01:01 EDT 2006 i686 i686 i386
GNU/Linux

Comment 1 Kevin Larkin 2006-06-03 22:27:45 UTC

I need to update the conditions under which this crash occurs.  

It happens when the laptop is booted with battery power, AND, it happens if the
laptop is booted on AC power, I disconnect the power, then close the lid.

Comment 2 Dave Jones 2006-10-17 00:30:25 UTC

A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed.  See bug 207474 for further details.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.

Thank you.

Comment 3 Dave Jones 2006-11-24 23:01:58 UTC

This bug has been mass-closed along with all other bugs that
have been in NEEDINFO state for several months.

Due to the large volume of inactive bugs in bugzilla, this
is the only method we have of cleaning out stale bug reports
where the reporter has disappeared.

If you can reproduce this bug after installing all the
current updates, please reopen this bug.

If you are not the reporter, you can add a comment requesting
it be reopened, and someone will get to it asap.

Thank you.