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:
Hit ESC on splash screen or remove splash and post terminal output as text @jpierce.coder
Remove splash from Kernel parameters with garuda-boot-options.
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.
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.
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.
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 rootflags=subvol=@ rd.udev.log_priori>
Jan 05 19:24:32 glomar-garudaPlasma-laptop kernel: Linux version 6.1.2-zen1-1-zen (linux-zen@archlinux) (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 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.
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:
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.
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.
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.