Plasma Login Freeze

Hello Team,

I'm on the latest ISO of KDE Dr460nized, and seem to have run into a bug. Whenever I log out of my current session back to the SDDM login screen, and then attempt to log back in, Plasma almost instantly freezes on the below splash screen:

It remains frozen here until I a hardware power off, and back on. Did I mess something up?

System:
Kernel: 6.1.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=c1fbee3f-f275-4de7-a4fd-1c2ac4647241 rw [email protected]
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.26.5 tk: Qt v: 5.15.7 info: latte-dock, plank
wm: kwin_x11 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Laptop System: ASUSTeK product: ASUS TUF Dash F15 FX516PM_FX516PM
v: 1.0 serial: <filter>
Mobo: ASUSTeK model: FX516PM v: 1.0 serial: <filter> UEFI: American
Megatrends LLC. v: FX516PM.322 date: 08/27/2021
Battery:
ID-1: BAT0 charge: 59.1 Wh (95.5%) condition: 61.9/76.0 Wh (81.4%)
volts: 15.8 min: 15.8 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A
status: not charging cycles: 94
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master 2S
serial: <filter> charge: 100% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: 11th Gen Intel Core i7-11370H socket: U3E1 bits: 64
type: MT MCP arch: Tiger Lake gen: core 11 level: v4 note: check built: 2020
process: Intel 10nm family: 6 model-id: 0x8C (140) stepping: 1
microcode: 0xA6
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
L1: 320 KiB desc: d-4x48 KiB; i-4x32 KiB L2: 5 MiB desc: 4x1.2 MiB
L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 1023 high: 1400 min/max: 400/4800 base/boost: 3300/4800
scaling: driver: intel_pstate governor: powersave volts: 0.8 V
ext-clock: 100 MHz cores: 1: 1164 2: 997 3: 725 4: 1153 5: 400 6: 1369
7: 983 8: 1400 bogomips: 52838
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: ASUSTeK
driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21
ports: active: eDP-1 empty: DP-1,DP-2,HDMI-A-2 bus-ID: 0000:00:02.0
chip-ID: 8086:9a49 class-ID: 0300
Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: ASUSTeK
driver: nouveau v: kernel non-free: 525.xx+ status: current (as of 2022-12)
arch: Ampere code: GAxxx process: TSMC n7 (7nm) built: 2020-22 ports:
active: none empty: HDMI-A-1 bus-ID: 0000:01:00.0 chip-ID: 10de:2520
class-ID: 0300
Display: x11 server: X.Org v: 21.1.6 with: Xwayland v: 22.1.7
compositor: kwin_x11 driver: X: loaded: modesetting,nouveau
alternate: fbdev,intel,nv,vesa dri: iris gpu: i915 display-ID: :0
screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: eDP-1 model: Najing CEC Panda 0x004d built: 2019 res: 1920x1080
hz: 144 dpi: 142 gamma: 1.2 size: 344x194mm (13.54x7.64")
diag: 395mm (15.5") ratio: 16:9 modes: 1920x1080
API: OpenGL v: 4.6 Mesa 22.3.2 renderer: Mesa Intel Xe Graphics (TGL GT2)
direct render: Yes
Audio:
Device-1: Intel Tiger Lake-LP Smart Sound Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel alternate: snd_sof_pci_intel_tgl
bus-ID: 0000:00:1f.3 chip-ID: 8086:a0c8 class-ID: 0403
Device-2: NVIDIA GA106 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 0000:01:00.1 chip-ID: 10de:228e
class-ID: 0403
Sound API: ALSA v: k6.1.2-zen1-1-zen running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.63 running: yes
Network:
Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi v: kernel bus-ID: 0000:00:14.3
chip-ID: 8086:a0f0 class-ID: 0280
IF: wlo1 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK driver: r8169 v: kernel port: 3000 bus-ID: 0000:2e:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eno2 state: down mac: <filter>
IF-ID-1: anbox0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 3-10:3 chip-ID: 8087:0026 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
RAID:
Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
v: 0.6 port: N/A bus-ID: 0000:00:0e.0 chip-ID: 8086:9a0b rev: class-ID: 0104
Drives:
Local Storage: total: 476.94 GiB used: 19.45 GiB (4.1%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: MZVLQ512HBLU-00B00 size: 476.94 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: FXM7201Q temp: 36.9 C scheme: GPT
SMART: yes health: PASSED on: 99d 1h cycles: 1,120
read-units: 29,282,778 [14.9 TB] written-units: 42,537,390 [21.7 TB]
Partition:
ID-1: / raw-size: 145.51 GiB size: 145.51 GiB (100.00%)
used: 19.44 GiB (13.4%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p6
maj-min: 259:6
ID-2: /boot/efi raw-size: 1000 MiB size: 998 MiB (99.80%)
used: 608 KiB (0.1%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p5
maj-min: 259:5
ID-3: /home raw-size: 145.51 GiB size: 145.51 GiB (100.00%)
used: 19.44 GiB (13.4%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p6
maj-min: 259:6
ID-4: /var/log raw-size: 145.51 GiB size: 145.51 GiB (100.00%)
used: 19.44 GiB (13.4%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p6
maj-min: 259:6
ID-5: /var/tmp raw-size: 145.51 GiB size: 145.51 GiB (100.00%)
used: 19.44 GiB (13.4%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p6
maj-min: 259:6
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.32 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 53.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 275 Uptime: 11m wakeups: 401 Memory: 15.32 GiB
used: 2.42 GiB (15.8%) Init: systemd v: 252 default: graphical
tool: systemctl Compilers: gcc: 12.2.0 Packages: pm: pacman pkgs: 1369
libs: 364 tools: octopi,paru Shell: garuda-inxi (sudo) default: Bash
v: 5.1.16 running-in: konsole inxi: 3.3.24
Garuda (2.6.14-1):
System install date:     2023-01-05
Last full system update: 2023-01-05
Is partially upgraded:   No
Relevant software:       snapper NetworkManager mkinitcpio
Windows dual boot:       Yes
Failed units:            systemd-networkd-wait-online.service

Hit ESC on splash screen or remove splash and post terminal output as text :slight_smile:
@jpierce.coder
Remove splash from Kernel parameters with garuda-boot-options.

1 Like

Yeah I tried hitting escape, I tried hitting about every key combination I could think of, lol. Frozen solid.

The splash screen wasn't spinning or anything. It had just Frozen, and no movement or any key binding combination worked to get past it

Escape won't work on KDE splash screens, it only does for Plymouth, the boot screen.

So it happens consistently? That's quite hard to troubleshoot.. something that might help understanding the issue is logging in via tty (Ctrl + Alt + F3) and using journalctl --user -xe - that shows user logs.
Also, once in tty try running startx to start Plasma manually to look out for eventual errors.

3 Likes

A post was split to a new topic: I dont wan't to put 2 passwords in when booting

I'll try this when I get home. Drove two hours to pick up my new desk for my WFH setup. :smiley:P

Okay so are you able to point me in a direction of what I'm looking for? Several yellow lines, a few red ones.
Over 2k lines in the logs

Also, when I run startx manually it loads in just fine

Here are a few snippets of yellow and red code:

Yellow:

Jan 05 18:46:08 glomar-garudaPlasma-laptop kded5[982]: kscreen.kded: PowerDevil SuspendSession action not available!
Jan 05 18:46:08 glomar-garudaPlasma-laptop plasmashell[1058]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Jan 05 18:46:08 glomar-garudaPlasma-laptop plasmashell[1058]: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemo>

RED:

The unit UNIT has entered the 'failed' state with result 'exit-code'.
Jan 05 18:46:09 glomar-garudaPlasma-laptop systemd[754]: Failed to start Initial Bashrc setup.
░░ Subject: A start job for unit UNIT has failed
Jan 05 18:46:09 glomar-garudaPlasma-laptop systemd[754]: Failed to start BTRFS Assistant Snapper check.
systemctl[1220]: Failed to enable unit: Unit file gamemoded\x3bsetup_dxvk.service does not exist.

Just to show a few of the yellow and most of the red lines of logs.

Edit: Weird, I logged out and back in, and this time it loaded the Plasma desktop, but then the desktop froze, and only thing I was able to do was move around the mouse. Nothing else was functional. Wasn't able to open tty either. Had to hardware button power off and power back on.

Did you try this?

Not yet, but I don't think it's the splash. See my edit to my comment above. I'll try it though.

Edit: Tried removing the splash screen through garuda-boot-options, and it just removed the boot splash, not the login splash, still freezes either on the splash screen logging in (after logging out from auto login) or just after the plasma desktop is loaded. Unable to do anything at all when it freezes, so unable to grab the logs through tty at that moment.

Some snapshots available from which you can boot?

Normally it boots up fine and loads Plasma initially just fine. Normally. But whenever I log out, and attempt to log back in is when it crashes. So I booted up two more times, and attempted to open Konsole (hadn't logged out yet either time). The system froze on trying to open Konsole via keyboard shortcut (Meta + Enter). Looking at the logs, it seems like my kernel may have crashed? I'll post the code as an edit to this post when I get it booted again.

So here

Jan 05 19:24:33 glomar-garudaPlasma-laptop kernel: intel_tcc_cooling: Programmable TCC Offset detected
Jan 05 19:24:33 glomar-garudaPlasma-laptop kernel: snd_hda_intel 0000:01:00.1: enabling device (0000 -> 0002)
Jan 05 19:24:33 glomar-garudaPlasma-laptop kernel: nouveau 0000:01:00.0: mc: intr 00000040

nouveau seems to crash. That third line of code repeats itself for a few hundred lines and then:

Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI: EC: EC started
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - ^XHCI.RHUB.HS04.VI2C (20220331/dspkginit-438)
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - ^XHCI.RHUB.HS04.VI2C (20220331/dspkginit-438)
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - ^SPI1.SPFD.CVFD (20220331/dspkginit-438)
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - ^SPI1.SPFD.CVFD (20220331/dspkginit-438)
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI: 12 ACPI AML tables successfully acquired and loaded
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI: Skipping parse of AML opcode: Method (0x0014)
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS10._PR3], AE_ALREADY_EXISTS (20220331/dswload2-326)
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI: Skipping parse of AML opcode: Method (0x0014)
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS10._PR2], AE_ALREADY_EXISTS (20220331/dswload2-326)
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI: Skipping parse of AML opcode: Method (0x0014)
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS10._PR0], AE_ALREADY_EXISTS (20220331/dswload2-326)
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS10._S0W], AE_ALREADY_EXISTS (20220331/dswload2-326)
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI: Skipping parse of AML opcode: PowerResource (0x5B84)
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS10.BTPR], AE_ALREADY_EXISTS (20220331/dswload2-326)

It throws a bunch of errors related to ACPI, followed by info lines of code mentioning firmware bugs.
Then at the very end the kernel crashes, which is where I guess it froze up:

Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=c1fbee3f-f275-4de7-a4fd-1c2ac4647241 rw [email protected] rd.udev.log_priori>
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: Linux version 6.1.2-zen1-1-zen ([email protected]) (gcc (GCC) 12.2.0, GNU ld (GNU Binutils) 2.39.0) #1 ZEN SMP PREEMPT_DYNAMIC Sat, 31 D>
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: microcode: microcode updated early to revision 0xa6, date = 2022-06-28

Disclaimer: I don't know what's going on, I just run some searches and I noticed that:

  • there is a good number of results for "kde stuck at second login after logout" although oldish
  • there's one thread on the Manjaro forum (Can't log in into KDE after logging out) where the problem is solved by disabling/changing plasma theme and/or "clearing cache" (I'm not sure what they mean because that's manjaro and some "system settings">"network" GUI tool is mentioned, also it isn't clear which of the two (theme and cache) did the trick)
  • there's this one on reddit (https://libreddit.kavin.rocks/r/kde/comments/kgxccl/kde_plasma_520_login_after_logout_is_impossible) where the suggested work-around is "Switching to terminal session and terminating remnant Plasma session-related processes (baloo_file and systemd --user) does indeed make login possible"
  • there's KDE bug 424488 (though marked solved and duplicate of 424408)
  • there's this Arch bbs thread (apparently unrelated, but includes that "crashing the kernel on kernel split_locks" and is also about an ASUS with nvidia) where the problem seems to have been caused by something blacklisting the nvidia driver (relevant posts at the very end)
    I doubt this is the case otherwise it wouldn't work the first time either, but maybe "something with the graphics card"
  • since AE_ALREADY_EXISTS sort of rhymed with "second login" I also searched about that, some threads suggest it's indeed some problem with the "BIOS" (actually UEFI I guess) that may be fixed by a firmware upgrade, but in many instances it's just noise in the logs and the system works fine regardless (curiously, searching that message one of the first results was a linux-hardware probe of an ASUS TUF Dash F15 FX516PM_FX516PM on Manjaro)

Not that I pretend to understand any of that LOL, I just hope some of that stuff rings a bell for troubleshooting.

4 Likes

Would it do this even if I don't have the NVIDIA drivers installed?

Interesting. I think I wasn't finding anything because I was searching the wrong terms, which makes sense. I'll dig in a little more, and see if I can figure out what's going on. Thanks for clarifying what I need to search for. It's more of an annoyance than a critical issue. The only thing that'll be hard to deal with is anytime I attempt to start terminal (even on first login) via keyboard shortcut (whether it's ctrl + alt + T or alt + enter), it also crashes the kernel. I'll dig a little further and update this post if I find anything. Thanks!

So I just updated to Linux Zen kernel 6.1.3 from 6.1.2, and now I can open the terminal via keyboard shortcuts (though it hangs the system for a good 2-3 seconds) without the system crashing. I'm guessing that part was a bug in 6.1.2 for my hardware? I haven't tried logging out and back in yet, but I'm about to test that.

Edit: So it's still crashing the kernel whenever I log out and back in, but using keyboard shortcuts for the terminal is fixed, so for now, until I can figure out a a little more information, I'll just avoid logging out and reboot if needed. Thanks for all the help guys!

Darn, 3 seconds to open a terminal would drive me nuts pretty soon.
To clarify, the problem is only when using a keyboard shortcut and not, say, clicking an icon in the panel/dock/whatever?

I'd be proud of myself if I had half of a clue, but some time and search-fu is the best I have to offer:

https://docs.kernel.org/x86/buslock.html

Which leaves me scratching my head, as it says the default is to warn not crash (there isn't even a crash option, split_lock_detect=fatal would kill the offending process).

So I guess it's

Beginning with the Tremont Atom CPU split lock operations may raise an Alignment Check (#AC) exception when a split lock operation is attemp[t]ed.

Where to go from here... :man_shrugging:

1 Like

That is correct. I was able to open the terminal from Plank and it would open immediately without issue. I closed the terminal and immediately tried open via keyboard and kernel crashed lol.

Yeah I'll keep digging around regarding the login kernel crashing. Garuda had an update in which the zen kernel updated frorm 6.1.2 to 6.1.3, which fixed the problem of crashing the kernel with keyboard shortcuts for terminal, so that's at least one problem out of the way. Not sure if it was a bug specific to my hardware or what. Now on 6.1.3 whenever I open via keyboard, it hangs for 2 - 3 seconds, but then it opens. It's at least usable, so I'll do more digging in the logs, get REALLY familiar with my system.

So, I'm reading [tip: x86/cpu] x86/split_lock: Enable split lock detection by kernel - tip-bot2 for Peter Zijlstra (Intel) and maybe there's something relevant in there (assuming the #AC theory is correct):

A split-lock occurs when an atomic instruction operates on data that spans
two cache lines. In order to maintain atomicity the core takes a global bus
lock.

This is typically >1000 cycles slower than an atomic operation within a
cache line. It also disrupts performance on other cores (which must wait
for the bus lock to be released before their memory operations can
complete). For real-time systems this may mean missing deadlines. For other
systems it may just be very annoying.

which may explain the 3 seconds system freeze

And this sentence

On systems that support split lock detection the default is "warn". Note
that if the kernel hits a split lock in any mode other than "off" it will
OOPs.

makes me think it's worth trying to boot with split_lock_detect=off and see what happens.

1 Like

Would I just add that to the boot params?

Yep.

1 Like

Nope, after rebooting, initial login, then logging out, kernel crashed on attempting to login again. Ugh... This is annoying.