You are not logged in.
Pages: 1
Hello,
Since a few weeks, my laptop (Dell XPS 15 9550) freezes when shutting down. The last printed message is
[ OK ] Reached target Power-Off.
Then nothing happens except fans that kick off. I have to hold the power button to actually shutdown the laptop.
journalctl gives me a bit more details but I cannot find useful information.
systemd[1]: Reached target Power-Off.
systemd[1]: Shutting down.
systemd-shutdown[1]: Syncing filesystems and block devices.
systemd-shutdown[1]: Sending SIGTERM to remaining processes...
systemd-journald[305]: Journal stopped
-- Reboot --
How could I solve this?
Thanks.
Last edited by julienfalque (2025-01-13 06:49:00)
Offline
Likely firmware bug, check if there's an update for your UEFI available. At that point in time that you see this message linux is for most intents and purposes "shut down". Also define "few weeks" did you update in between? Was it not reproducible on a certain kernel but is now?
Offline
I have the same problem on a Dell XPS 13 7390 2-in-1 since kernel 5.5. Downgrading to version 5.4 (now linux-lts) solve the problem.
I've filed a bug upstream https://bugzilla.kernel.org/show_bug.cgi?id=206571 and bisected the kernel to commit 6c3a44ed3c553c324845744f30bcd1d3b07d61fd.
For me version 5.5 has other issues, so, for now, I'm sticking with lts version.
Offline
Same problem on HP Spectre x360 aw0xxx with kernel 5.5.x.
One time screen showed the log of kernel panic with the error:
sched: Unexpected reschedule of offline CPU#4!
This doesn't happen with kernel 5.4.x.
Offline
Same issue on my XPS 7390 2in1.
In my case i sometimes get a kernel panic after shutdown (capslock led blinking and fans spinning).
This panic also makes it impossible to S3 sleep or hibernate.
Last edited by krystiancha (2020-02-28 14:11:58)
Offline
Same issue on my XPS 7390 2in1.
In my case i sometimes get a kernel panic after shutdown (capslock led blinking and fans spinning).
This panic also makes it impossible to S3 sleep or hibernate.
I have exactly the same problem at the moment. If i revert to the 5.4 the issue disappears.
Last edited by soares (2020-04-18 23:52:34)
Offline
Same issue here on an HP Spectre. Does not occur on linux-lts, but does on the latest linux.
Mine too sometimes will result in the blinking caps lock kernel panic, but not always. One time a couple of days ago I did get the CPU message, and I took a picture on my phone (uploaded here). Apologies for the format/quality, of course ordinarily I would have copied the text!
EDIT:
Confirmed reverting the commit found by edoars above (6c3a44ed3c553c324845744f30bcd1d3b07d61fd) fixed it.
If anyone wants a quick fix here is the PKGBUILD I used: https://pastebin.com/PCT1e4uZ
Only added one line to revert the commit (+ changed the name)
Last edited by bananaoomarang (2020-04-19 23:49:54)
Offline
Latest kernel versions seem to have fixed the issue, although there was no activity on https://bugzilla.kernel.org/show_bug.cgi?id=206571.
Offline
I've just updated the system and the issue for me is still present on linux-5.6.12.arch1-1
Offline
Same issue for me too. HP Spectre x360 aw0116na
Working fine with LTS kernel. Broken in stable and zen kernels.
Offline
Hi,
I experienced the same shutdown/reboot issues as mentioned in this thread on a YOGA C940-14iil Laptop.
Sometimes also with the message "Unexpected reschedule of offline CPU#X"
Everything is fine with the current LTS kernel (Zen does not work either)
The problem seems to be the commit described in Post #3 and the same issues are mentioned in this bug report.
A possible workaround is to disable a specific virtualization option in BIOS, see Comment #35 for a detailed description.
I do not have this option in my BIOS settings and disabling virtualization in BIOS completely did not help in my case.
However, I was able to resolve the issues by adding the kernel parameter
intel_iommu=off
With this workaround my machine reboots/shutdowns without the above mentioned problems using the latest mainline kernel (5.6.13-arch1-1).
Offline
Also experiencing this issue on a MacBookPro11,4 on stock arch kernel 5.6.13-arch1-1 for about a week now.. On shutdown all I get is a never-ending blinking underscore.
Might end up switch to LTS kernel for a while since this is my work machine, but Id prefer to run the same kernel on all my arch machines.
Offline
However, I was able to resolve the issues by adding the kernel parameter
intel_iommu=off
With this workaround my machine reboots/shutdowns without the above mentioned problems using the latest mainline kernel (5.6.13-arch1-1).
Works for me also. Perfect now. Thank you for highlighting this.
EDIT: Ah, but the new kernel apparently doesn't detect my laptop's sound (with or without that kernel parameter).... back to the LTS kernel for me.
Last edited by HaughtyGrayAlien (2020-05-22 12:28:11)
Offline
Pages: 1