Bug 443279

Summary:	latest kernel update makes suspend to ram unusable
Product:	[openSUSE] openSUSE 11.0	Reporter:	Martin Koller <kollix>
Component:	Kernel	Assignee:	Pavel Machek <pavel>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	openSUSE 11.0
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Martin Koller 2008-11-10 08:23:03 UTC

Using the 2.6.25.16-0.1-pae kernel and ati-fglrxG01-kmp-pae-8.532_2.6.25.16_0.1-1.1 on an IBM Thinkpad T43 works with suspend-to-ram/resume like a charm.

Installing the latest kernel security patch to version 2.6.25.18 breaks suspend to ram. The laptop does no longer resume when in suspend mode (not even the USB bus is reactivated, as the LED light on my USB mouse is not turned on again). The laptop simply blocks and does not react to anything. I need to hard power-off the machine.

Comment 1 Cyril Hrubis 2008-11-10 14:24:32 UTC

Is this reproducible without ati binary module?

Comment 2 Martin Koller 2008-11-10 17:56:42 UTC

Yes. I set Driver "ati" in xorg.conf, made sure lsmod does not show fglrx and tried again. Same result.

Comment 3 Pavel Machek 2008-11-25 10:55:38 UTC

Hmm, that's  duplicate of vanilla regression, and we even know which patch causes that IIRC...

...yes...



commit ffa4da2a25bb4ac08f710ac99827baf48a8f8d57
Author: Thomas Gleixner <tglx@linutronix.de>
Date:   Wed Sep 3 21:37:08 2008 +0000

    clockevents: prevent multiple init/shutdown

    commit 9c17bcda991000351cb2373f78be7e4b1c44caa3 upstream

    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

is reported to cause a resume regression on Lenovo x60, x41 and x61 (probably
other Lenovo boxes are affected as well) with 2.6.25.18.  At the same time, the
2.6.27.y kernels are reported to work correctly for the affected users.

Can you please try to identify the upstream commits that fix the problem on
these boxes?

Comment 4 Rafael Wysocki 2008-11-25 15:38:19 UTC


*** This bug has been marked as a duplicate of bug 439461 ***