You are not logged in.
Hi,
Suspend to ram works ok, but suspend to disk seems to mostly fail with a kernel panic. I'm not sure how to get the contents of the error, but it contains the following.
BUG: unable to handle kernel paging request at ffff800c902e000
IP: [..] load_image_lzo=0x7ee/0xe50
Oops: 0002 [#1] PREEMPT SMP
Call trace:
wake_up_atomic
swsusp_read
software_resume.part
resume_store
kobj_attr_store
sysfs_write
vfs_write
SyS_write
system_call_fastpath
RIP load_image_lzo
Kernel panic - not syncing: Attempted to kill init? exitcode=9
Any ideas what could be wrong? I'm running kernel 3.1.2.9-1-ARCH #1 SMP PREEMPT
I've had the laptop resume from hibernate successfully at least once (yesterday) but haven't had it work today.
Offline
Just ran memtest and it seems to crash after 3 minutes. I wonder if this is related?
Offline
If memtest has crashed, you'd better change your faulty RAM - as it can be the source of all sorts of misery...
And yes, it could be related.
Also, try to check your RAM in another box.
Last edited by scar (2014-01-29 14:01:32)
“The future has already arrived. It's just not evenly distributed yet.”
― William Gibson
Offline
on second thought I don't think it's a memory issue. Quite a few people have reported memtest86+ 5.01 freezing when running in multithreaded mode, and when I ran memtest on a different PC it also froze.. Too much of a coincidence I think. I'm running prime95 now and so far no issues. I'll let it run for a few hours but I think the hardware is stable, so now I need to figure out what is causing the hibernation issue.
Last edited by mrpringle (2014-01-29 21:04:29)
Offline
Another thing is I have a 4GB swap partition and 8GB of ram. Don't know whether this should be a problem?
Offline
ok, I've scanned the ssd for problems. stress tested the memory and cpu. I'm pretty sure the hibernate//resume problem is not caused by faulty hardware. Worst case scenario is I configure the computer so it never hibernates, but I would prefer to resolve the issue.
Offline
Try to disconnect as much stuff from your computer as possible and remove any cards in card readers.
With my laptop I've found that if I have an sd card in the card reader when resuming from hibernation I also get a kernel panic, no messages or errors shown on screen. I don't use hibernation much, so I have no idea when this started to happen but a few kernel releases ago it used to work without problems.
This particular card reader or implementation in my laptop is a bit temperamental, often I get errors related to the card reader when cold booting with a card inserted, so you probably want to look at the output of dmesg as see if anything is throwing errors during a normal cold boot, that might help narrow it down a bit.
You should have a swap partition as large as your ram if you want to hibernate (you will see this recommendation everywhere) but I guess the kernel will use only as much swap as it needs, I guess that if there isn't enough swap the kernel will just abort hibernation.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
thanks for the suggestion. I can't see anything obvious in dmesg. Maybe I'll just leave it for now and in a few months it might magically work again after a kernel update.
Offline