Bug 439442

Summary:	With latest kernel 2.6.25.18-0.2 resumeing from s2ram on ThinkPad T61p no longer works
Product:	[openSUSE] openSUSE 11.0	Reporter:	Michael Karbach <karbach>
Component:	Kernel	Assignee:	E-mail List <bnc-team-screening>
Status:	VERIFIED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	caf4926
Version:	Final
Target Milestone:	---
Hardware:	64bit
OS:	openSUSE 11.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Michael Karbach 2008-10-28 10:01:42 UTC

After updating from kernel 2.6.25.11-0.1 to 2.6.25.18-0.2 on OpenSuSE-11.0 resumeing from a suspend to RAM state fails. After downgrading the kernel back to the old one the systems resumes without any problem.

The system is a Lenovo ThinkPad T61p. All details of my installation can be seen here:

http://wptl12.physik.uni-wuppertal.de/index.php/computing/computer/81-thinkpad-t61p


Best regards,

 Michael

Comment 1 Alexander Orlovskyy 2008-10-28 11:07:42 UTC

Please provide s2ram -n output log (test it on kernel 2.6.25.18-0.2)
It would be great if you can answer following questions:

- what options you gave to s2ram to make it work ?
- did you tested it from both X and the text console mode (ctrl-alt-f1 or the minimal mode described here) ?
- if there is any special setup you needed to do to make it work, also mention it.  ?

Comment 2 Alexander Orlovskyy 2008-10-28 11:13:29 UTC

*** Bug 439353 has been marked as a duplicate of this bug. ***

Comment 3 Michael Karbach 2008-10-28 17:05:33 UTC

I have used the options: -f -a 3

I have only used it from X

I do not need any other special setup. As far as I can judge, it also works with 2.6.25.11-0.1 without any option except -f.

But note, may be this is relevant, my usual resume from s2ram needs very long, roughly 2:30-3 min. And it seems, that the system apart from X, is ready 1-2min before. I do not know why, and have not seen any comment on this behaviour anywhere on the net. Apart from that, suspend to RAM works so far without any problem.

Comment 4 Michael Karbach 2008-10-28 17:42:06 UTC

Now I have done a lot of tests and eventually succeeded to resume!

Without any option, except  s2ram -f it works!

And now my problem with the 3min is also resolved, it resumes within a few seconds :-)


So, at least for me the bug can be closed. 

I have updated my webpage with this hint. 


Best regards,

 Michael

Comment 5 Alexander Orlovskyy 2008-10-30 14:19:50 UTC

Michael, i will close this bug.
If you get any new info about this bug, than please reopen it.