Arch Linux

beyonddevnull

Member

Registered: 2020-04-12

Posts: 4

(Updated) plasma restarts instead of powering off the computer.

Update:
When the machine boots up. Once I get to SDDM (login manager). If I do not log into plasma and just use the poweroff/shutdown GUI button. The machine powers off as expected.
I installed awesome-git from the AUR. Use SDDM to select awesomeWM (instead of plasma). Launch alacritty. Enter the "poweroff" command. Computer powers off as expected. I am interested in knowing what is causing this. Until then this accelerates my switching to awesome I guess.

(ORIGINAL POST BELOW)

When I attempt to power off the machine using "shut down" using the graphical plasma menu or for example the "poweroff" command through the terminal, the system will appear to mostly shut down. The system looks like it has mostly powered off from looking at the monitor, but LEDs on the mobo stay on. After a few moments with an empty screen, the fans ramp back up and the load sequence back to the system begins..

I would like help so that when I issue the expected shutdown or poweroff signals the system stays powered off as expected.

Searching on the wiki I have found references for issues possibly being the following and frequently without a clear solution or steps to remediate below
- laptop related (I have a desktop that I built).
- possible kernel bugs?
- systemd config for poweroff service thing having a reboot line in it for some reason
- usb3 acpi
- other unspecified hardware issues

I have a relatively new arch install (kernel 5.11.13-arch1-1) using SDDM/Plasma.
My motherboard is a B550 tomahawk, 5600x, and a 6800XT.

Here is the journalctl log right before the new -- Boot appears

Apr 14 11:12:32 eagleeye systemd[1]: Reached target Shutdown.
Apr 14 11:12:32 eagleeye systemd[1]: Reached target Final Step.
Apr 14 11:12:32 eagleeye systemd[1]: systemd-poweroff.service: Deactivated successfully.
Apr 14 11:12:32 eagleeye systemd[1]: Finished Power-Off.
Apr 14 11:12:32 eagleeye audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-poweroff comm="s>
Apr 14 11:12:32 eagleeye audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-poweroff comm="sy>
Apr 14 11:12:32 eagleeye systemd[1]: Reached target Power-Off.
Apr 14 11:12:32 eagleeye systemd[1]: Shutting down.
Apr 14 11:12:32 eagleeye audit: BPF prog-id=13 op=UNLOAD
Apr 14 11:12:32 eagleeye audit: BPF prog-id=12 op=UNLOAD
Apr 14 11:12:32 eagleeye audit: BPF prog-id=11 op=UNLOAD
Apr 14 11:12:32 eagleeye audit: BPF prog-id=16 op=UNLOAD
Apr 14 11:12:32 eagleeye audit: BPF prog-id=15 op=UNLOAD
Apr 14 11:12:32 eagleeye audit: BPF prog-id=14 op=UNLOAD
Apr 14 11:12:32 eagleeye systemd-shutdown[1]: Syncing filesystems and block devices.
Apr 14 11:12:32 eagleeye systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Apr 14 11:12:32 eagleeye systemd-journald[525]: Journal stopped
-- Boot 

After this sequence is completed, the LEDs on the mobo case remain on but the screen goes dark. After a period of time (10-ish seconds?)  the fans ramp up and it loads back to grub.

I am a bit stuck on debugging this. Hoping for some instructions on how to begin debugging this and a path to resolution.

Thanks in advance.

Last edited by beyonddevnull (2021-04-15 13:34:11)