Shutdown sometime stalls, monitor turns off, pc stays on

Issues & Assistance
1

Happens at the:

Authentication error: PLASMALOGIN::Auth::ERROR_INTERNAL "Process crashed"

I think, also I am using bcache in writeback mode, has an intel optane for cache, and hdd as the backing device. Works flawlessly during runtime. Don’t know if that could attribute to anything, since I’ve never had this issue before, and ever since adding the bcache, or updating the kernel to 7.1,… There are too many things that have changed.

edit: Things I currently have in the backing device: Brave browser profile, games, mesa_shader_cache,proton prefixes.

  • The bcache mount in /etc/fstab

  • UUID=e7cea7ce-be76-4479-b143-5c5453b41aa9 /media/Data2 ext4 defaults,noatime,nofail,commit=60 0 1

edit 2: After a bit of searching around, I’ve managed to fix the unmount failled of bcache device, by removing the symlink(mesa_shader_cache) to that drive, I’d thought that was the problem, but same old problem still occur:

edit 3: Did some more searching around, switched to sddm, but same error is still present, BUT computer is shutting down now. So…I guess I’ll stick with sddm? I’m not entirely sure what is wrong with the system, if it’s a software/hardware problem. Though everything runs fine.

edit 4: NVM, still happens regardless of sddm or plasmalogin, my speculation was false, gonna try downgrading the linux-firmware-amdgpu as listed in: Bug Report: linux-firmware-amdgpu 20260622 prevents clean poweroff .

2

It just happened again, after writing this(started the pc, opened the browser, exit the browser,shutdown).

Do note, I am still able to shutdown fine, these weird bugs happen sometime? I don’t quite get it.

3

I changed backed to sddm, let’s see how stable this goes.

4

Same error as plasmalogin, but strangely enough, the pc did shutdown just fine.

5

Cross-posting :stuck_out_tongue: This looks kinda like Kernel 'linux-cachyos 7.1.1-2' seems to fail to reboot 9/10 times, lts kernel works every time - #5 by axra

6

Interesting! I didn’t realize others were experiencing the same symptoms as me. Though I have been able to reboot cleanly, just aren’t able to shutdown. That does remind me…These bugs happens after I’ve installed kernel 7.1.1-2.

7

I just found my PC this morning powered on in the same state after I thought it turned off last night. So +1 to this. I saw that I wasn’t part of the i2c group. but other than that no real errors in my journal.

8

now i can enter the chat! :rofl:
i do have this issue, but it was fine after added my user to the i2c group
incase needed

sudo usermod -aG i2c <your username>

from quick research it was for managing DDC/CI (for brightness control i think)? seems happens after new KDE Plasma major upgrade (my current guess)

9

Also journalctl -b for: below

and: below

Added for more context.

10
  1. Is this reproducible on the LTS Kernel?
  2. If its also reproduceible on the LTS kernel, could you please try to downgrade linux-firmware-amdgpu to 1:20260519-1
11

It could be also tried to pass amd_pstate=passive to the kernel cmdline.

Please report back.

12

Hello! Thank you for the reply!!! But isn’t this specific kernel parameter only for amd cpus? I don’t quite get it.

13

Thank you for the reply!! It is currently very late for me. I will report back as soon as possible!!