Home / ubuntu / Questions / 1380024
In Process
alchemy
Asked: 2021-12-09 21:57:29 +0800 CST

Why doesn't 'systemctl reboot' work?

  • 772

Why dont these commands work in Kubuntu 20.04? Applications shut down and the screen goes black, but it never finishes poweroff. Any ideas?

systemctl poweroff
systemctl reboot

https://askubuntu.com/a/479368/795299

I should clarify.. the regular GUI restart and shutdown buttons work fine. The regular CLI commands (reboot and shutdown -H now) also don't work. But they were and I was concerned they are more abrupt, not giving applications time to save and close.

Here are some errors from journalctl -r (reverse order):

Dec 10 14:21:31 osboxes kernel: Fixing recursive fault but reboot is needed!
...theres a big chunk of what looks like machine code numbers for the kernel here...
Dec 10 14:21:31 osboxes kernel: CPU: 13 PID: 2635 Comm: QQmlThread Tainted: P           OE     5.4.0-91-generic #102-Ubuntu
Dec 10 14:21:31 osboxes kernel: Oops: 0010 [#1] SMP PTI
Dec 10 14:21:31 osboxes kernel: PGD 0 P4D 0 
Dec 10 14:21:31 osboxes kernel: #PF: error_code(0x0010) - not-present page
Dec 10 14:21:31 osboxes kernel: #PF: supervisor instruction fetch in kernel mode
Dec 10 14:21:31 osboxes kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000
Dec 10 14:21:31 osboxes pulseaudio[7418]: GetManagedObjects() failed: org.freedesktop.systemd1.ShuttingDown: Refusing activation, D-Bus is shutting down.
Dec 10 14:21:31 osboxes dbus-daemon[1171]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Refusing activation, D-Bus is shutting down.
Dec 10 14:21:31 osboxes dbus-daemon[1171]: [system] Activation via systemd failed for unit 'rtkit-daemon.service': Refusing activation, D-Bus is shutting down.
...this error repeats for 10 dbus-daemon messages...
Dec 10 14:21:28 osboxes dbus-daemon[2354]: [session uid=1001 pid=2354] Activated service 'org.kde.kglobalaccel' failed: Process org.kde.kglobalaccel received signal 6
Dec 10 14:21:28 osboxes org.kde.kglobalaccel[7171]: Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposi>
Dec 10 14:21:28 osboxes org.kde.kglobalaccel[7171]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Dec 10 14:21:28 osboxes org.kde.kglobalaccel[7171]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
..no errors for about 15 lines..
Dec 10 14:21:28 osboxes systemd[1]: Stopped ACPI event daemon.
Dec 10 14:21:28 osboxes systemd[1]: acpid.service: Succeeded.
Dec 10 14:21:28 osboxes org.kde.kglobalaccel[7171]: qt.qpa.xcb: could not connect to display :0
Dec 10 14:21:27 osboxes kernel: snd_hda_codec_hdmi hdaudioC1D1: HDMI: invalid ELD data byte 9
Dec 10 14:21:27 osboxes systemd[1]: finalrd.service: Succeeded.
Dec 10 14:21:27 osboxes systemd[1]: Failed unmounting /media/abc/VHDs.
..added below errors..
Dec 10 17:55:40 osboxes systemd-udevd[16858]: veth5ed07fa: Failed to get link config: No such device
Dec 10 17:55:40 osboxes systemd-tmpfiles[17063]: [/run/finalrd-libs.conf:9] Duplicate line for path "/run/initramfs/lib64", ignoring.
Dec 10 17:55:40 osboxes libvirtd[1290]: unable to read: /sys/class/net/veth5ed07fa/operstate: No such file or directory
Dec 10 17:55:40 osboxes libvirtd[1290]: Failed to open file '/sys/class/net/veth5ed07fa/operstate': No such file or directory

The unmounting error is from a symlink to the docker directory onto a data partition. Disabling the mountpoint in fstab didnt resolve.

It looks like the last message is acpi related: Error "fixing recursive fault but reboot is needed". But using acpi noirq didn't resolve.

Comparing journalctl between using the restart button from the desktop which succeeds, I find there are similar dbus-daemon messages, and umounting error, but no kerner bug error. There is a "NVIDIA ACPI Video Driver.. failed with exit code", but it still succeeds.

reboot does work from tty2 if I dont log in from sddm as user first.

bash

1 Answers

  1. This does not answer Why doesn't 'systemctl reboot' work?, but it may solve your problem.

    Try with

    $ sudo shutdown
$ sudo shutdown -r

    You could configure your system so you don't need sudo as well.

    Yet another option is to add acpi=noirq to the grub line.

    A possible cause is Nvidia drivers.

    To dig a little further, please read and post the output of journalctl that includes a failed shutdown/reboot, with

    $ journalctl --list-boots > boots.txt
$ journalctl --no-pager -b > boot_minus0.txt
$ journalctl --no-pager -b -1 > boot_minus1.txt
...

    This creates files that you can later upload to pastebin. Make your effort in inspecting them.

    Related:

    1. https://www.debian.org/releases/buster/amd64/ch08s01.en.html
    • 1