Arch Linux

ulke

Member

Registered: 2011-04-29

Posts: 50

[Solved] Suspend to RAM fails with kernel panic after upgrade

[Edit:]
I was wrong to assume device-mapper or lvm2 to be the cause of the problem, it was actually VirtualBox. I discovered this when I tried to shut down the system and got another kernel panic, but this time with console output. Downgrading Virtualbox to 4.0.12-1 fixed it for now, until I find the time to write a bug report.

[2nd edit:]
Somebody already wrote a bug report:
http://www.virtualbox.org/ticket/9253

[3rd edit:]
"Somebody" was none other than the great wonder. Thanks!

[Orinal post:]
Since yesterday's pacman -Syu, suspend to RAM fails and the systems hangs with a blinking caps lock LED. The only candidates I could find in pacman.log that seem capable of causing such an error are lvm2 and device-mapper (updated July 16). I run an Arch i686 setup with an encrypted HD using LUKS and LVM2.

I have no idea how to proceed. What logs, if any, could give me a hint at what's going on? How do I determine whether lvm2 or device-mapper or something else is to blame? Sorry if these are broad and/or stupid questions, I'm new at this...

Last edited by ulke (2011-07-20 17:44:27)

StenM

Member

Registered: 2011-07-03

Posts: 33

Re: [Solved] Suspend to RAM fails with kernel panic after upgrade

No downgrading required.
Power off (post 6):
https://bbs.archlinux.org/viewtopic.php?id=122956
Hibernation (post 7):
https://bbs.archlinux.org/viewtopic.php?id=122957