Shutdown problem with kernels 6.15 and 6.16

After the last Manjaro update to kernel 6.15.3-1, the following happens:
I shut down the computer (via the GUI or via systemctl poweroff).
As soon as I move the mouse or press a key, the computer starts up again.
I don’t have this problem with kernel 6.12.34-1!

System:
  Kernel: 6.15.3-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.15-x86_64
    root=UUID=9d81fcf2-9aa2-4e1d-9f3e-61092f4c896c rw rootflags=subvol=@
    nvidia_drm.modeset=1 nvidia_drm.fbdev=1 nvidia.NVreg_EnableGpuFirmware=0
    nvidia.NVreg_PreserveVideoMemoryAllocations=1 quiet splash
    udev.log_priority=3
  Desktop: KDE Plasma v: 6.3.5 tk: Qt v: N/A info: frameworks v: 6.15.0
    wm: kwin_wayland vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: Megaport product: Hypnos v: 284698
    serial: <superuser required>
  Mobo: Gigabyte model: Z690 GAMING X DDR4 v: x.x
    serial: <superuser required> part-nu: 119-DE uuid: <superuser required>
    UEFI: American Megatrends LLC. v: F31b date: 05/16/2025
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 32 GiB available: 31.17 GiB used: 7.69 GiB (24.7%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB slots: 4 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: DDR4-A1 type: no module installed
  Device-2: DDR4-A2 type: DDR4 detail: synchronous size: 16 GiB
    speed: 2133 MT/s volts: curr: 1 min: 1 max: 1.35 width (bits): data: 64
    total: 64 manufacturer: Corsair part-no: CMH32GX4M2E3200C16 serial: N/A
  Device-3: DDR4-B1 type: no module installed
  Device-4: DDR4-B2 type: DDR4 detail: synchronous size: 16 GiB
    speed: 2133 MT/s volts: curr: 1 min: 1 max: 1.35 width (bits): data: 64
    total: 64 manufacturer: Corsair part-no: CMH32GX4M2E3200C16 serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: 12th Gen Intel Core i9-12900K bits: 64 type: MST AMCP
    arch: Alder Lake gen: core 12 level: v3 note: check built: 2021+
    process: Intel 7 (10nm ESF) family: 6 model-id: 0x97 (151) stepping: 2
    microcode: 0x3A
  Topology: cpus: 1x dies: 1 clusters: 10 cores: 16 threads: 24 mt: 8 tpc: 2
    st: 8 smt: enabled cache: L1: 1.4 MiB desc: d-8x32 KiB, 8x48 KiB; i-8x32
    KiB, 8x64 KiB L2: 14 MiB desc: 8x1.2 MiB, 2x2 MiB L3: 30 MiB
    desc: 1x30 MiB
  Speed (MHz): avg: 4900 min/max: 800/5100:5200:3900 scaling:
    driver: intel_pstate governor: powersave cores: 1: 4900 2: 4900 3: 4900
    4: 4900 5: 4900 6: 4900 7: 4900 8: 4900 9: 4900 10: 4900 11: 4900 12: 4900
    13: 4900 14: 4900 15: 4900 16: 4900 17: 4900 18: 4900 19: 4900 20: 4900
    21: 4900 22: 4900 23: 4900 24: 4900 bogomips: 152985
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_lbr arch_perfmon art avx avx2 avx_vnni bmi1 bmi2
    bts clflush clflushopt clwb cmov constant_tsc cpuid cpuid_fault cx16 cx8
    de ds_cpl dtes64 dtherm dts ept ept_ad erms est f16c flexpriority
    flush_l1d fma fpu fsgsbase fsrm fxsr gfni hfi ht hwp hwp_act_window
    hwp_epp hwp_notify hwp_pkg_req ibpb ibrs ibrs_enhanced ibt ida intel_pt
    invpcid lahf_lm lm mca mce md_clear mmx monitor movbe movdir64b movdiri
    msr mtrr nonstop_tsc nopl nx ospke pae pat pbe pcid pclmulqdq pconfig
    pdcm pdpe1gb pebs pge pku pln pni popcnt pse pse36 pts rdpid rdrand
    rdseed rdtscp rep_good sdbg sep serialize sha_ni smap smep smx
    split_lock_detect ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm
    tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer tsc_known_freq umip
    user_shstk vaes vme vmx vnmi vpclmulqdq vpid waitpkg x2apic xgetbv1 xsave
    xsavec xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling mitigation: Clear Register File
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB:
    conditional; PBRSB-eIBRS: SW sequence; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA AD102 [GeForce RTX 4090] vendor: CardExpert driver: nvidia
    v: 575.64 alternate: nouveau,nova_core,nvidia_drm non-free: 550-570.xx+
    status: current (as of 2025-04) arch: Lovelace code: AD1xx
    process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16
    ports: active: none off: DP-2,DP-3,HDMI-A-1 empty: DP-1 bus-ID: 01:00.0
    chip-ID: 10de:2684 class-ID: 0300
  Device-2: Razer USA Kiyo Pro driver: snd-usb-audio,uvcvideo type: USB
    rev: 3.2 speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 2-5:4
    chip-ID: 1532:0e05 class-ID: 0102
  Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_wayland driver: X: loaded: modesetting,nvidia
    unloaded: nouveau alternate: fbdev,nv,vesa dri: iris
    gpu: nvidia,nvidia-nvswitch d-rect: 9600x2880 display-ID: 0
  Monitor-1: DP-2 pos: primary,top-left model: LG (GoldStar) ULTRAGEAR+
    serial: <filter> built: 2024 res: mode: 3840x2160 hz: 144 scale: 150% (1.5)
    to: 2560x1440 dpi: 163 gamma: 1.2 chroma: red: x: 0.675 y: 0.322 green:
    x: 0.255 y: 0.690 blue: x: 0.141 y: 0.059 white: x: 0.314 y: 0.329
    size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9
    modes: 3840x2160, 2560x1440, 1920x1080, 1280x1024, 1280x720, 1024x768,
    800x600, 720x480, 640x480
  EDID-Warnings: 1: parse_edid: unknown tag 112
  Monitor-2: DP-3 pos: top-center model: LG (GoldStar) ULTRAGEAR+
    serial: <filter> built: 2024 res: mode: 3840x2160 hz: 144 scale: 150% (1.5)
    to: 2560x1440 dpi: 163 gamma: 1.2 chroma: red: x: 0.675 y: 0.322 green:
    x: 0.255 y: 0.690 blue: x: 0.141 y: 0.059 white: x: 0.314 y: 0.329
    size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9
    modes: 3840x2160, 2560x1440, 1920x1080, 1280x1024, 1280x720, 1024x768,
    800x600, 720x480, 640x480
  EDID-Warnings: 1: parse_edid: unknown tag 112
  Monitor-3: HDMI-A-1 pos: bottom-r model: 12.3FHD serial: <filter>
    built: 2023 res: mode: 1920x720 hz: 60 scale: 100% (1) dpi: 157 gamma: 1.2
    chroma: red: x: 0.596 y: 0.341 green: x: 0.318 y: 0.569 blue: x: 0.153
    y: 0.129 white: x: 0.314 y: 0.329 size: 310x128mm (12.2x5.04")
    diag: 335mm (13.2") modes: 1920x720, 1600x900, 1680x720, 1280x720,
    1024x768, 800x600, 640x480
  EDID-Warnings: 1: parse_edid: unhandled CEA mode 69 2: parse_edid:
    unhandled CEA mode 83 3: parse_edid: unhandled CEA mode 108 4: parse_edid:
    unhandled CEA mode 110 5: parse_edid: unhandled CEA mode 68 6: parse_edid:
    unhandled CEA mode 83
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
    x11: drv: nvidia inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 575.64
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
    memory: 23.43 GiB display-ID: :0.0
  API: Vulkan v: 1.4.313 layers: 6 device: 0 type: discrete-gpu
    name: NVIDIA GeForce RTX 4090 driver: nvidia v: 575.64 device-ID: 10de:2684
    surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: Gigabyte driver: snd_hda_intel
    v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl bus-ID: 00:1f.3
    chip-ID: 8086:7ad0 class-ID: 0403
  Device-2: NVIDIA AD102 High Definition Audio vendor: CardExpert
    driver: snd_hda_intel v: kernel alternate: nova_core pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:22ba class-ID: 0403
  Device-3: Razer USA Leviathan V2 driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-11.2:21
    chip-ID: 1532:0532 class-ID: 0300 serial: <filter>
  Device-4: Razer USA Kraken V3 Pro
    driver: cdc_acm,hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-11.3:13 chip-ID: 1532:052c
    class-ID: 0a00
  Device-5: Razer USA Kiyo Pro driver: snd-usb-audio,uvcvideo type: USB
    rev: 3.2 speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 2-5:4
    chip-ID: 1532:0e05 class-ID: 0102
  API: ALSA v: k6.15.3-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.5 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 05:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Device-2: Intel Wi-Fi 5 Wireless-AC 9x6x [Thunder Peak] driver: iwlwifi
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 06:00.0
    chip-ID: 8086:2526 class-ID: 0280
  IF: wlp6s0 state: down mac: <filter>
  Info: services: NetworkManager,systemd-timesyncd
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel Wireless-AC 9260 Bluetooth Adapter driver: btusb v: 0.8
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-12.1:16
    chip-ID: 8087:0025 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 5.5 TiB used: 287.61 GiB (5.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: MZVL22T0HBLB-00B00 size: 1.86 TiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: GXB7801Q temp: 47.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:1 vendor: Samsung model: SSD 980 PRO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 5B2QGXA7 temp: 44.9 C
    scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Crucial model: CT2000MX500SSD1
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B type: USB rev: 3.1
    spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
    scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 100 GiB size: 100 GiB (100.00%) used: 20.77 GiB (20.8%)
    fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:4 label: ROOT
    uuid: 9d81fcf2-9aa2-4e1d-9f3e-61092f4c896c
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 616 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:3 label: N/A
    uuid: 5BD7-2146
  ID-3: /home raw-size: 1.77 TiB size: 3.58 TiB (203.08%)
    used: 266.84 GiB (7.3%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:5
    label: HOME uuid: aefb8dbd-52a6-44c5-95b8-e62a8a5735cd
  ID-4: /var/cache raw-size: 100 GiB size: 100 GiB (100.00%)
    used: 20.77 GiB (20.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:4
    label: ROOT uuid: 9d81fcf2-9aa2-4e1d-9f3e-61092f4c896c
  ID-5: /var/log raw-size: 100 GiB size: 100 GiB (100.00%)
    used: 20.77 GiB (20.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:4
    label: ROOT uuid: 9d81fcf2-9aa2-4e1d-9f3e-61092f4c896c
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/nvme1n1p1 maj-min: 259:2 size: 1.82 TiB fs: btrfs label: HOME
    uuid: aefb8dbd-52a6-44c5-95b8-e62a8a5735cd
  ID-2: /dev/sda1 maj-min: 8:1 size: 1.82 TiB fs: exfat label: Extern
    uuid: 7FF7-623A
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-4:2 info: VIA Labs USB2.0 Hub ports: 5 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 2109:2822
    class-ID: 0900
  Hub-3: 1-4.4:5 info: VIA Labs USB2.0 Hub ports: 5 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 2109:2822
    class-ID: 0900
  Device-1: 1-4.4.2:20 info: Cadwell Laboratories TouchScreen type: HID
    driver: hid-generic,hid-multitouch,usbhid interfaces: 3 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 200mA
    chip-ID: 27c0:0859 class-ID: 0300 serial: <filter>
  Device-2: 1-4.4.5:19 info: VIA Labs USB Billboard Device type: billboard
    driver: N/A interfaces: 1 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
    mode: 2.0 power: 100mA chip-ID: 2109:8818 class-ID: 1100 serial: <filter>
  Device-3: 1-4.5:8 info: VIA Labs USB Billboard Device type: billboard
    driver: N/A interfaces: 1 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
    mode: 2.0 power: 100mA chip-ID: 2109:8818 class-ID: 1100 serial: <filter>
  Hub-4: 1-5:3 info: Fresco Logic USB2.0 Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d5c:5011
    class-ID: 0900
  Hub-5: 1-5.3:6 info: Terminus USB 2.0 Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 1a40:0801 class-ID: 0900
  Device-1: 1-7:4 info: Razer USA Huntsman V2 type: keyboard,mouse,HID
    driver: razerkbd,usbhid interfaces: 5 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 power: 500mA chip-ID: 1532:026c class-ID: 0300
  Device-2: 1-8:7 info: Razer USA Tartarus V2 type: keyboard,mouse
    driver: razerkbd,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 1532:022b class-ID: 0300
  Hub-6: 1-11:11 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Device-1: 1-11.2:21 info: Razer USA Leviathan V2 type: audio,HID
    driver: hid-generic,snd-usb-audio,usbhid interfaces: 3 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 1532:0532 class-ID: 0300 serial: <filter>
  Device-2: 1-11.3:13 info: Razer USA Kraken V3 Pro
    type: audio,keyboard,abstract (modem),CDC-data
    driver: cdc_acm,hid-generic,snd-usb-audio,usbhid interfaces: 6 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 1532:052c class-ID: 0a00
  Device-3: 1-11.4:15 info: Razer USA Basilisk V3 Pro type: mouse,keyboard
    driver: razermouse,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 1532:00ab class-ID: 0301
    serial: <filter>
  Hub-7: 1-12:12 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Device-1: 1-12.1:16 info: Intel Wireless-AC 9260 Bluetooth Adapter
    type: bluetooth driver: btusb interfaces: 2 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 8087:0025 class-ID: e001
  Device-2: 1-13:14 info: Integrated Express RGB LED Controller type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 048d:5702 class-ID: 0300
  Hub-8: 2-0:1 info: super-speed hub ports: 9 rev: 3.1
    speed: 20 Gb/s (2.33 GiB/s) lanes: 2 mode: 3.2 gen-2x2 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-9: 2-3:2 info: VIA Labs USB3.2 Hub ports: 4 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 2109:0822
    class-ID: 0900
  Hub-10: 2-3.4:5 info: VIA Labs USB3.2 Hub ports: 4 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 2109:0822
    class-ID: 0900
  Hub-11: 2-4:3 info: Fresco Logic USB3.0 Hub ports: 4 rev: 3.1
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d5c:5001
    class-ID: 0900
  Device-1: 2-4.4:6 info: ASMedia ASM1051E SATA 6Gb/s bridge ASM1053E
    ASM1153 3Gb/s ASM1153E bridge type: mass storage driver: uas interfaces: 1
    rev: 3.1 speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1
    chip-ID: 174c:55aa class-ID: 0806 serial: <filter>
  Device-2: 2-5:4 info: Razer USA Kiyo Pro type: video,audio
    driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 power: 896mA
    chip-ID: 1532:0e05 class-ID: 0102
Sensors:
  System Temperatures: cpu: 45.0 C mobo: 45.0 C
  Fan Speeds (rpm): cpu: 1421 fan-2: 0 fan-3: 0 fan-4: 796 fan-5: 1901
    fan-6: 1341
  Power: 12v: N/A 5v: N/A 3.3v: N/A vbat: 3.17
Repos:
  Packages: pm: pacman pkgs: 1501 libs: 368 tools: pamac,yay
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: http://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
    2: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
    3: https://manjaro.kurdy.org/stable/$repo/$arch
    4: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
    5: https://ftp.halifax.rwth-aachen.de/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 510
  1: cpu: 162% command: C:\Program pid: 4386 mem: 2775.1 MiB (8.6%)
  2: cpu: 28.8% command: /desktop
    started-by: C:\windows\system32\explorer.exe pid: 3691 mem: 211.4 MiB (0.6%)
  3: cpu: 23.0% command: wineserver pid: 3666 mem: 42.1 MiB (0.1%)
  4: cpu: 7.3% command: kwin_wayland pid: 1461 mem: 297.9 MiB (0.9%)
  5: cpu: 7.2% command: vivaldi-bin pid: 5019 mem: 283.9 MiB (0.8%)
  Memory top: 5 of 510
  1: mem: 2775.1 MiB (8.6%) command: C:\Program pid: 4386 cpu: 162%
  2: mem: 802.8 MiB (2.5%) command: plasmashell pid: 1627 cpu: 1.4%
  3: mem: 470.6 MiB (1.4%) command: vivaldi-bin pid: 2288 cpu: 1.6%
  4: mem: 458.8 MiB (1.4%) command: vivaldi-bin pid: 3479 cpu: 4.0%
  5: mem: 445.3 MiB (1.3%) command: exe pid: 2108 cpu: 2.1%
Info:
  Processes: 510 Power: uptime: 34m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.37 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Compilers: clang: 20.1.6 gcc: 15.1.1 Shell: Zsh v: 5.9 default: Bash
    v: 5.2.37 running-in: konsole inxi: 3.3.38

I think it’s related to the kernel.

1 Like

Your post has been moved to a dedicated topic.

Please provide system information as described (below) and explain your issue as coherently as possible. Also, provide supporting information, wherever practical.

Feel free to rename this topic to something you feel more adequately describes your issue.

I’m sure someone will help when they are able.

Regards.


Welcome to the Manjaro community

As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit:


Update Announcements

The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.

System Information

While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly; :eyes:

Output of the inxi command with appropriate parameters will achieve this (naturally, formatted according to forum guidelines) and will generally be more useful for those wishing to help:

inxi --filter --verbosity=8

or the short form:

inxi -zv8

Be prepared to provide output from other commands whenever asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.

Highly Recommended
Required Reading
Technical Resources

This could indicate that your system is entering sleep state (s2idle) instead of shutting down.

In sleep state the system is still powered but can be woken by a peripheral action such as the ones you describe.

2 Likes

OK, if it goes into s2idle instead of shutdown, how do I change that?

It is also possible that the ACPI interaction has been improved and can now be woken up with USB in S5 state (soft off), which was not possible before. Usually there is an option in the UEFI settings to turn it off if you don’t need it.

1 Like

Unfortunately, I cannot find anything like this in the UEFI.
With kernel 6.16.0rc3-1 I also have this phenomenon.
Since I place my mouse on the charging station after switching off, this is annoying.

Well, there is a method in to disable the input devices…

Please share the output of:

cat /proc/acpi/wakeup

You can disable i.e. toggle the wakeup inputs by entering for example:

sudo bash -c 'echo XHC > /proc/acpi/wakeup'   

XHC is one of the devices in the first column.

That’s not permanent. It needs to be set on every boot. You can create systemd service for that task.

EDIT:

You can detect what device it is by:

lspci -nn -s 00:06.0

So pci:0000:00:06.0 becomes 00:06.0

cat /proc/acpi/wakeup                                                                                                                         ✔ 
Device  S-state   Status   Sysfs node
PEG1      S4    *enabled   pci:0000:00:01.0
PEGP      S4    *disabled  pci:0000:01:00.0
PEG2      S4    *disabled
PEGP      S4    *disabled
PEG0      S4    *enabled   pci:0000:00:06.0
PEGP      S4    *disabled  pci:0000:02:00.0
RP09      S4    *enabled   pci:0000:00:1d.0
PXSX      S4    *disabled  pci:0000:06:00.0
RP10      S4    *disabled
PXSX      S4    *disabled
RP11      S4    *disabled
PXSX      S4    *disabled
RP12      S4    *disabled
PXSX      S4    *disabled
RP13      S4    *disabled
PXSX      S4    *disabled
RP14      S4    *disabled
PXSX      S4    *disabled
RP15      S4    *disabled
PXSX      S4    *disabled
RP16      S4    *disabled
PXSX      S4    *disabled
RP01      S4    *disabled  pci:0000:00:1c.0
PXSX      S4    *disabled
RP02      S4    *disabled
PXSX      S4    *disabled
RP03      S4    *enabled   pci:0000:00:1c.2
PXSX      S4    *disabled
RP04      S4    *disabled
PXSX      S4    *disabled
RP05      S4    *disabled
PXSX      S4    *disabled
RP06      S4    *disabled
PXSX      S4    *disabled
RP07      S4    *disabled
PXSX      S4    *disabled
RP08      S4    *disabled
PXSX      S4    *disabled
RP17      S4    *disabled
PXSX      S4    *disabled
RP18      S4    *disabled
PXSX      S4    *disabled
RP19      S4    *disabled
PXSX      S4    *disabled
RP20      S4    *disabled
PXSX      S4    *disabled
RP21      S4    *disabled
PXSX      S4    *disabled
RP22      S4    *disabled
PXSX      S4    *disabled
RP23      S4    *disabled
PXSX      S4    *disabled
RP24      S4    *disabled
PXSX      S4    *disabled
RP25      S4    *enabled   pci:0000:00:1a.0
PXSX      S4    *disabled  pci:0000:03:00.0
RP26      S4    *disabled
PXSX      S4    *disabled
RP27      S4    *disabled
PXSX      S4    *disabled
RP28      S4    *disabled
PXSX      S4    *disabled
XHCI      S4    *enabled   pci:0000:00:14.0
XDCI      S4    *disabled
HDAS      S4    *disabled  pci:0000:00:1f.3
CNVW      S4    *disabled
AWAC      S4    *enabled   platform:ACPI000E:00
sudo bash -c 'echo XHC > /proc/acpi/wakeup'

Doesn’t change the behaviorm

Do you see a XHC device on your list? :thinking:

Then simply stick to the 6.12 kernel, its an LTS kernel and will stay up-to-date for quite a while.

1 Like
  • Topic title changed to reflect the actual issue.
  • Topic moved to SupportKernel.

@Casi2020

Unless you have a specific reason to use the latest-and-greatest kernel (which usually reaches EOL very quickly), it’s generally recommended to remain with the current SLTS; in this case, kernel 6.12 (LTS) as mentioned by @Wollie .

Otherwise, there is usually no great advantage gained.

Again, unless you have a special need, I suggest returning to kernel 6.12 (LTS) for everyday use, and marking the post from @Wollie as the solution to this topic.

Regards.

Even though I keep being told to use kernel 6.12.

I have kernel 6.15 installed.

With this, the computer starts with every mouse movement or keystroke.

This does not happen with the Arch Linux 6.15.6-arch1-1 kernel.

What feature was built into the 6.15 kernel from Manjaro and what advantage should this have? For me this is not an advantage but only a big disadvantage!

Can someone from the Manjaro team comment on this?

Because Manjaro Gmbh is working with device vendors - a lot of device specific kernel patches are added to the kernels - even they are device specific - it shouldn’t affect other systems.

We use this patch for improving S5 power management. I can check with AMD again if that might create a regression of sorts …

Thanks for the information.
Even if it doesn’t help me at first.
If I can help with system information, I will be happy to share it with you.

You claim a kernel without that patch series works on your hardware. You could simply drop ot and recompile the kernel without it to see if it creates a regression on your system with it …

After checking again. Since we added that patch since 6.15-rc7, it mostly can’t be the patch. However I still checked with AMD:

  1. Well if this is a real problem it should be fixed before that patch series is landing
  2. AMD is not going to land it with known regressions
  3. AMD would suggest the following:
    1. Take the exact same kernel with that patch series applied and patch series reverted and make sure that the issue only happens if it’s applied.
    2. On a kernel with it applied use something like this to turn off all wakeup sources before shutting down the system with S4.
echo "disabled" | sudo tee /sys/class/wakeup/*/device/power/wakeup
  1. if that helps it does confirm that the default wakeup status for at least one device causes this behavior

  2. and it should be narrowed down what device is causing it. It’s probably the xhci controller.

1 Like

@Casi2020 you can try Release 6.15.6-1 · manjaro-kernels/linux615 · GitHub, which includes the patch series, which might break your shutdown, and Release 6.15.6-2 · manjaro-kernels/linux615 · GitHub, which doesn’t ship it. Let me know if installing 6.15.6-2 solves the issue for you.

System information can often reveal contributing factors for many issues; the preference is to provide it, rather than not.

Note that personally identifiable information is filtered from the resulting output:

inxi -zv8

(as previously given)