You are not logged in.
You can use the Same kernel for both.
Offline
Hi @seth,
in that case I am still missing something. I will try to explain step-by-step:
1. install kexec-tools
2. set crashkernel=256 in systemd-boot options for linux kernel
3. reboot
4. run the command "kexec -p /boot/vmlinuz-linux --initrd=/boot/initramfs-linux.img --append="irqpoll nr_cpus=1 reset_devices"
5. Force the crash
6. Force reboot by long pressing the power button (ctrl+alt+del doesn't work)
7. Laptop will reboot as normal
8. Unlock LUKS/LVM and boot up KDE
9. makedumpfile -z -d 31 /proc/vmcore /root/vmcore.crashdump_compressed
10. Provide you the crash file or analyze it myself
Correct?
Last edited by Utini (2024-09-02 06:42:54)
Setup 1: Thinkpad T14s G3, 14" FHD - R7 6850U - 32GB RAM - 2TB Solidigm P44 Pro NVME
Setup 2: Thinkpad X1E G1, 15.6" FHD - i7-8850H - 32GB RAM - NVIDIA GTX 1050Ti - 2x 1TB Samsung 970 Pro NVME
Accessories: Filco Majestouch TKL MX-Brown Mini Otaku, Benq XL2420T (144Hz), Lo(w)gitech G400, Puretrak Talent, Sennheiser HD800S + Meier Daccord FF + Meier Classic FF
Offline
5. Force the crash
6. Force reboot by long pressing the power button (ctrl+alt+del doesn't work)
7. Laptop will reboot as normal
No, force the crash, the other kernel will take over, you get a memory dump of the crashed kernel that you can then inspect w/ crash.
Do not reboot before you've secured the coredump or it'll be lost.
You can use kdumpst to automatize this, but I've never used it, so we just assume it'll do the right thing
Offline
Ahh I guess I was just not patient enough!
So I forced the crash, waited 2-3 mins and then the system was usable again.
I have no dump but I now have a bigger journalctl file.
"/proc/vmcore/" does not exist. So it seems like no dump was created?
Here is the journalctl though, which contains more valuable information?
Link: https://files.bestmail.ws/Arch/journal0209_3.txt
I didn't reboot the system so far - so let me know if I should check/export anything else
Last edited by Utini (2024-09-02 09:57:37)
Setup 1: Thinkpad T14s G3, 14" FHD - R7 6850U - 32GB RAM - 2TB Solidigm P44 Pro NVME
Setup 2: Thinkpad X1E G1, 15.6" FHD - i7-8850H - 32GB RAM - NVIDIA GTX 1050Ti - 2x 1TB Samsung 970 Pro NVME
Accessories: Filco Majestouch TKL MX-Brown Mini Otaku, Benq XL2420T (144Hz), Lo(w)gitech G400, Puretrak Talent, Sennheiser HD800S + Meier Daccord FF + Meier Classic FF
Offline
There's no kernel error in that log, but xfreerdp3 crashes.
Since it 26k lines covering 5h, when about did the crash occur?
~11:45 ?
I currently doubt you're actually facing a kernel panic here.
Do you have the same problem w/ a plasma/X11 session?
Offline
Oh sorry - forgot to mention: The crash happened only a few minutes before creating the log. 11:35 or 11:45 seems to be the time (ethernet connection disconnected).
I didn't try X11 yet but I can try tomorrow.
Setup 1: Thinkpad T14s G3, 14" FHD - R7 6850U - 32GB RAM - 2TB Solidigm P44 Pro NVME
Setup 2: Thinkpad X1E G1, 15.6" FHD - i7-8850H - 32GB RAM - NVIDIA GTX 1050Ti - 2x 1TB Samsung 970 Pro NVME
Accessories: Filco Majestouch TKL MX-Brown Mini Otaku, Benq XL2420T (144Hz), Lo(w)gitech G400, Puretrak Talent, Sennheiser HD800S + Meier Daccord FF + Meier Classic FF
Offline
You end up w/ no screen
Sep 02 11:45:28 S2000 konsole[22684]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Sep 02 11:45:28 S2000 baloorunner[2405]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Sep 02 11:45:28 S2000 keepassxc[7118]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
at least xwayland doesn't like that
Sep 02 11:45:28 S2000 kwin_wayland_wrapper[1696]: XWAYLAND: mode -1x-1 is not available
and then all hell breaks lose.
I guess the eDP is deactivated while running on the dock (and using an external monitor)?
Try to explicitly enable it first.
Offline
Yes the eDP (laptop display) was disabled. I have now enabled it and the docking disconnect is a lot more fluid now. Also no crashes/freezes so far.
But that means wasting energy on the laptop display since it is of no use atm.
@Edit: The following might be a different problem/bug. It should be possible to get 3 screens (2x external + 1x internal) via USB C.
Also with USB-C (USB 3.2) it seems like I can't output three different displays in total, meaning the laptop display will always be mirrored.
The USB4 port does allow three individual displays but it gets unnecessary hot then. Its a bug with the Thinkpad T14s G3 AMD where the USB4 port gets so hot that even the CPU temps rise.
Last edited by Utini (2024-09-03 08:15:15)
Setup 1: Thinkpad T14s G3, 14" FHD - R7 6850U - 32GB RAM - 2TB Solidigm P44 Pro NVME
Setup 2: Thinkpad X1E G1, 15.6" FHD - i7-8850H - 32GB RAM - NVIDIA GTX 1050Ti - 2x 1TB Samsung 970 Pro NVME
Accessories: Filco Majestouch TKL MX-Brown Mini Otaku, Benq XL2420T (144Hz), Lo(w)gitech G400, Puretrak Talent, Sennheiser HD800S + Meier Daccord FF + Meier Classic FF
Offline
But that means wasting energy on the laptop display since it is of no use atm.
You only need to make sure to enable the eDP before you undock the device.
What happens is that you've an external monitor, then you undock, have no external monitor, have no output at all (most likely kscreen resizes the otput to 0x0) and a bunch clients lose it over that.
An alternative approach would be to disable the kscreen daemon and ideally of course the undocking even would implicitly enable the eDP *before* the system responds to the output loss (you could try a udev rule or fox X11, if the problem manifests there at all, x-on-resize)
Also with USB-C (USB 3.2) it seems like I can't output three different displays in total, meaning the laptop display will always be mirrored.
=> X11 session and "xrandr -q" and xorg log for that setup (the data is pointless in the context of wayland, you can check kscreen-doctor on this, but idk how much that is maybe impacted by the wayland compositor)
Offline
Thanks for your debugging help and thanks for the hint to kscreen-doctor.
I have now managed to use the three screen all together at their maximum capabilities:
eDP at FHD 60Hz
Screen 1 at FHD 75Hz
Screen 2 at FHD 60Hz
I will see if I can reduce the brightness of my eDP automatically when switching to this setup and then use that eDP for various different side tasks that I have yet to find and define ;-P
I am going to set this to solved but I wonder if this issue might hunt other people as well and if some kind of a fallback solution should be provided?
E.g. such a udev rule by default or atleast mentioning it somewhere in the wiki?
Setup 1: Thinkpad T14s G3, 14" FHD - R7 6850U - 32GB RAM - 2TB Solidigm P44 Pro NVME
Setup 2: Thinkpad X1E G1, 15.6" FHD - i7-8850H - 32GB RAM - NVIDIA GTX 1050Ti - 2x 1TB Samsung 970 Pro NVME
Accessories: Filco Majestouch TKL MX-Brown Mini Otaku, Benq XL2420T (144Hz), Lo(w)gitech G400, Puretrak Talent, Sennheiser HD800S + Meier Daccord FF + Meier Classic FF
Offline
https://wiki.archlinux.org/title/ThinkPad_docks but technically this isn't dock related.
The main bug that generally needs to be addressed / worked around is that (wayland?) clients are unable to handle a headless situation which is maybe such a general issue that one might expect a screen managing daemon to handle and catch it globally by either being more smarterer™ and enabling a remaining one or adding a fake VGA output.
Offline