[solved] kernel 3.1.5 kills suspend to ram

Harey · 2011-12-13 07:48:40

Hello all,

since the update to kernel 3.1.5 my system is not able to suspend to ram anymore. I haven't tested suspend to disk yet but I fear the result will be the same. System goes down but the wake up process hangs with a black screen. Only hard reset (!) can get me out here. Can't even change to another tty with ctrl-alt-Fx

Harvey

Edit: Same with suspend to disk. System doesn't even switch off. Both suspends were working before.

Last edited by Harey (2012-01-04 11:29:43)

Shark · 2011-12-13 12:00:59

Do you have anything in kernel line?

pedromj · 2011-12-13 13:00:17

What is your system/hardware (x86/x86-64, brand, CPU model, video card)?

Harey · 2011-12-13 16:03:37

pedromj wrote:

What is your system/hardware (x86/x86-64, brand, CPU model, video card)?

My system:

harvey@obelix ~ $ lspci
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and Protocol Registers (rev 11)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1a.1 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1a.2 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1a.7 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06)
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1d.1 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1d.2 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1d.3 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1d.7 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation 5 Series Chipset LPC Interface Controller (rev 06)
00:1f.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA IDE Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
00:1f.5 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 2 port SATA IDE Controller (rev 06)
01:00.0 VGA compatible controller: nVidia Corporation G84 [GeForce 8600 GT] (rev a1)
02:00.0 SATA controller: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 02)
02:00.1 IDE interface: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 02)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-Core Registers (rev 04)
3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 04)
3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 04)
3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 04)
3f:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller (rev 04)
3f:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Target Address Decoder (rev 04)
3f:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Test Registers (rev 04)
3f:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Control Registers (rev 04)
3f:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Address Registers (rev 04)
3f:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Rank Registers (rev 04)
3f:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Thermal Control Registers (rev 04)                            
3f:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Control Registers (rev 04)                                    
3f:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Address Registers (rev 04)                                    
3f:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Rank Registers (rev 04)                                       
3f:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Thermal Control Registers (rev 04)

My kernel line:

kernel /vmlinuz-linux_64 cryptdevice=/dev/sda5:root root=/dev/mapper/root ro vga=795 resume=/dev/mapper/swapDevice

To make this clear:
This configuration has been working perfectly until I upgraded to kernel 3.1.5.

Edit: I downgraded kernel 3.1.5 -> 3.1.4 and everything is working again. The new kernel definitely is to blame

Harvey

Last edited by Harey (2011-12-13 16:14:37)

pedromj · 2011-12-13 16:13:45

Harey wrote:

To make this clear:
This configuration has been working perfectly until I upgraded to kernel 3.1.5.

No doubt but to do the magic ;-) we need information to isolate the problem. Usually, the problem with suspend-to-ram resides in the graphics card, but not always.

Have you tried to suspend/resume from the console without starting X? Have you tried to disable KMS? Have you tried to boot the kernel alone (something like init=/bin/sh) and suspend/resume (echo mem > /sys/power/state)?

If not, please try.

Harey · 2011-12-13 17:12:01

pedromj wrote:

Harey wrote:
To make this clear:
This configuration has been working perfectly until I upgraded to kernel 3.1.5.
No doubt but to do the magic ;-) we need information to isolate the problem. Usually, the problem with suspend-to-ram resides in the graphics card, but not always.
Have you tried to suspend/resume from the console without starting X? Have you tried to disable KMS? Have you tried to boot the kernel alone (something like init=/bin/sh) and suspend/resume (echo mem > /sys/power/state)?
If not, please try.

console: same effect
KMS: This is a nvidia card with the nvidia drivers. Do they even support KMS? If so, how can I disable this?
boot kernel alone: same effect

Meanwhile I tested kernel 3.1.5 with my intel-based laptop without problems. I have an older one with nvidia graphics which I will test later. But my desktop isn't willing to suspend anymore

Harvey

Last edited by Harey (2011-12-13 17:12:35)

pedromj · 2011-12-13 20:50:24

You can also try to downgrade the linux package to discard other problems (recently the pm-utils was updated too).

If you don't know how, take a look to:
https://wiki.archlinux.org/index.php/Do … ckages#ARM

And get the package from:
http://arm.konnichi.com/core/os/x86_64/ … pkg.tar.xz

If it works with 3.1.4 you can upgrade again and look other alternatives to find the problem, if not, take a look to pm-utils quirks.

Harey · 2011-12-14 08:10:06

pedromj wrote:

You can also try to downgrade the linux package

As I said before, I did this already and just linux 3.1.5 -> linux 3.1.4 is needed for suspend to work again.

Meanwhile I have tested another laptop with nvidia graphics and an older Intel Processor. This machine is working too
The problem seems to be specific to my desktop system. Not sure what else I can do to hunt this down.

Harvey

BonBaba · 2011-12-14 09:50:16

Hi, I have a same problem on kernel 3.1.5.
My system could suspend to ram, but couldn't wake up(black screen).
I have downgraded to kernel 3.1.4 and everything works fine now.

Here is my system:

[bonbaba@EndeavorPro ~]$ lspci
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and Protocol Registers (rev 11)
00:19.0 Ethernet controller: Intel Corporation 82578DC Gigabit Network Connection (rev 05)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 05)
00:1a.1 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 05)
00:1a.2 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 05)
00:1a.7 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05)
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 05)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 05)
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 (rev 05)
00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 7 (rev 05)
00:1c.7 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 8 (rev 05)
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 05)
00:1d.1 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 05)
00:1d.2 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 05)
00:1d.3 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 05)
00:1d.7 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation 5 Series Chipset LPC Interface Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
01:00.0 VGA compatible controller: nVidia Corporation G92 [GeForce GTS 250] (rev a2)
06:00.0 SATA controller: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 03)
06:00.1 IDE interface: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 03)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-Core Registers (rev 04)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 04)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 04)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 04)
ff:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller (rev 04)
ff:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Target Address Decoder (rev 04)
ff:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Test Registers (rev 04)
ff:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Control Registers (rev 04)
ff:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Address Registers (rev 04)
ff:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Rank Registers (rev 04)
ff:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Thermal Control Registers (rev 04)
ff:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Control Registers (rev 04)
ff:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Address Registers (rev 04)
ff:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Rank Registers (rev 04)
ff:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Thermal Control Registers (rev 04)

My kernel line:

kernel /boot/vmlinuz-linux root=/dev/sdb2 resume=/dev/sdb7 ro

I'm using nvidia graphics card too so it might be the cause...

pedromj · 2011-12-14 11:26:25

I don't know what else to try to isolate the problem. Not taking into account the NVidia graphics, as you said it works, the common thing seems to be the processor family. You can check the changelog [1] in order to find what changed about your specific system.

[1] http://www.kernel.org/pub/linux/kernel/ … eLog-3.1.5

BonBaba · 2011-12-14 12:44:37

pedromj wrote:

I don't know what else to try to isolate the problem. Not taking into account the NVidia graphics, as you said it works, the common thing seems to be the processor family. You can check the changelog [1] in order to find what changed about your specific system.
[1] http://www.kernel.org/pub/linux/kernel/ … eLog-3.1.5

Thank you for your reply.
I have read through the log, but I cannot find out the problem since I'm not a programmer, not good at English.
Howerver I found a commit about suspend:

commit b5e0fb085f337c2ab00532d09056da3525f2e847
Author: Kevin Hilman
Date: Tue Nov 22 17:18:24 2011 -0800
usb: musb: PM: fix context save/restore in suspend/resume path

commit 5d193ce8f1fa7c67c7fd7be2c03ef31eed344a4f upstream.

Currently the driver tries to save context in the suspend path, but
will cause an abort if the device is already runtime suspended. This
happens, for example, if MUSB loaded/compiled-in, in host mode, but no
USB devices are attached. MUSB will be runtime suspended, but then
attempting a system suspend will crash due to the context save
being attempted while the device is disabled.

On OMAP, as of v3.1, the driver's ->runtime_suspend() callback will be
called late in the suspend path (by the PM domain layer) if the driver
is not already runtime suspended, ensuring a full shutdown.

Therefore, the context save is not needed in the ->suspend() method
since it will be called in the ->runtime_suspend() method anyways
(similarily for resume.)

NOTE: this leaves the suspend/resume methods basically empty (with
some FIXMEs and comments, but I'll leave it to the maintainers
to decide whether to remove them.

I don't know whether this is related to the problem or not.

Harey · 2011-12-14 14:08:45

Since I am not alone anymore I have filed a bug report:
https://bugs.archlinux.org/task/27572

Harvey

jusko · 2011-12-14 16:24:23

Same situation here. Will update on the bug report.

BonBaba wrote:

I'm using nvidia graphics card too so it might be the cause...

I am using ATI (tried both drivers); so it's probably not the card.

EDIT: Might not be related, but I'm also on an encrypted rootfs.

Last edited by jusko (2011-12-14 17:14:32)

pedromj · 2011-12-15 08:41:29

You could compare your systems (hardware and modules) to know what they have in common and thus approach the problem.

Also, please, join the bug reports and fix their description to something more relevant like "Resume from suspend-to-ram broken in kernel 3.1.5" (just a suggestion).

BonBaba · 2011-12-15 10:15:39

jusko wrote:

Same situation here. Will update on the bug report.
BonBaba wrote:
I'm using nvidia graphics card too so it might be the cause...
I am using ATI (tried both drivers); so it's probably not the card.
EDIT: Might not be related, but I'm also on an encrypted rootfs.

Thank you for your reply.
I have just reported on Bugtracker too.
I don't use encryption at all(...dangerous!), so perhaps it is not related, but I'm not sure.

I hope someone will solve this issue...
I wish I were a super hacker!

Harey · 2011-12-17 13:12:40

This seems to be a problem with Redhat too:
https://bugzilla.redhat.com/show_bug.cg … &id=768010

I think this is an upstream bug in the kernel.

Harvey

Harey · 2011-12-18 12:42:41

YAY! I found it! My system suspends again.

Here is what I did: My system's BIOS has in 'Power Management Setup' an option 'HPET support' (high precision timer support) which can be set 32bit, 64bit or disabled. If disabled, the suspend works with kernel 3.1.5. Maybe the kernel cracks can guess now where all the trouble comes from. For me it's working and that is all I need

Nevertheless this seems to be only a workaround so I won't mark the thread as SOLVED.

Harvey

gborzi · 2011-12-23 10:09:44

Thanks Harvey, your workaround works fine with my system. Not having a BIOS that allows me to disable HPET, I had to disable it by adding hpet=disable to the kernel parameters.

Harey · 2012-01-04 11:29:08

Kernel 3.1.7 fixes this error for me.
http://www.kernel.org/pub/linux/kernel/ … eLog-3.1.7

BonBaba · 2012-01-05 01:48:42

That is a very good news!

mjohnson · 2012-01-12 14:40:14

I just found this thread after experiencing the same issue; for me, disabling HPET in grub's menu.lst works (thanks for the workaround!), but I'm running kernel 3.1.8-1, so either the underlying issue wasn't completely fixed, or they broke it again going from 3.1.7 to 3.1.8, or something else...any ideas? (I'm very happy to have a workaround, but it'd be nice to have it just working!)

Harey · 2012-01-12 15:15:20

mjohnson wrote:

I'm running kernel 3.1.8-1, so either the underlying issue wasn't completely fixed, or they broke it again going from 3.1.7 to 3.1.8, or something else...any ideas?

That's bad news. My systems suspends without problems with kernel 3.1.8. Is your system completely freezed after suspend? Are there any error messages?

Harvey

mjohnson · 2012-01-12 16:34:34

Harey wrote:

That's bad news. My systems suspends without problems with kernel 3.1.8. Is your system completely freezed after suspend? Are there any error messages?

It seems to wake up just fine (fans turn on, hard drives spin up, etc.), except that the screen doesn't turn on (and no amount of moving the mouse or keyboard changes that). To top it off, I can SSH in from my laptop, so the only thing wrong seems to be the screen.

Looking in /var/log/pm-suspend.log I don't see any obvious errors; is there anywhere else I should check for errors?

Harey · 2012-01-12 17:00:41

mjohnson wrote:

It seems to wake up just fine (fans turn on, hard drives spin up, etc.), except that the screen doesn't turn on (and no amount of moving the mouse or keyboard changes that). To top it off, I can SSH in from my laptop, so the only thing wrong seems to be the screen.

This sounds like an unrelated issue. Your graphics card is not waking up again. The former bug caused the whole system to freeze. Have a look a /var/log/Xorg.0.log. What card do you have? What driver do you use? Try from a ssh shell

init 3

and then

init 5

Does this resurrect the card?

Harvey

Last edited by Harey (2012-01-12 17:01:51)

mjohnson · 2012-01-12 17:43:57

Well, whatever happened doesn't seem to be reproducible! I'm sorry for muddying the waters here with an issue unrelated to the original one. I removed the hpet=disable line from /boot/grub/menu.lst and rebooted, then once my system had finished booting I suspended it...and when I woke it, it woke back up just fine. I've tried it a couple of times now, and no issues. I guess it was something transient, and I apologize for the bother!

Arch Linux

#1 2011-12-13 07:48:40

[solved] kernel 3.1.5 kills suspend to ram

#2 2011-12-13 12:00:59

Re: [solved] kernel 3.1.5 kills suspend to ram

#3 2011-12-13 13:00:17

Re: [solved] kernel 3.1.5 kills suspend to ram

#4 2011-12-13 16:03:37

Re: [solved] kernel 3.1.5 kills suspend to ram

#5 2011-12-13 16:13:45

Re: [solved] kernel 3.1.5 kills suspend to ram

#6 2011-12-13 17:12:01

Re: [solved] kernel 3.1.5 kills suspend to ram

#7 2011-12-13 20:50:24

Re: [solved] kernel 3.1.5 kills suspend to ram

#8 2011-12-14 08:10:06

Re: [solved] kernel 3.1.5 kills suspend to ram

#9 2011-12-14 09:50:16

Re: [solved] kernel 3.1.5 kills suspend to ram

#10 2011-12-14 11:26:25

Re: [solved] kernel 3.1.5 kills suspend to ram

#11 2011-12-14 12:44:37

Re: [solved] kernel 3.1.5 kills suspend to ram

#12 2011-12-14 14:08:45

Re: [solved] kernel 3.1.5 kills suspend to ram

#13 2011-12-14 16:24:23

Re: [solved] kernel 3.1.5 kills suspend to ram

#14 2011-12-15 08:41:29

Re: [solved] kernel 3.1.5 kills suspend to ram

#15 2011-12-15 10:15:39

Re: [solved] kernel 3.1.5 kills suspend to ram

#16 2011-12-17 13:12:40

Re: [solved] kernel 3.1.5 kills suspend to ram

#17 2011-12-18 12:42:41

Re: [solved] kernel 3.1.5 kills suspend to ram

#18 2011-12-23 10:09:44

Re: [solved] kernel 3.1.5 kills suspend to ram

#19 2012-01-04 11:29:08

Re: [solved] kernel 3.1.5 kills suspend to ram

#20 2012-01-05 01:48:42

Re: [solved] kernel 3.1.5 kills suspend to ram

#21 2012-01-12 14:40:14

Re: [solved] kernel 3.1.5 kills suspend to ram

#22 2012-01-12 15:15:20

Re: [solved] kernel 3.1.5 kills suspend to ram

#23 2012-01-12 16:34:34

Re: [solved] kernel 3.1.5 kills suspend to ram

#24 2012-01-12 17:00:41

Re: [solved] kernel 3.1.5 kills suspend to ram

#25 2012-01-12 17:43:57

Re: [solved] kernel 3.1.5 kills suspend to ram

Board footer