Bug 358029

Summary:	lenovo x60s sometimes hangs on resume
Product:	[openSUSE] openSUSE 10.3	Reporter:	Juergen Weigert <jw>
Component:	Mobile Devices	Assignee:	Holger Macht <hmacht>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Minor
Priority:	P5 - None	CC:	behlert
Version:	Final
Target Milestone:	---
Hardware:	x86
OS:	openSUSE 10.3
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Bug Depends on:
Bug Blocks:	357354
Attachments:	/var/log/pm-suspend.log another logfile, directly after a failed resume.

Description Juergen Weigert 2008-02-01 15:44:00 UTC

While testing the docking station, I did suspend to ram and resume frequently.
When the laptop was suspended detached from the docking station,
then inserted and resumed, it always hangs on a black screen, with a blinking
half moon led. Capslock and numlock keys switch ther LEDs on and off.
Typing fast -- generating interrupts as suggested by seife -- does not
help.

Comment 1 Holger Macht 2008-02-03 15:47:21 UTC

Can you please post /var/log/pm-suspend.log. This rather sounds like some sleep hook hanging somewhere...

Comment 2 Juergen Weigert 2008-02-04 21:53:39 UTC

Created attachment 193119 [details]
/var/log/pm-suspend.log

I can confirm that the chance to resume correlates with the number of active hooks. More hooks, smaller chance. See also bug #357401

Comment 3 Holger Macht 2008-02-04 22:18:26 UTC

May be this is even a duplicate of bug #357401? We'll see...

Comment 4 Forgotten User ZhJd0F0L3x 2008-02-07 13:18:02 UTC

(In reply to comment #2 from Juergen Weigert)
> Created an attachment (id=193119) [details]
> /var/log/pm-suspend.log
> 
> I can confirm that the chance to resume correlates with the number of active
> hooks. More hooks, smaller chance. See also bug #357401

This logfile looks like the resume actually worked...

Comment 5 Juergen Weigert 2008-02-07 14:10:24 UTC

Created attachment 193613 [details]
another logfile, directly after a failed resume.

Comment 6 Holger Macht 2008-06-02 15:43:07 UTC

So the system did not even run one single hook on resume. It must hang inside the kernel or s2ram already. I don't think we'll have the time to investigate this further for 10.3. Sorry, closing.