Applied the patch and compiled a Kernel.
Seems to be fixed in 6.9.0-rc4 (got bored after 35 cycles)
2 Likes
Yeah Iām not doing that XD
That sounds like very good news
Itās part of 6.8.7 now.
3 Likes
Thank you Mario.
Confirmed 400 cycles on 6.8.7.
40 cycles so far, thatās double my previous record.
Edit: Just had a reset after about 130 cycles, gonna give it another run.
Edit2: Well damn the reset is reproducible, at least it went from freeze or reset to just reset.
2 Likes
not here. 6.8.7 still wonāt hibernate, while 6.6.28 does.
Not saying itās relevant but I have changed the Wifi controller to an Intel one.
So have I, also tried setting the igpu back to game optimized but that doesnāt seem to have completely fixed it.
1 Like
Not hibernating at all is probably a separate issue
1 Like
Now itās cracked 500 cycles, I donāt get it anymore.
I have changed absolutely nothing.
Edit: and now it froze after 530 cycles. On one hand I am glad I am not crazy and it just suddenly works, on the other hand it doesnāt just suddenly work XD.
1 Like
Probably over 100 is enough for a normal use-case for hibernate unless you donāt reboot your laptop for months on end.
Honestly I never had it happen in normal use before
no comment XD
1 Like
Is anyone else still having issues with hibernate specifically and only after suspending?
I have suspend-then-hibernate configured, and am frequently coming back to an empty battery after suspending the system and then walking away. The system suspends properly, but locks up after waking and then attempting to hibernate.
On arch 6.8.7, bios 3.05, and I can reproduce/demonstrate the problem the following way:
- Boot cleanly, run the aforementioned hibernate stress test for some cycles to vet that the behavior discussed previously is fixed.
- Suspend by running
systemctl suspend. Alternatively, use something like amd_s2idle.py to easily wake up automatically after e.g. 10s. Resume. - Run the stress test again. After 1-2 cycles, the system locks up with a black screen, but keyboard and power LEDs are still lit. If not, suspend and resume again, then run the stress test again.
Or
- Set
HibernateDelaySec=30in/etc/systemd/sleep.conf. - Run
systemctl suspend-then-hibernate1-2 times until it locks up.
Anecdotally, this issue also seems to occur more often when the system wakes itself via rtc, but Iāve not done extensive testing of this.
I have the same problem on arch. Maybe itās not the same problem as discussed here?
I have an luks partition with lvm on it and a swapfile on the lvm-root partition (ext4).
No problems with hibernation on 6.6.x. Workās very reliable.
With the exact same configuration on 6.8.x or 6.9rc[1-5] after systemctl hibernate the screen turns black for about 10-15 seconds and then the screensaver screen shows upā¦
dmesg shows:
[ 892.144251] PM: Cannot find swap device, try swapon -a
[ 892.144253] PM: Cannot get swap writer
But swapon shows:
NAME TYPE SIZE USED PRIO
/swapfile file 32G 0B -2
So the reason why hibernation fails is obvious. For some reason hibernate to swapfile is no longer working although nothing in the configuration changed except the kernel.
But sadly I wasnāt able to find any information or bugreport on the net. This error is only known with swapfiles on btrfs-partitions and dracut (iām using mkinitcpio) but not on ext4.
Maybe someone has a hint for me how to further debug this?
I have ran hibernate to sapfiles on btrfs and ext4 under luks on 6.8.x and both worked (with the crash after a bunch of cycles issue discussed here though).
@Mistral24, you describe exactly the issues I have (including reliable hibernation w/kernel 6.6x and failed hibernation w/ swapfile error messages w/kernel 6.8+) using Manjaro with grub and standard ext4 partitions. Something in kernel 6.8+ is off.
Confirming that Iām still seeing same behavior (hibernate fails intermittently) after updating to 3.05 bios on Arch 6.8.8.
But looks like the upstream bios issue is still in progress 
Iām now on 6.9rc6 and hibernation is back working 
.
On 6.8.8 itās still brokenā¦
1 Like