You are not logged in.
Hi there,
After updating Arch a couple of days ago, my laptop (Dell XPS 13 9320) is not powering off.
Linked here is a paste of my log when powering off (output of "sudo journalctl -b 1"). The bit that catches my eye the most is this:
dev-nvme0n1p2.swap: Swap process exited, code=exited, status=4/NOPERMISSION
This also happens when I do a
sudo systemctl stop dev-nvme0n1p2.swap
. However,
sudo swapoff /dev/nvme0n1p2
works just fine.
Additionally, The system is occasionally (maybe 50% of the time) hanging on boot. In those cases, I get a log like this (click me) with a much scarier "null pointer dereference" error.
My system has been working perfectly with regular updates for the past 8 months or so; this is the first time I've experienced any boot or poweroff issues. For what it's worth, it also seems to lock up when I close the lid. I'm not sure how to get log info for that.
Thanks for any help, please let me know if there's any other info I can include.
Edit: Also, here is a log of the pacman update that seems to have broken things: https://pastebin.com/raw/u3BY8ccR.
Edit 2: I'm not sure if this needs clarification, but I guess the "freeze" happens at the very end of the power-down sequence. The last line I see on my screen is "shutdown[1]: Powering off." and it just hangs there. The longest I let it go was a couple of hours.
Last edited by mortimer_mcmire (2024-01-30 14:45:15)
Offline
Bumping this to note that the same thing is happening when I try to suspend my computer via "systemctl suspend" or by closing the lid. This totally freezes my computer (screen still on but not refreshing) and, like in the poweroff case, there's no way out other than holding down the power button.
Here is a suspend log from when I tried closing my laptop lid:
https://pastebin.com/raw/26j8VjYu
It seems that in both the suspend case and the poweroff case, everything happens correctly up until the final step, and then whatever is supposed to talk to my hardware to actually do the deed just fails silently.
I can't figure out where else to look for clues, so if anyone is able to help, I would be eternally grateful.
Offline
https://pastebin.com/raw/qA63CYpN cuts off before the actual kernel stack trace and the poweroff in https://pastebin.com/raw/nEuLABgw takes 3 seconds?
The critical update has the kernel from 6.6 to 6.7 (does the issue remain w/ the LTS kernel?) and switch from dbus-daemon to dbus-broker (does it remain if you install dbus-daemon-units?)
Jan 29 09:07:50 say-aprende slim[1024]: [01/29/24, 09:07:50:909] info: [DESKTOP-SIDE-EFFECT] Update from desktop for keys ["app"]
Since you're the second one today, PSA: SLiM is DEAD
Offline
Thank you for the suggestions and PSA! I know I need to move on from SLiM; I couldn't find another graphical login manager that suited my needs (locking + works with dual monitors). Oh well, I will find my way back to ly.
Is a 3-second poweroff abnormal? I think my laptop usually powers off very quickly. Sorry about the truncated logs; not sure what happened there since pastebin is down at the moment.
In any case: The solution here was that (months ago) I had installed kernel modules from archlinux-ipu6-webcam to get my blasted Intel webcam working. I'm not sure exactly which module was the culprit, but those modules are causing issues with the 6.7 kernel. Uninstalling them with pacman made my machine behave normally after the next reboot.
Offline
Is a 3-second poweroff abnormal?
Depends on what needs to be done for the shutdown, but it's certainly no excessive (eg. 25s dbus or 90s systemd timeouts take magnitudes longer)
Offline
Oh well, I will find my way back to ly
which isn't a fix either because it's not setting up systemd sessions properly as well.
Offline
I had completely read over that one…
https://wiki.archlinux.org/title/Display_manager
xdm doesn't have to look shit, https://archlinux.org/packages/extra/any/xdm-archlinux/ and on a de-facto single user system you could just boot straight into a locked GUI session.
Offline