Bug 768553

Summary:	Kernel 3.1.10-1.13.1 broke suspend to ram on Thinkpad x220
Product:	[openSUSE] openSUSE 12.1	Reporter:	kolA flash <kolAflash>
Component:	Kernel	Assignee:	Rafael Wysocki <rjw>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P2 - High	CC:	gordon, guido.juckeland, jeffm, mattm3a, schuetzm
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 12.1
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description kolA flash 2012-06-23 15:17:59 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20100101 Firefox/13.0

Device: Laptop
Thinkpad x220 (429136G)
CPU + graphic: Core i7 2620M (2.7 GHz)
RAM: 8GM
OS: openSUSE 12.1 x86_64
Power: AC
Kernel parameters (worked very fine with "3.1.10-1.9-desktop"): splash=silent quiet showopts vga=0x317 pcie_aspm=force acpi=noirq i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1

I put my Thinkpad really often into suspend to ram and usually it works very fine. But since I did the Kernel update to "3.1.10-1.13.1-desktop" the suspend to ram doesn't works any more (tried it three times). When putting into "suspend to ram" (tried both: using the KDE shutdown menu OR by pressing Fn-F4 on my keyboard) my Thinkpad just went to the black screen it usually show for about 1 second before going into suspend. But since "3.1.10-1.13.1-desktop" it stays at that screen and the power button starts blinking. This is written on the screen:
[  106.171868] Freezing user space processes ... (elapsed 0.01 seconds) done.
[  106.183823] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[  106.194961] Suspending console(s) (use no_console_suspend to debug)
I think it' identical with the usual text, but usually there's more output after those three lines.

From this point on the system is frozen, no reaction on CTRL-ALT-FX, CTRL-ALT-DELETE or ALT-PRINT-(REISUB). Can't reach it via ping or ssh via WLAN or LAN anymore. I had to reboot by pressing the powerbutton.


One time I tried to boot the system with these kernel parameters (instead of the ones mentioned at the top): splash=silent quiet showopts vga=0x317 no_console_suspend
But it didn't helped. Just gave me this output instead:
[  176.142384] Freezing user space processes ... (elapsed 0.01 seconds) done.
[  176.155130] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.



Because I'm currently very busy I don't have time for any debugging. Sorry for that...

WORKAROUND: After returning to kernel "3.1.10-1.9-desktop" (packages: kernel-desktop, kernel-desktop-base, kernel-desktop-devel, kernel-devel, kernel-docs) everything's fine again.


Maybe related?
https://bugzilla.novell.com/show_bug.cgi?id=768503


Thanks :-)
colAflash

Reproducible: Always

Steps to Reproduce:
1. Put notebook into "suspend to ram" by pressing Fn-F2 (if you have a Thinkpad with that keyboard shortcut) or using the KDE shutdown menu.
Actual Results:  
System goes to console screen, freezes and powerbutton blinks. Had to restart by pressing powerbutton.

Expected Results:  
suspend to ram

Comment 1 kolA flash 2012-06-23 15:28:21 UTC

Additional information concerning relation to bug 768503:
My system is shutting down properly when using "3.1.10-1.13.1-desktop". So maybe it's not as related as I thought.


very busy = studying exams until 14th of July. After that I can do some debugging if you need further information.

Comment 2 Gordon Dickens 2012-06-24 13:00:53 UTC

I am having the same problem.  Sleep/suspend-to-RAM does not work.
The computer freezes and I have to do a hard power off and reboot
to get it back.  I am running OpenSUSE 12.1 on a Dell Precision
M6300 laptop.  The kernel that fails is kernel-default
3.1.10-1.13.1.  I have reverted to kernel-default 3.1.10-1.9.1
which works fine.

BTW, this bug is duplicated in the following bugs as well:

#764864
#768560
#768483

Somebody with the appropriate credentials needs to mark these
bugs as duplicates.

FYI,

Gordon

Comment 3 Guido Juckeland Guido Juckeland 2012-06-25 07:09:12 UTC

Same issue with me on a Thinkpad X201.

Comment 4 Jeff Mahoney 2012-06-25 18:26:24 UTC

Raising Prio to P2 since this seems to be affecting a bunch of users and is a regression.

Comment 5 Rafael Wysocki 2012-06-26 19:38:44 UTC

A duplicate of bnc#764864, perhaps?

Comment 6 Matthew Mah 2012-06-27 19:48:11 UTC

I also have this problem. As the status of this bug is currently NEEDINFO, what info do you need?

Comment 7 Jeff Mahoney 2012-06-27 20:25:31 UTC

This is probably a duplicate of an issue for which we revoked the last kernel update (the one you already installed).

Can you see if the 12.1 KOTD (which will become the next update) fixes the issue for you? You can download it here: http://download.opensuse.org/repositories/Kernel:/openSUSE-12.1/

Comment 8 Guido Juckeland Guido Juckeland 2012-06-28 07:30:38 UTC

(In reply to comment #7)
> Can you see if the 12.1 KOTD (which will become the next update) fixes the
> issue for you? You can download it here:
> http://download.opensuse.org/repositories/Kernel:/openSUSE-12.1/

kernel-desktop-3.1.10-51.1.x86_64 works for me (thinkpad x201).

Got it from:
juckel@denkbrett:~> zypper lr -d | grep kernel
 6 | kernel                             | kernel                             | Yes     | No      |   99     | rpm-md | http://download.opensuse.org/repositories/Kernel:/openSUSE-12.1/standard        |      

Thanks!!

Guido

Comment 9 kolA flash 2012-06-28 10:22:17 UTC

> Can you see if the 12.1 KOTD (which will become the next update) fixes the
> issue for you? You can download it here:
> http://download.opensuse.org/repositories/Kernel:/openSUSE-12.1/

Downloaded and installed (rpm -i ...) from that URL:
kernel-desktop-3.1.10-51.1.x86_64.rpm
kernel-desktop-base-3.1.10-51.1.x86_64.rpm

Rebootet with that kernel, put my notebook into standby and it worked very fine. Waked it up again (worked fine) and put it again into standby and it worked fine too. Also tried to shutdown and it worked also fine. :-)

So that kernel seems to fix the bug.

Comment 10 Jeff Mahoney 2012-06-28 12:46:50 UTC

This is actually a duplicate of bnc#764864, so I'll re-close it that way.

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