Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#78766 - [systemd] PLEASE ENTER SUMMARY
Attached to Project:
Arch Linux
Opened by Mehmet Türk (mmturk) - Monday, 12 June 2023, 07:29 GMT
Last edited by Toolybird (Toolybird) - Monday, 12 June 2023, 19:47 GMT
Opened by Mehmet Türk (mmturk) - Monday, 12 June 2023, 07:29 GMT
Last edited by Toolybird (Toolybird) - Monday, 12 June 2023, 19:47 GMT
|
DetailsDescription:
On reboot or poweroff i get: "Failed to unmount /oldroot" errors ending with "kvm: exiting hardware virtualization" line (takes too long to reach this line). I can only power off by long pressing the power button. I've seen similar bug reports and workarounds relating to nouveau/nvidia drivers but my laptop is all amd. HP aero 13 be-0024nt. ryzen 5 5600u with integrated gpu rtl8821ce wifi/bt card Additional info: * systemd 253.4+ * cannot produce any useful logs * cannot find any upstream bug reports but this also happens on updated fedora 38 but not on updated ubuntu 23.04 Steps to reproduce: Issue reboot or poweroff (sometimes it succeeds to cleanly reboot/poweroff, 1 out of 10 tries) |
This task depends upon
Closed by Toolybird (Toolybird)
Monday, 12 June 2023, 19:47 GMT
Reason for closing: Upstream
Additional comments about closing: See comments
Monday, 12 June 2023, 19:47 GMT
Reason for closing: Upstream
Additional comments about closing: See comments
FS#63697as I did not have this problem with earlier (prior to 253) systemd versions. Also I do not have an NVIDIA card, just an integrated AMD gpu.FS#72499although again not limited to 253. If you disable KVM in firmware is the issue still present? Have you left the system in the hung state for an extended period of time for instance 30 minutes to see if it does eventually shutdown after numerous timeout expiries. Have you tried bisecting between systemd 252 and 253 to locate what triggers the issue? Being able to reproduce the issue on Fedora would indicate it is an upstream issue rather than a packaging issue. Have you reported it to the systemd developers?- I have left it for more than 40 minutes in one occasion, reboot/shutdown did not complete.
- I have no idea how to bisect.
- Fedora just like Arch updated both kernel and systemd versions, experienced the same issue (not rebooting or powering off) after that. But on Fedora all I was seeing was splash screen, couldn't see any outputs.
See [1] for a guide to bisecting with git. See [2] for the upstream systemd issue tracker.
[1] https://wiki.archlinux.org/title/Bisecting_bugs_with_Git
[2] https://github.com/systemd/systemd/issues
Either way, the above means it's not an Arch packaging bug. It looks like a kernel or maybe a systemd regression. Please use the proper support channels (Forum/IRC/Mailing Lists/Reddit/etc) to see if anyone can assist further. @loqs has already steered you in the right direction.
If you are running libvirt, one related upstream issue is [1] (because both Arch and Fedora are affected by this, and even though it hasn't been mentioned, shutdown problems seem likely).
[1] https://github.com/systemd/systemd/issues/27953