Bug 66041
Summary: | 2 attempts needed to hibernate | ||
---|---|---|---|
Product: | Power Management | Reporter: | Eric Lan (tenoreamer) |
Component: | Hibernation/Suspend | Assignee: | Rafael J. Wysocki (rjw) |
Status: | CLOSED DUPLICATE | ||
Severity: | normal | CC: | aaron.lu, lenb, rui.zhang, tianyu.lan |
Priority: | P1 | ||
Hardware: | x86-64 | ||
OS: | Linux | ||
Kernel Version: | 3.10-2 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: | dmesg after failed "s2disk" |
Description
Eric Lan
2013-11-28 07:32:49 UTC
Could you try the latest upstream kernel v3.13-rc1? Is there easier way to help you debug this ? The linux environment is a production system for me and I don't want to risk damaging it by upgrading to a release-candidate kernel. You can't upgrade kernel? So how can you test a fix patch? So far, I know a fix about hibernation swap allocation fix in the v3.13. This may fix the issue. http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=fd432b9f8c7c88428a4635b9f5a9c6e174df6e36 Because I had only 4G RAM and I used 64-bit LMDE, that might not fix it. I am not familiar with the procedure. I found the most forefront Debian sid used the kernel 3.11-2, still lesser than v3.13. So it would involve re-compile and re-configure the kernel by myself right ? (In reply to Eric Lan from comment #4) > Because I had only 4G RAM and I used 64-bit LMDE, that might not fix it. > > I am not familiar with the procedure. I found the most forefront Debian sid > used the kernel 3.11-2, still lesser than v3.13. So it would involve > re-compile and re-configure the kernel by myself right ? Yes, you can follow this link to rebuild kernel. http://kernelnewbies.org/KernelBuild It doesn't have anything to do with swap, it may be that we didn't preallocate/free enough memory during the start of hibernation. Please attach full dmesg after a failed hibernation. Created attachment 118501 [details]
dmesg after failed "s2disk"
dmesg after failed "s2disk" (the first time)
|