Summary: | sys-power/hibernate-script-2.0-r1 - hibernate and hibernate-ram not working with gentoo-sources-2.6.29-r4 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Atanas Kamburov <atanas.kamburov> |
Component: | [OLD] Core system | Assignee: | Krzysztof Pawlik (RETIRED) <nelchael> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | mobile+disabled, psomas |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | https://bugzilla.kernel.org/show_bug.cgi?id=14006 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | tuxonice-sources-2.6.29-r3 kernel config |
Description
Atanas Kamburov
2009-05-20 04:21:33 UTC
A little update. hibernate and hibernate-ram work with neither gentoo-sources-2.6.29-r5 nor tuxonice-sources-2.6.26-r3. I updated my BIOS, double-checked ACPI options in the kernel, etc. with no success. I am starting to think that I am missing some important kernel option or that the HDD has some bad sectors. Never had any problems with the HDD so far though, and smartmontools don't show anything wrong. I would be very grateful if anyone had a look at my kernel config and emerge --info and spot the problem; I am ready to provide more details. Oh and btw, my system is an IBM ThinkPad x31. Thanks in advance. Created attachment 196307 [details]
tuxonice-sources-2.6.29-r3 kernel config
this is probably a duplicate of #271949 (the bug is caused by the e100) (In reply to comment #3) > this is probably a duplicate of #271949 > (the bug is caused by the e100) > hey, thanks for the hint... However, I de-selected the e100 driver in the kernel and disabled the ethernet card in bios, with no success :( For your information, my hibernate is not working with both gentoo-sources-2.6.29-r5 and tuxonice-sources-2-6-28-r3 (also with unloaded modules for usb, ipw2100 etc.). The good news is, hibernate works with gentoo-sources-2.6.27-r10, so I am going to stick to this older kernel until things get better. Maybe the bug should be renamed to something like "kernel regression ...". I don't want to push, but just ask ... is anyone working on this bug? FYI, I have posted a bug upstream: http://bugzilla.kernel.org/show_bug.cgi?id=14006 From your report on kernel Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=14006) it looks like general kernel/hardware issue thus I'm closing this bug. |