Bug#872664: linux-image-4.9.0-3-686-pae: Resume from hibernate fails on Thinkpad T60
Hi, Ben Hutchings wrote: > On Sun, 2017-08-27 at 13:04 +0200, Holger Wansing wrote: > > Control: reassign -1 initramfs-tools > > > > > > Holger Wansing wrote: > > > > > > I tried to find the problem, and performed some tests found on > > > https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.t > > > xt > > > in »a) Test modes of hibernation«: > > > I ran all off (one by one): > > > echo freezer > /sys/power/pm_test > > > echo devices > /sys/power/pm_test > > > echo platform > /sys/power/pm_test > > > echo processors > /sys/power/pm_test > > > echo core > /sys/power/pm_test > > > and then hibernated and resumed. > > > Everything with success ! > > > > > > I also did (from »c) Using the "test_resume" hibernation option«): > > > # echo test_resume > /sys/power/disk > > > # echo disk > /sys/power/state > > > and this succeeded too, several times and reliably. > > > > > > > > > So this is probably not a kernel issue. > > > I will try if a BIOS upgrade solves the problem. > > > > After BIOS upgrade, still no success :-( > > > > Anyhow, this does not look kernel-related; since initramfs is also > > involved in hibernating, reassigning accordingly. > > The initramfs just tells the kernel where to read the resume image > from. But do check whether the resume device is configured correctly > (see /usr/share/doc/initramfs-tools/NEWS.Debian.gz) It was configured in /etc/initramfs-tools/conf.d/resume: RESUME=UUID=446d3716-ee67-4c7c-90fa-ae5c3aaf5ec7 The UUID matches the swap partition. So I assume everything is fine here. And the harddrive (an SSD) gets some seconds of heavy load, so I think, it loads the resume image. Holger -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#872664: linux-image-4.9.0-3-686-pae: Resume from hibernate fails on Thinkpad T60
On Sun, 2017-08-27 at 13:04 +0200, Holger Wansing wrote: > Control: reassign -1 initramfs-tools > > > Holger Wansing wrote: > > > > I tried to find the problem, and performed some tests found on > > https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.t > > xt > > in »a) Test modes of hibernation«: > > I ran all off (one by one): > > echo freezer > /sys/power/pm_test > > echo devices > /sys/power/pm_test > > echo platform > /sys/power/pm_test > > echo processors > /sys/power/pm_test > > echo core > /sys/power/pm_test > > and then hibernated and resumed. > > Everything with success ! > > > > I also did (from »c) Using the "test_resume" hibernation option«): > > # echo test_resume > /sys/power/disk > > # echo disk > /sys/power/state > > and this succeeded too, several times and reliably. > > > > > > So this is probably not a kernel issue. > > I will try if a BIOS upgrade solves the problem. > > After BIOS upgrade, still no success :-( > > Anyhow, this does not look kernel-related; since initramfs is also > involved in hibernating, reassigning accordingly. The initramfs just tells the kernel where to read the resume image from. But do check whether the resume device is configured correctly (see /usr/share/doc/initramfs-tools/NEWS.Debian.gz) Ben. -- Ben Hutchings Teamwork is essential - it allows you to blame someone else. signature.asc Description: This is a digitally signed message part
Bug#872664: linux-image-4.9.0-3-686-pae: Resume from hibernate fails on Thinkpad T60
Control: reassign -1 initramfs-tools Holger Wansing wrote: > > I tried to find the problem, and performed some tests found on > https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt > in »a) Test modes of hibernation«: > I ran all off (one by one): > echo freezer > /sys/power/pm_test > echo devices > /sys/power/pm_test > echo platform > /sys/power/pm_test > echo processors > /sys/power/pm_test > echo core > /sys/power/pm_test > and then hibernated and resumed. > Everything with success ! > > I also did (from »c) Using the "test_resume" hibernation option«): > # echo test_resume > /sys/power/disk > # echo disk > /sys/power/state > and this succeeded too, several times and reliably. > > > So this is probably not a kernel issue. > I will try if a BIOS upgrade solves the problem. After BIOS upgrade, still no success :-( Anyhow, this does not look kernel-related; since initramfs is also involved in hibernating, reassigning accordingly. -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#872664: linux-image-4.9.0-3-686-pae: Resume from hibernate fails on Thinkpad T60
I tried to find the problem, and performed some tests found on https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt in »a) Test modes of hibernation«: I ran all off (one by one): echo freezer > /sys/power/pm_test echo devices > /sys/power/pm_test echo platform > /sys/power/pm_test echo processors > /sys/power/pm_test echo core > /sys/power/pm_test and then hibernated and resumed. Everything with success ! I also did (from »c) Using the "test_resume" hibernation option«): # echo test_resume > /sys/power/disk # echo disk > /sys/power/state and this succeeded too, several times and reliably. So this is probably not a kernel issue. I will try if a BIOS upgrade solves the problem. thanks Holger -- Created with Sylpheed 3.5.1 under the n e w D E B I A N L I N U X 9 " S T R E T C H " . Registered Linux User #311290 - https://linuxcounter.net/
Bug#872664: linux-image-4.9.0-3-686-pae: Resume from hibernate fails on Thinkpad T60
Package: src:linux Version: 4.9.30-2 Severity: normal Hi, since upgrading from Jessie to Stretch, I'm unable to use suspend/resume feature on my IBM T60 Thinkpad. Before it worked perfectly for years. The symptoms are exactly as described in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843609: When resuming I get the grub menu, then some initial kernel messages (output from fsck for example), the harddisk is working a lot, and then only a blinking cursor, that's it. Switching to virtual consoles is not possible, and no X. Performing a hibernate when the system is running in recovery mode (single user mode, init 1) gives the same result. I tried with the 4.11 kernel from unstable, the same problem. I also tried with the 3.16 kernel from jessie, which is also still installed here, the same problem. Thus it's probably not a kernel problem, but I have no clue what package to report this against instead ... Holger -- Created with Sylpheed 3.2.0 under the new D E B I A N L I N U X 7 . 0 W H E E Z Y ! Registered Linux User #311290 - https://linuxcounter.net/
