You are not logged in.
When I hibernate my system, everything seems fine.
However, when it wakes up, all I can see is a frozen image of the moment when I hibernated, regardless of how long I wait.
Does anybody know how I could even start to debug this? nothing appears in the journal, those are the last entries I see in the problematic boot:
ago 02 00:25:39 dell-xps systemd[1]: Starting Wait for lockscreen before suspending...
ago 02 00:25:39 dell-xps systemd[1]: Started Wait for lockscreen before suspending.
ago 02 00:25:39 dell-xps systemd[1]: Reached target Sleep.
ago 02 00:25:39 dell-xps systemd[1]: Starting System Hibernate...
ago 02 00:25:39 dell-xps systemd[1]: hyprlock-suspend.service: Deactivated successfully.
ago 02 00:25:39 dell-xps systemd-sleep[5767]: Successfully froze unit 'user.slice'.
ago 02 00:25:39 dell-xps systemd-sleep[5767]: Performing sleep operation 'hibernate'...
ago 02 00:25:39 dell-xps kernel: PM: hibernation: hibernation entry
ago 02 00:25:39 dell-xps kernel: Filesystems sync: 0.014 seconds
The same happens if I hibernate from a tty (or at least, I can boot back into that tty and see the cursor blinking, but can't type anything. I can also switch to other ttys with ctrl+alt+fX but I only get an unresponsive black screen with a blinking cursor) and normal suspension works fine (except, of course, suspend-then-hibernate).
This is happening with 6.10.10 zen (but has been happening for the past 3-4 months too, while the lts kernel works fine) on my xps 9320 (i7 1260P). 16GB of ram and 16GB swapfile
Offline
Can you narrow down around which time this broke? Also does this happen with the "linux" package aswell?
Offline
That's a bit of a hard question as downgrading kernels that much isnt exactly trivial.
Yes, the normal Linux kernel has that issue aswell
Offline
Does adding either `nomodeset` or `i915.modeset=0` to the kernel command line help anything?
Offline
broken af graphics and laptop not even turning on after hibernation, instead stuck on the XPS screen (reisub worked fine)
Offline
the latest lts release is now 6.12, meaning that I'm now having this issues when using lts kernels too. great
Offline
Is the issue also present in the latest kernel release candidate?
sudo pacman -U https://pkgbuild.com//\~gromit/linux-bisection-kernels/linux-mainline-6.14rc3-1-x86_64.pkg.tar.zst
This way we don't start investigating a bug in detail which may already be fixed in a newer version ..
(note that this installs the kernel as linux-mainline, so you need to configure your bootloader to boot it (for example via grub-mkconfig -o ... or by writing the systemd-boot loader entry))
Offline
I don't seem to be able to boot with that kernel, not really sure why. I have configured /etc/mkinitcpio.d/linux-mainline.preset accordingly, as follows
# mkinitcpio preset file for the 'linux' package
ALL_config="/etc/mkinitcpio.conf"
ALL_kver="/boot/vmlinuz-linux"
PRESETS=('default')
#default_config="/etc/mkinitcpio.conf"
#default_image="/boot/initramfs-linux.img"
default_uki="/boot/EFI/Linux/arch-linux-mainline.efi"
#default_options=""
#fallback_config="/etc/mkinitcpio.conf"
#fallback_image="/boot/initramfs-linux-fallback.img"
fallback_uki="/boot/EFI/Linux/arch-linux-mainline-fallback.efi"
fallback_options="-S autodetect --cmdline /etc/kernel/fallback_cmdline"
(copied the one from linux, which is why some comments might look off)
then regenerated it and created the boot entry with
sudo efibootmgr --create --disk /dev/nvme0n1 --part 1 --label "Arch Linux Mainline" --loader /boot/EFI/Linux/arch-linux-mainline.efi
Getting a "no bootable device found" error when trying to boot from it tho (it does look like it is being signed properly by sbctl, sb shouldn't be the issue here).
Unless you have any reason to believe that some change in this kernel could fix my issue though, I don't think this is worth wasting much time on, as I've been having this issue on recent kernels on pretty much all kernels released after 6.6 or 6.7 (haven't really bisected it, might consider doing so if getting desperate ahah).
Thanks a lot for the help tho, I will try to see what I can do to hopefully manage to try the newer kernel out and let you know what happens if I do. Let me know if there's anything else you think could be useful
Offline