Bug 603402

Summary:	Fails to suspend because of device 00:0a (parport0)
Product:	[Fedora] Fedora	Reporter:	Stefan Neufeind <redhat>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	13	CC:	anton, dougsland, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mgoodwin
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-02-02 18:30: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 Stefan Neufeind 2010-06-12 21:38:13 UTC

When closing the notebook-lid the system tries to suspend but logs to /var/log/messages:

PM: Device 00:0a failed to suspend: error -5
PM: Some devices failed to suspend

and immediately continues working normal. Looking at sys it seems that the device is parport0. Happened on a Dell D630 several times now, on other times the system suspended fine. Worked fine until after one of the latest kernel-upgrades (I think it even already worked after upgrading to F13, but I'm not sure).

Running kernel 2.6.33.5-112.fc13.x86_64.

Comment 1 Mark Goodwin 2011-01-28 05:02:26 UTC

I haven't tested it (yet) but apparently the fix has been posted upstream:
https://lkml.org/lkml/2010/10/21/456

Regards
-- Mark

Comment 2 Stefan Neufeind 2011-01-28 07:40:55 UTC

Sorry for the late reply. Haven't seen this anymore for quite some time. Not on my current F14, but I think also some time during F13 it must have started working again.

Anybody still experiencing this? Otherwise maybe we should close it.

Comment 3 Mark Goodwin 2011-01-28 07:47:05 UTC

(In reply to comment #2)
> Sorry for the late reply. Haven't seen this anymore for quite some time. Not on
> my current F14, but I think also some time during F13 it must have started
> working again.
> 
> Anybody still experiencing this? Otherwise maybe we should close it.

I'm still hitting it - running F14 on my laptop 2.6.35.6-45.fc14.x86_6
I'll build a patched kernel and see if it goes away.

-- Mark

Comment 4 Mark Goodwin 2011-02-02 06:15:23 UTC

Updated to 2.6.35.10-74.fc14 and this seems to be fixed now.
So I think we can just close it out.

-- Mark