You are not logged in.
hi all
i've been struggling with random crashes since i've upgraded to plasma6
at Jun 03 21:18:06 njordr kernel: Linux version 6.9.3 i had to reboot the machine since it was completely frozen.
checking the logs below
does not show anything odd, besides the fact that systemd is unable to show any logs for the past 8 minutes
Jun 03 21:10:07 njordr kmix[3795]: org.kde.kmix: No such icon "audio-card-pci"
-- Boot d4d9a081bd0f4d2eb0eb3e895d81e1be --
Jun 03 21:18:06 njordr kernel: Linux version 6.9.3 (bogdan@njordr) (gcc (GCC) 14.1.1 20240522, GNU ld (GNU Binutils) 2.42.0) #1 SMP PREEMPT Mon Jun 3 10:50:05 EEST 2024
i'm not sure how to troubleshoot the fact that nothing gets written to the journal, or how to capture the lost logs...
in the good old days one could find everything in /var/log/messages, but that era is long since gone...
thanx
Offline
https://wiki.archlinux.org/title/Keyboa … el_(SysRq)
If you reboot with the power button, the tail of the journal cannot be preserved.
There're known issues w/ the 550xx nvidia drivers, https://bbs.archlinux.org/viewtopic.php … 4#p2175194 => https://aur.archlinux.org/packages/nvidia-535xx-dkms
Also some nvme's cause trouble and that seems to have recently flared up => try https://wiki.archlinux.org/title/Solid_ … leshooting to disable APST, notably the explicit iommu=intel in your journal is irritating itr.
Offline
thanx for your reply
i expect to loose some couple of seconds worth of journal logs, but not 8 minutes or so....
i've checked for nvme issues, and as far as journald is reporting for the past 20000 minutes, nothing out of the ordinary comes up for this. besides the usual orphaned inode issues...
Offline
You'll loose everything after the last time the filesystem was sync'd to disk.
=> use the sysrq for a somewhat clean shutdown, nb. that you've to explicitly enable it first!
Offline
You'll loose everything after the last time the filesystem was sync'd to disk.
=> use the sysrq for a somewhat clean shutdown, nb. that you've to explicitly enable it first!
8 minutes seems quite unreasonable for this. i'm able to write stuff to disk,it's just that journald if failing to log anything..
also, i lack the sysrq key, and ctrl+alt+del doesnt do anything
Offline
Furthermore, some keyboards may not provide a separate SysRq key. In this case, a separate PrtScn key should be present.
The print screen key offers the same functionality .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
https://en.wikipedia.org/wiki/Magic_SysRq_key wrote:Furthermore, some keyboards may not provide a separate SysRq key. In this case, a separate PrtScn key should be present.
The print screen key offers the same functionality .
that's good to know. in my case this is under Fn+F6. I'll give it a go next time the system crashes
Offline
nope, sadly printscreen key doesn't no anything...
Offline
As mentioned, you've to first enable the feature.
Then it's still alt+print+r,e,i,s,u,b (wait a couple of seconds between each step)
You should test the general function at a point where the system hasn't crashed to ensure it principally works.
If the kernel no longer responds to sysrequests, it has paniced and the only way to debug that is https://wiki.archlinux.org/title/Kdump
Offline