Kernel 7.0 broke the ACPI poweroff?

vangeancexyz · 2026-05-23 15:52:53

My computer doesn't shut down completely. The operating system and kernel get terminated (I was told that when the caps lock key turns off, the kernel has been unloaded and shut down), but the computer keeps running and the only way to turn it off is by pressing and holding the power button.

Im using kernel 7.0.5-arch1-1 and this bug happens on the Hyprland desktop environment. I use GRUB and I can't perfectly reproduce the problem in the kernel logs, because both seem to have the same pattern: on kernel 7.0.5-arch1-1 it says it shut down but stays on, while on kernel 6.18.32-2-lts it shuts down completely. The problem on the newer kernel happens sometimes and other times it shuts down just fine. It has nothing to do with updates (sometimes I run pacman -Syu before shutting down, other times I don't, and that seems unrelated to the problem) or with resource usage during the shutdown process.

Logs 7.0.5-arch1-1: https://pastebin.com/zANYMeMk
Logs 6.18.32-2-lts: https://pastebin.com/aFqQz0Gb

I dual boot with CachyOS with KDE/COSMIC (but i use arch for my daily use) and the same thing happens there with different kernels, just like it happens on arch.

My computer:
~ ❯ inxi -b
System:
Host: sunshine Kernel: 7.0.9-zen2-1-zen arch: x86_64 bits: 64
Desktop: Hyprland v: 0.55.0 Distro: Arch Linux
Machine:
Type: Desktop Mobo: INTEL model: H61 serial: <superuser required>
Firmware: UEFI vendor: American Megatrends v: 4.6.5 date: 11/10/2022
CPU:
Info: quad core Intel Core i5-2400 [MCP] speed (MHz): avg: 1746
min/max: 1600/3400
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Lexa PRO [Radeon
540/540X/550/550X / RX 540X/550/550X] driver: amdgpu v: kernel
Display: wayland server: X.org v: 1.21.1.22 with: Xwayland v: 24.1.11
compositor: Hyprland v: 0.55.0 driver: X: loaded: modesetting dri: radeonsi
gpu: amdgpu resolution: 1920x1080~100Hz
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Info: Tools: wl: nwg-displays x11: xprop,xrandr
Network:
Device-1: Intel Wireless 7265 driver: iwlwifi
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
driver: r8169
Device-3: Sony DualSense wireless controller (PS5)
driver: playstation,snd-usb-audio,usbhid type: USB
Drives:
Local Storage: total: 1.67 TiB used: 813.39 GiB (47.5%)
Info:
Memory: total: 16 GiB available: 15.56 GiB used: 2.26 GiB (14.5%)
Processes: 266 Uptime: 2m Shell: Zsh inxi: 3.3.40

~ ❯ find /boot/vmli*
/boot/vmlinuz-linux
/boot/vmlinuz-linux-lts
/boot/vmlinuz-linux-zen

In case you want to see the kernel logs on CachyOS:
Logs 7.0.9-1-cachyos: https://pastebin.com/Zxu25hgG
Logs 6.18.32-1-cachyos-lts: https://pastebin.com/p0V2KjhR
(sorry in advance for posting another operating system on the Arch forum)

BIGBEASTISHANK · 2026-05-23 15:54:44

Bro crazy see this
https://bbs.archlinux.org/viewtopic.php … 5#p2298515

Need to know something, name of laptop please

Last edited by BIGBEASTISHANK (2026-05-23 15:55:44)

cryptearth · 2026-05-23 16:35:31

BIGBEASTISHANK wrote:

Need to know something, name of laptop please

it's a H61 board with a 2400 and a rx500 - all needed info - that's a desktop, no laptop

@OP
since 7.0 i noticed that my system (also desktop, msi b550-a pro, 5600, rx7700) sometimes has issues, too - but not shutdown but warm reboot
i usually update and reboot as first action - when i'm too fast i noticed the shutdown is slow and when it finally finishes it hangs on actual warm reboot requires hard reset; shutdown however worked without issues yet

could be something with 7.0 - could be a coincidence
haven't tested with lts yet as hard to active reproduce

vangeancexyz · 2026-05-23 16:44:36

BIGBEASTISHANK wrote:

Bro crazy see this
https://bbs.archlinux.org/viewtopic.php … 5#p2298515
Need to know something, name of laptop please

I read the whole thing, but apparently your problem was with the laptop's hardware; mine is a desktop.

The problem is identical to mine in behavior, but the cause is different: in your case it's a new MSI laptop with a firmware bug. In my case it's an Intel H61 desktop with an AMI BIOS from 2009/2022

vangeancexyz · 2026-05-23 16:53:53

cryptearth wrote:

BIGBEASTISHANK wrote:
Need to know something, name of laptop please
it's a H61 board with a 2400 and a rx500 - all needed info - that's a desktop, no laptop
@OP
since 7.0 i noticed that my system (also desktop, msi b550-a pro, 5600, rx7700) sometimes has issues, too - but not shutdown but warm reboot
i usually update and reboot as first action - when i'm too fast i noticed the shutdown is slow and when it finally finishes it hangs on actual warm reboot requires hard reset; shutdown however worked without issues yet
could be something with 7.0 - could be a coincidence
haven't tested with lts yet as hard to active reproduce

I’ve been using kernel 6.18; since my computer is a bit “older,” I’m not missing out on anything significant that kernel 7.0 offers, but I’m not sure if it’s really the kernel or just a coincidence, as you yourself said; even so, I’m waiting for a solution to revert to the previous version.

seth · 2026-05-23 20:19:20

@BIGBEASTISHANK
According to https://bbs.archlinux.org/viewtopic.php … 9#p2298519 the LTS kernel is affected for you as well while for the OP it seems a clear regression.

@vangeancexyz, 6.19.14 is also not affected?
I don't like LTS

May 23 11:57:40.564049 sunshine systemd[583]: sys-devices-pci0000:00-0000:00:01.0-0000:01:00.1-sound-card2-controlC2.device: Failed to enqueue SYSTEMD_USER_WANTS job, ignoring: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
May 23 11:57:40.565230 sunshine systemd[1]: sys-devices-pci0000:00-0000:00:01.0-0000:01:00.1-sound-card2-controlC2.device: Failed to enqueue SYSTEMD_WANTS job, ignoring: Transaction for sound.target/start is destructive (poweroff.target has 'start' job queued, but 'stop' is included in transaction).
May 23 11:57:40.572987 sunshine systemd[1]: sys-devices-pci0000:00-0000:00:1a.0-usb1-1\x2d1-1\x2d1.1-1\x2d1.1:1.0-sound-card0-controlC0.device: Failed to enqueue SYSTEMD_WANTS job, ignoring: Transaction for sound.target/start is destructive (poweroff.target has 'start' job queued, but 'stop' is included in transaction).
May 23 11:57:40.578468 sunshine systemd[1]: sys-devices-pci0000:00-0000:00:1a.0-usb1-1\x2d1-1\x2d1.3-1\x2d1.3:1.0-sound-card3-controlC3.device: Failed to enqueue SYSTEMD_WANTS job, ignoring: Transaction for sound.target/start is destructive (systemd-poweroff.service has 'start' job queued, but 'stop' is included in transaction).
May 23 11:57:40.578601 sunshine systemd[583]: sys-devices-pci0000:00-0000:00:1a.0-usb1-1\x2d1-1\x2d1.3-1\x2d1.3:1.0-sound-card3-controlC3.device: Failed to enqueue SYSTEMD_USER_WANTS job, ignoring: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).

7.0

May 23 11:51:54.703439 sunshine systemd[594]: Requested transaction contradicts existing jobs: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
May 23 11:51:54.703453 sunshine systemd[594]: sys-devices-pci0000:00-0000:00:1a.0-usb1-1\x2d1-1\x2d1.3-1\x2d1.3:1.0-sound-card1-controlC1.device: Failed to enqueue SYSTEMD_USER_WANTS job, ignoring: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
May 23 11:51:54.704483 sunshine systemd[1]: Requested transaction contradicts existing jobs: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
May 23 11:51:54.704491 sunshine systemd[1]: sys-devices-pci0000:00-0000:00:1a.0-usb1-1\x2d1-1\x2d1.3-1\x2d1.3:1.0-sound-card1-controlC1.device: Failed to enqueue SYSTEMD_WANTS job, ignoring: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
May 23 11:51:54.705874 sunshine systemd[1]: Requested transaction contradicts existing jobs: Transaction for systemd-rfkill.socket/start is destructive (systemd-poweroff.service has 'start' job queued, but 'stop' is included in transaction).
May 23 11:51:54.705881 sunshine systemd[1]: sys-devices-virtual-misc-rfkill.device: Failed to enqueue SYSTEMD_WANTS job, ignoring: Transaction for systemd-rfkill.socket/start is destructive (systemd-poweroff.service has 'start' job queued, but 'stop' is included in transaction).
May 23 11:51:54.714426 sunshine systemd[1]: Requested transaction contradicts existing jobs: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
May 23 11:51:54.714436 sunshine systemd[1]: sys-devices-pci0000:00-0000:00:01.0-0000:01:00.1-sound-card3-controlC3.device: Failed to enqueue SYSTEMD_WANTS job, ignoring: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
May 23 11:51:54.721984 sunshine systemd[1]: Requested transaction contradicts existing jobs: Transaction for sound.target/start is destructive (systemd-poweroff.service has 'start' job queued, but 'stop' is included in transaction).
May 23 11:51:54.721993 sunshine systemd[1]: sys-devices-pci0000:00-0000:00:1a.0-usb1-1\x2d1-1\x2d1.1-1\x2d1.1:1.0-sound-card0-controlC0.device: Failed to enqueue SYSTEMD_WANTS job, ignoring: Transaction for sound.target/start is destructive (systemd-poweroff.service has 'start' job queued, but 'stop' is included in transaction).

The execution order is different and the 7.0 kernel lacks a line - maybe exposes a race condition.
=> Get rid of that (test shutting down from the multi-user.target and also on of the cards seem a usb device, no idea why the shutdown tries to start the sound target)

BIGBEASTISHANK · 2026-05-23 20:40:23

vangeancexyz wrote:

I read the whole thing, but apparently your problem was with the laptop's hardware; mine is a desktop.

hey just want to clear it out and will update In my old post too, its software issue, which I have confirmed and right now I dont have any other solution then grub settings for mine

seth wrote:

the LTS kernel is affected for you as well

I am not on lts kernal, its some kind of werid glitch issue which is happning with dual boot i guess

@vangeancexyz Do you have dual boot or just linux?

vangeancexyz · 2026-05-25 23:19:58

seth wrote:

@BIGBEASTISHANK
According to https://bbs.archlinux.org/viewtopic.php … 9#p2298519 the LTS kernel is affected for you as well while for the OP it seems a clear regression.

@vangeancexyz, 6.19.14 is also not affected?
I don't like LTS

May 23 11:57:40.564049 sunshine systemd[583]: sys-devices-pci0000:00-0000:00:01.0-0000:01:00.1-sound-card2-controlC2.device: Failed to enqueue SYSTEMD_USER_WANTS job, ignoring: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
May 23 11:57:40.565230 sunshine systemd[1]: sys-devices-pci0000:00-0000:00:01.0-0000:01:00.1-sound-card2-controlC2.device: Failed to enqueue SYSTEMD_WANTS job, ignoring: Transaction for sound.target/start is destructive (poweroff.target has 'start' job queued, but 'stop' is included in transaction).
May 23 11:57:40.572987 sunshine systemd[1]: sys-devices-pci0000:00-0000:00:1a.0-usb1-1\x2d1-1\x2d1.1-1\x2d1.1:1.0-sound-card0-controlC0.device: Failed to enqueue SYSTEMD_WANTS job, ignoring: Transaction for sound.target/start is destructive (poweroff.target has 'start' job queued, but 'stop' is included in transaction).
May 23 11:57:40.578468 sunshine systemd[1]: sys-devices-pci0000:00-0000:00:1a.0-usb1-1\x2d1-1\x2d1.3-1\x2d1.3:1.0-sound-card3-controlC3.device: Failed to enqueue SYSTEMD_WANTS job, ignoring: Transaction for sound.target/start is destructive (systemd-poweroff.service has 'start' job queued, but 'stop' is included in transaction).
May 23 11:57:40.578601 sunshine systemd[583]: sys-devices-pci0000:00-0000:00:1a.0-usb1-1\x2d1-1\x2d1.3-1\x2d1.3:1.0-sound-card3-controlC3.device: Failed to enqueue SYSTEMD_USER_WANTS job, ignoring: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).

7.0

May 23 11:51:54.703439 sunshine systemd[594]: Requested transaction contradicts existing jobs: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
May 23 11:51:54.703453 sunshine systemd[594]: sys-devices-pci0000:00-0000:00:1a.0-usb1-1\x2d1-1\x2d1.3-1\x2d1.3:1.0-sound-card1-controlC1.device: Failed to enqueue SYSTEMD_USER_WANTS job, ignoring: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
May 23 11:51:54.704483 sunshine systemd[1]: Requested transaction contradicts existing jobs: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
May 23 11:51:54.704491 sunshine systemd[1]: sys-devices-pci0000:00-0000:00:1a.0-usb1-1\x2d1-1\x2d1.3-1\x2d1.3:1.0-sound-card1-controlC1.device: Failed to enqueue SYSTEMD_WANTS job, ignoring: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
May 23 11:51:54.705874 sunshine systemd[1]: Requested transaction contradicts existing jobs: Transaction for systemd-rfkill.socket/start is destructive (systemd-poweroff.service has 'start' job queued, but 'stop' is included in transaction).
May 23 11:51:54.705881 sunshine systemd[1]: sys-devices-virtual-misc-rfkill.device: Failed to enqueue SYSTEMD_WANTS job, ignoring: Transaction for systemd-rfkill.socket/start is destructive (systemd-poweroff.service has 'start' job queued, but 'stop' is included in transaction).
May 23 11:51:54.714426 sunshine systemd[1]: Requested transaction contradicts existing jobs: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
May 23 11:51:54.714436 sunshine systemd[1]: sys-devices-pci0000:00-0000:00:01.0-0000:01:00.1-sound-card3-controlC3.device: Failed to enqueue SYSTEMD_WANTS job, ignoring: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
May 23 11:51:54.721984 sunshine systemd[1]: Requested transaction contradicts existing jobs: Transaction for sound.target/start is destructive (systemd-poweroff.service has 'start' job queued, but 'stop' is included in transaction).
May 23 11:51:54.721993 sunshine systemd[1]: sys-devices-pci0000:00-0000:00:1a.0-usb1-1\x2d1-1\x2d1.1-1\x2d1.1:1.0-sound-card0-controlC0.device: Failed to enqueue SYSTEMD_WANTS job, ignoring: Transaction for sound.target/start is destructive (systemd-poweroff.service has 'start' job queued, but 'stop' is included in transaction).

The execution order is different and the 7.0 kernel lacks a line - maybe exposes a race condition.
=> Get rid of that (test shutting down from the multi-user.target and also on of the cards seem a usb device, no idea why the shutdown tries to start the sound target)

I completely reinstalled Arch and removed the dual boot, which solved the problem. Since I also needed to format the computer, it now shuts down normally in kernel 7.0.X.

In a way, there isn't a plausible "solution," but should I still mark this post as "solved"?

Last edited by vangeancexyz (2026-05-25 23:20:57)

seth · 2026-05-26 05:33:55

Do you currently still get any of the sound.target related errors on shutdown?

BIGBEASTISHANK · 2026-05-26 06:33:49

vangeancexyz wrote:

I completely reinstalled Arch and removed the dual boot, which solved the problem.

Yaa dual boot is having issue i guess

vangeancexyz · 2026-05-26 18:48:53

seth wrote:

Do you currently still get any of the sound.target related errors on shutdown?

yes, they still appear in the logs, but the computer shuts down

Arch Linux

#1 2026-05-23 15:52:53

Kernel 7.0 broke the ACPI poweroff?

#2 2026-05-23 15:54:44

Re: Kernel 7.0 broke the ACPI poweroff?

#3 2026-05-23 16:35:31

Re: Kernel 7.0 broke the ACPI poweroff?

#4 2026-05-23 16:44:36

Re: Kernel 7.0 broke the ACPI poweroff?

#5 2026-05-23 16:53:53

Re: Kernel 7.0 broke the ACPI poweroff?

#6 2026-05-23 20:19:20

Re: Kernel 7.0 broke the ACPI poweroff?

#7 2026-05-23 20:40:23

Re: Kernel 7.0 broke the ACPI poweroff?

#8 2026-05-25 23:19:58

Re: Kernel 7.0 broke the ACPI poweroff?

#9 2026-05-26 05:33:55

Re: Kernel 7.0 broke the ACPI poweroff?

#10 2026-05-26 06:33:49

Re: Kernel 7.0 broke the ACPI poweroff?

#11 2026-05-26 18:48:53

Re: Kernel 7.0 broke the ACPI poweroff?

Board footer