Can't shut down Arch. Reaches state Reached target System Power Off

borealis69 · 2024-05-31 19:15:43

Hi .... yes,

Can't shut down arch. Arch reaches state:

[OK] Reached target Umount All Filesystems
[OK] Reached target Late Shutdown Services
[OK] Finished System Power Off
[      93.437339] reboot: Power down

After it reaches this state it just freezes and doesn't shut down.

Latest log has just this error in it, which also appeared when i was in the install media of arch, but i just ignored ... maybe thats why it doest shut down:

hub 8-0:1.0: config failed, hub doesn't have any ports! (err -19)

usb-devices displays this for usb 8. Driver(none) .. not gud, innit?:

T:  Bus=08 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 0
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev=06.09
S:  Manufacturer=Linux 6.9.2-arch1-1 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=0000:10:00.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=(none)
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

I've tried suspending usb autosuspend. Doesnt work.... please help?

UPDATE:
I've also tried updating BIOS to no avail. Literally nothing changed. Same shit, differet BIOS version.

I'm on desktop PC. Motherboard is asrock b650m-hdv/m.2. It's using latest BIOS version, at least now it is.
When it reaches that semi powered off state, the keyboard is disabled along with the mouse, they do not work. The screen freezes at this and doesn't change picture:

[OK] Reached target Umount All Filesystems
[OK] Reached target Late Shutdown Services
[OK] Finished System Power Off
[      93.437339] reboot: Power down

Also the fans keep spinning along with the RGB, and RAM RGB. The power button LED is working as if the PC is turned on.

There is no parallel windows installation. PC has only Arch as OS. I'm using xorg, also don't have xorg-xinit installed. I'm using GNOME desktop environment.
PC pretty much runs 100% fine, just can't power it off.

Result of sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st is:
https://0x0.st/XN5i.txt

Last edited by borealis69 (2024-06-01 11:29:23)

mesaprotector · 2024-05-31 22:26:17

It could be the USB hub (if it is, you probably want autosuspend on) but there are a lot of possibilities.

Are you on a desktop or laptop? Are there any lights still on when your computer freezes (backlight, caps lock LED, etc.)?

seth · 2024-05-31 22:35:59

Please use [code][/code] tags. Edit your post in this regard.

The system does shut down, but the ACPI call to power off fails.

Is there a parallel windows installation?
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Please post your complete system journal for the previous boot:

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

borealis69 · 2024-06-01 11:21:59

I'm on desktop PC. Motherboard is asrock b650m-hdv/m.2. It's using latest BIOS version, at least now it is.
When it reaches that semi powered off state, the keyboard is disabled along with the mouse, they do not work. The screen freezes at this and doesn't change picture:

[OK] Reached target Umount All Filesystems
[OK] Reached target Late Shutdown Services
[OK] Finished System Power Off
[      93.437339] reboot: Power down

Also the fans keep spinning along with the RGB, and RAM RGB. The power button LED is working as if the PC is turned on.

There is no parallel windows installation. PC has only Arch as OS. I'm using xorg, also don't have xorg-xinit installed. I'm using GNOME desktop environment.
PC pretty much runs 100% fine, just can't power it off.

Last edited by borealis69 (2024-06-01 11:26:50)

seth · 2024-06-01 11:59:02

seth wrote:

Please post your complete system journal for the previous boot:
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

It's gonna be helpful to have an oversight over the general hardware and if any issues hint up, that's gonna be long before the end of the journal.
As mentioned, the system shuts down fine - you're ending at this thing here:

Last edited by seth (2024-06-01 11:59:13)

borealis69 · 2024-06-01 14:34:15

I don't wish to turn off my PC manually. I WANT my OS to turn off my PC when I instruct it to poweroff. I want the OS to do what it supposed to. As for "oversight over the general hardware"...
I'm using a ryzen 5 7600, the above mentioned motherboard, rtx 2060 12gb, ram 32gb dual channel and bios is with default settings. (I have changed nothing on it)

I have posted the journal in my first post. I'll post it again here.
https://0x0.st/XN5i.txt

seth · 2024-06-01 14:43:12

I understand that, I'm just trying to explain the state of the system you're reaching.
And I obvously didn't notice your edit to your OP, but that journal ends with a suspend to RAM, not a shutdown?

Right off the bat, you're running NM and dhcpcd concurrently - disable the latter.
Also there's *possibly* a recent flare up reg. nvme's - try to disable APST, https://wiki.archlinux.org/title/Solid_ … leshooting
And there're pending issues w/ the nvidia 550xx drivers, https://bbs.archlinux.org/viewtopic.php … 3#p2174003 - try the 535xx drivers.

borealis69 · 2024-06-02 09:26:45

Hello again,
Just one quick correction about the journal. I remembered that I put my system in Suspend before turning it off manually via the power button.
Attached below is the most recent journal. I attempted to poweroff but as described before, it gets to powered off, but never physically powering off. I will attempt the suggested solutions later today.

https://0x0.st/XqiI.txt

seth · 2024-06-02 12:57:42

Jun 02 02:50:14 borealis systemd[1134]: session.slice: Consumed 1d 23h 42min 25.305s CPU time.
Jun 02 02:50:14 borealis systemd[1134]: Closed D-Bus User Message Bus Socket.
Jun 02 02:51:44 borealis systemd[1134]: app-gnome-net.lutris.Lutris-12289.scope: Stopping timed out. Killing.
Jun 02 02:51:44 borealis systemd[1134]: app-gnome-net.lutris.Lutris-12289.scope: Killing process 18171 (winedevice.exe) with signal SIGKILL.
Jun 02 02:51:44 borealis systemd[1134]: app-gnome-net.lutris.Lutris-12289.scope: Failed to kill control group /user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-net.lutris.Lutris-12289.scope, ignoring: Invalid argument
Jun 02 02:51:44 borealis systemd[1134]: app-gnome-net.lutris.Lutris-12289.scope: Failed with result 'timeout'.

In addition to the previous, lutris seems to be stalling the shutdown and there's a massive amount of

Jun 02 02:50:13 borealis dbus-broker-launch[606]: Activation request for 'org.freedesktop.UDisks2' failed.

througout the entire shutdown process

This might be down to the network misconfig, but you should probably try to explicitly quit lutris before the shutdown

Arch Linux

#1 2024-05-31 19:15:43

Can't shut down Arch. Reaches state Reached target System Power Off

#2 2024-05-31 22:26:17

Re: Can't shut down Arch. Reaches state Reached target System Power Off

#3 2024-05-31 22:35:59

Re: Can't shut down Arch. Reaches state Reached target System Power Off

#4 2024-06-01 11:21:59

Re: Can't shut down Arch. Reaches state Reached target System Power Off

#5 2024-06-01 11:59:02

Re: Can't shut down Arch. Reaches state Reached target System Power Off

#6 2024-06-01 14:34:15

Re: Can't shut down Arch. Reaches state Reached target System Power Off

#7 2024-06-01 14:43:12

Re: Can't shut down Arch. Reaches state Reached target System Power Off

#8 2024-06-02 09:26:45

Re: Can't shut down Arch. Reaches state Reached target System Power Off

#9 2024-06-02 12:57:42

Re: Can't shut down Arch. Reaches state Reached target System Power Off

Board footer