Repeatedly black screen

suse_paul · March 29, 2024, 8:43am

With my fresh installation of OS 15.5 (KDE) on a Lenovo laptop I repeatedly, ie. at least once per day, encounter a black screen “out of the blue”.
sometimes I can switch with Alt-Ctrl-F1 to a konsole, but login is not possible.
my only “remedy” is a hard reset.

Is there a solution?
Where can I look for possible causes?

Does plasma have a problem with the GPU?
(sometimes there is a flickering popup instead of a "normal one, when hovering over the window bar)
Already earlier with different versions of OS on a Fujitsu laptop I repeatedly had problems with a frozen desktop - only the mouse could be moved.-> only hard reset helped.

hui · March 29, 2024, 9:08am

Journal? Logs? Dmesg?

suse_paul · March 29, 2024, 9:24am

I didn’t see anything suspicious with “dmesg”, or “journalctl -f”

which logs would I consult that “survive” a reboot after crash?

pavinjoseph · March 29, 2024, 8:17pm

If you’re really sure there’s nothing in the journal, then it’s a kernel panic and the filesystem is not syncing with the error messages.

In this case, the kernel dump needs to be captured and saved by a capture kernel running in a reserved area of memory using kdump:

mrmazda · March 30, 2024, 9:47am

Only F1? Or, all the Fs? SDDM configuration tends to tie it and F2 up, so try any of F3-F6 instead whenever SDDM is running.

suse_paul · March 30, 2024, 6:45pm

now indeed the crash was different:
the screen was frozen, with no plasmashell window bar. the mouse pointer could be moved, but clicking had no effect.
I could switch with alt-ctrl-F1 to a console: keyboard letters appeared on the screen, but had no effect.
alt-ctrl-F2-F6 showed a black screen with a white pixel in the upper left corner.

journalctl --list-boots
shows only

 0 d5169d2aa8614376bb7ed1f637f04252 Sat 2024-03-30 18:14:56 CET—Sat 2024-03-30 17:42:48 CET

shouldn’t there be more than the last boot?

some output from dmesg:

0.195675] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0], AE_NOT_FOUND (20220331/dswload2-163)
[    0.195683] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-221)
...
[    1.642715] PM: hibernation: the secret key is invalid
...
[    2.653216] Lockdown: systemd-hiberna: hibernation is restricted; see man kernel_lockdown.7
[    2.653218] PM: hibernation: the secret key is invalid

some output from journalctl:

ar 30 18:14:56 legion kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0], AE_NOT_FOUND (20220331/dswload2-163)
Mar 30 18:14:56 legion kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-221)
...
Mar 30 18:14:56 legion kernel: pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
Mar 30 18:14:56 legion kernel: pci 0000:00:07.2: [8086:9a2f] type 01 class 0x060400
Mar 30 18:14:56 legion kernel: pci 0000:00:07.2: PME# supported from D0 D3hot D3cold
Mar 30 18:14:56 legion kernel: pci 0000:00:07.2: DPC: RP PIO log size 0 is invalid
...
Mar 30 18:14:57 legion kernel: usb: port power management may be unreliable
...
Mar 30 18:15:01 legion systemd[1]: haveged.service: Main process exited, code=exited, status=1/FAILURE
Mar 30 18:15:01 legion systemd[1]: haveged.service: Failed with result 'exit-code'.
...
Mar 30 17:15:02 legion tlp[856]: Error: tlp.service is not enabled, power saving will not apply on boot.
Mar 30 17:15:02 legion tlp[856]: >>> Invoke 'systemctl enable tlp.service' to correct this!
Mar 30 17:15:02 legion kernel: r8169 0000:5c:00.0: can't disable ASPM; OS doesn't have ASPM control
...
Mar 30 17:15:02 legion kernel: iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
...
Mar 30 17:15:02 legion kernel: thermal thermal_zone11: failed to read out thermal zone (-61)
...
Mar 30 17:15:03 legion (udev-worker)[751]: 3-14: Process '/usr/lib/virtualbox/VBoxCreateUSBNode.sh 189 261 e0' failed with exit code 1.
Mar 30 17:15:03 legion (udev-worker)[759]: 2-3: Process '/usr/lib/virtualbox/VBoxCreateUSBNode.sh 189 129 00' failed with exit code 1.
Mar 30 17:15:03 legion (udev-worker)[750]: 3-7: Process '/usr/lib/virtualbox/VBoxCreateUSBNode.sh 189 258 00' failed with exit code 1.
Mar 30 17:15:03 legion (udev-worker)[834]: 3-9: Process '/usr/lib/virtualbox/VBoxCreateUSBNode.sh 189 259 00' failed with exit code 1.
Mar 30 17:15:03 legion (udev-worker)[756]: 3-6: Process '/usr/lib/virtualbox/VBoxCreateUSBNode.sh 189 257 ef' failed with exit code 1.
Mar 30 17:15:03 legion (udev-worker)[763]: 3-10: Process '/usr/lib/virtualbox/VBoxCreateUSBNode.sh 189 260 00' failed with exit code 1.
...
Mar 30 17:15:05 legion boltd[1643]: [e04df1a9-713b-domain0                    ] udev: failed to determine if uid is stable: unknown NHI PCI id '0x9a1f'
...
Mar 30 17:15:05 legion boltd[1643]: [f137fdd8-5669-domain1                    ] udev: failed to determine if uid is stable: unknown NHI PCI id '0x9a21'
...
Mar 30 17:15:05 legion kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
...
Mar 30 17:15:06 legion systemd[1]: vboxdrv.service: Failed with result 'exit-code'.
Mar 30 17:15:06 legion systemd[1]: Failed to start VirtualBox Linux kernel module.
...
Mar 30 17:15:08 legion upowerd[2312]: energy_full (81,300000) is greater than energy_full_design (80,000000)
...
Mar 30 17:15:09 legion org_kde_powerdevil[2295]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this ha>
...
Mar 30 17:15:08 legion ksmserver[2163]: Qt: Session management error: networkIdsList argument is NULL
...
Mar 30 17:15:09 legion udisksd[2428]: Can't load configuration file /etc/udisks2/udisks2.conf
...
Mar 30 17:15:09 legion org_kde_powerdevil[2295]: org.kde.powerdevil: Handle button events action could not check for screen configuration
...
Mar 30 17:15:09 legion kwin_x11[2166]: kf.config.core: "\"fsrestore1\" - conversion of \"0,0,0,0\" to QRect failed"
Mar 30 17:15:09 legion kwin_x11[2166]: kf.config.core: "\"fsrestore2\" - conversion of \"0,0,0,0\" to QRect failed"
Mar 30 17:15:09 legion kwin_x11[2166]: kf.config.core: "\"fsrestore3\" - conversion of \"0,0,0,0\" to QRect failed"
Mar 30 17:15:09 legion kwin_x11[2166]: kf.config.core: "\"fsrestore4\" - conversion of \"0,0,0,0\" to QRect failed"
Mar 30 17:15:09 legion kwin_x11[2166]: kf.config.core: "\"fsrestore5\" - conversion of \"0,0,0,0\" to QRect failed"
Mar 30 17:15:09 legion kwin_x11[2166]: kf.config.core: "\"fsrestore6\" - conversion of \"0,0,0,0\" to QRect failed"
Mar 30 17:15:09 legion kwin_x11[2166]: kf.config.core: "\"fsrestore7\" - conversion of \"0,0,0,0\" to QRect failed"
Mar 30 17:15:09 legion kwin_x11[2166]: kf.config.core: "\"fsrestore8\" - conversion of \"0,0,0,0\" to QRect failed"
Mar 30 17:15:09 legion kwin_x11[2166]: kf.config.core: "\"fsrestore9\" - conversion of \"0,0,0,0\" to QRect failed"
Mar 30 17:15:09 legion kwin_x11[2166]: kf.config.core: "\"fsrestore10\" - conversion of \"0,0,0,0\" to QRect failed"
Mar 30 17:15:09 legion kwin_x11[2166]: kf.config.core: "\"fsrestore11\" - conversion of \"0,0,0,0\" to QRect failed"
Mar 30 17:15:09 legion kwin_x11[2166]: kf.config.core: "\"fsrestore12\" - conversion of \"0,0,0,0\" to QRect failed"
Mar 30 17:15:09 legion kwin_x11[2166]: kf.config.core: "\"fsrestore13\" - conversion of \"0,0,0,0\" to QRect failed"
Mar 30 17:15:09 legion kwin_x11[2166]: kf.config.core: "\"fsrestore14\" - conversion of \"0,0,0,0\" to QRect failed"
...
Mar 30 17:15:09 legion kded5[2165]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
...
Mar 30 17:15:09 legion plasmashell[2250]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Mar 30 17:15:09 legion plasmashell[2250]: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
Mar 30 17:15:09 legion plasmashell[2250]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Mar 30 17:15:09 legion plasmashell[2250]: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
...
ar 30 17:15:09 legion ksystemstats[2617]: kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Temperature %1" msgid_plural: "" msgctxt: "@title %1 is a number"
Mar 30 17:15:09 legion ksystemstats[2617]: kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Voltage %1" msgid_plural: "" msgctxt: "@title %1 is a number"
...
ar 30 17:15:11 legion plasmashell[2250]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:43:5: QML MouseArea: Cannot anchor to an item that isn't a parent or sibling.
Mar 30 17:15:11 legion plasmashell[2250]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:43:5: QML MouseArea: Cannot anchor to an item that isn't a parent or sibling.
...
Mar 30 17:15:12 legion plasmashell[2250]: file:///usr/share/ksysguard/sensorfaces/org.kde.ksysguard.piechart/contents/ui/CompactRepresentation.qml:22:1: QML CompactRepresentation: Binding loop detected for property "implicitHeight"
Mar 30 17:15:12 legion plasmashell[2250]: file:///usr/share/plasma/plasmoids/org.kde.plasma.networkmanagement/contents/ui/main.qml:95: TypeError: Cannot read property 'airplaneModeAvailable' of null
...
Mar 30 17:15:12 legion plasmashell[2250]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:18:1: QML MouseArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth"
Mar 30 17:15:12 legion plasmashell[2250]: Both point size and pixel size set. Using pixel size.
Mar 30 17:15:12 legion plasmashell[2250]: file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/Tooltip.qml:78:9: QML GridLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth"
Mar 30 17:15:12 legion plasmashell[2250]: org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout
...

suse_paul · April 1, 2024, 2:15pm

now the system froze without reacting to any keyboard entry or mouse action.
journalctl again only shows the last boot - now earlier entries.
so I probably have to check the proposal with kexec/kdump…

nobody has another idea what could cause such behaviour?

suse_paul · April 3, 2024, 10:52am

even after a regular reboot, journalctl only shows the current boot.
how can I configure journal to save/preserve boots?

arvidjaar · April 3, 2024, 10:56am

mkdir /var/log/journal

or man journald.conf, look for Storage= option (hint - Storage=persistent).

suse_paul · April 3, 2024, 5:11pm

kexec/kdump “caught” a crash.

the generated dmesg.txt contains:

...
[15194.396112] baloo_filemetad[4470]: segfault at 996718 ip 00007f83f3d30716 sp 00007ffc8eada1c8 error 6 in libQt5Gui.so.5.15.8[7f83f39de000+6f6000]
[15194.396119] Code: 10 e9 3b 00 48 8d 35 21 a3 3c 00 48 8d 3d 72 fe ff ff e8 bd b0 dc ff e9 37 ff ff ff 0f 1f 84 00 00 00 00 00 48 8b 06 48 89 07 <f0> 83 00 01 c3 90 0f 1f 40 00 53 48 89 f2 48 89 fb be 42 00 00 00
[15271.981026] baloo_filemetad[4561]: segfault at 996718 ip 00007f842f930716 sp 00007fff19a2c048 error 6 in libQt5Gui.so.5.15.8[7f842f5de000+6f6000]
[15271.981033] Code: 10 e9 3b 00 48 8d 35 21 a3 3c 00 48 8d 3d 72 fe ff ff e8 bd b0 dc ff e9 37 ff ff ff 0f 1f 84 00 00 00 00 00 48 8b 06 48 89 07 <f0> 83 00 01 c3 90 0f 1f 40 00 53 48 89 f2 48 89 fb be 42 00 00 00
[20729.087957] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead.
[30736.685919] usb 2-3: USB disconnect, device number 2
[30736.686229] xhci_hcd 0000:00:0d.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[30736.686234] usb 2-3: cmd cmplt err -108
[30736.686274] sd 1:0:0:0: [sda] tag#20 uas_zap_pending 0 uas-tag 1 inflight: CMD 
[30736.686277] sd 1:0:0:0: [sda] tag#20 CDB: Write(10) 2a 00 38 67 80 93 00 00 30 00
[30736.686301] sd 1:0:0:0: [sda] tag#20 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
[30736.686303] sd 1:0:0:0: [sda] tag#20 CDB: Write(10) 2a 00 38 67 80 93 00 00 30 00
[30736.686304] I/O error, dev sda, sector 946307219 op 0x1:(WRITE) flags 0x800 phys_seg 6 prio class 0
[30736.686312] EXT4-fs warning (device sda3): ext4_end_bio:347: I/O error 10 writing to inode 2498243 starting block 118288402)
[30736.686400] Buffer I/O error on device sda3, logical block 39867583
[30736.686416] Buffer I/O error on device sda3, logical block 39867584
[30736.686420] Buffer I/O error on device sda3, logical block 39867585
[30736.686423] Buffer I/O error on device sda3, logical block 39867586
[30736.686426] Buffer I/O error on device sda3, logical block 39867587
[30736.686429] Buffer I/O error on device sda3, logical block 39867588
[30736.686794] device offline error, dev sda, sector 767160099 op 0x1:(WRITE) flags 0x0 phys_seg 77 prio class 0
[30736.686804] EXT4-fs warning (device sda3): ext4_end_bio:347: I/O error 17 writing to inode 2886866 starting block 95895012)
[30736.686808] Buffer I/O error on device sda3, logical block 17474193
[30736.686814] EXT4-fs warning (device sda3): ext4_end_bio:347: I/O error 17 writing to inode 2886866 starting block 95895013)
[30736.686877] Buffer I/O error on device sda3, logical block 17474194
[30736.686887] Buffer I/O error on device sda3, logical block 17474195
[30736.686891] Buffer I/O error on device sda3, logical block 17474196
[30736.686929] device offline error, dev sda, sector 720042643 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
[30736.686935] EXT4-fs warning (device sda3): ext4_end_bio:347: I/O error 17 writing to inode 2886864 starting block 90005330)
[30736.686939] device offline error, dev sda, sector 720049619 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
[30736.686943] EXT4-fs warning (device sda3): ext4_end_bio:347: I/O error 17 writing to inode 2886867 starting block 90006202)
[30736.686946] device offline error, dev sda, sector 720054227 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
[30736.686950] Buffer I/O error on dev sda3, logical block 11585959, lost async page write
[30736.686955] device offline error, dev sda, sector 1214773579 op 0x1:(WRITE) flags 0x0 phys_seg 3 prio class 0
[30736.686959] EXT4-fs warning (device sda3): ext4_end_bio:347: I/O error 17 writing to inode 2626472 starting block 151846697)
[30736.686961] EXT4-fs warning (device sda3): ext4_end_bio:347: I/O error 17 writing to inode 2626472 starting block 151846698)
[30736.686964] device offline error, dev sda, sector 1327815323 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
[30736.686968] Buffer I/O error on dev sda3, logical block 87556096, lost async page write
[30736.686972] device offline error, dev sda, sector 1551764955 op 0x1:(WRITE) flags 0x0 phys_seg 23 prio class 0
[30736.686976] EXT4-fs warning (device sda3): ext4_end_bio:347: I/O error 17 writing to inode 2887129 starting block 193970619)
[30736.686978] EXT4-fs warning (device sda3): ext4_end_bio:347: I/O error 17 writing to inode 2887129 starting block 193970620)
[30736.686980] device offline error, dev sda, sector 720001331 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
[30736.686984] EXT4-fs warning (device sda3): ext4_end_bio:347: I/O error 17 writing to inode 2887130 starting block 90000166)
[30736.686986] device offline error, dev sda, sector 627366891 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
[30736.686990] Buffer I/O error on dev sda3, logical block 42, lost async page write
[30736.686994] Buffer I/O error on dev sda3, logical block 9961504, lost async page write
[30736.686998] Buffer I/O error on dev sda3, logical block 9961646, lost async page write
[30736.687001] Buffer I/O error on dev sda3, logical block 9961678, lost async page write
[30736.687005] Buffer I/O error on dev sda3, logical block 9961997, lost async page write
[30736.687008] Buffer I/O error on dev sda3, logical block 9962010, lost async page write
[30736.687012] Buffer I/O error on dev sda3, logical block 9969698, lost async page write
[30736.687015] Buffer I/O error on dev sda3, logical block 9970183, lost async page write
[30736.687026] EXT4-fs error (device sda3): ext4_check_bdev_write_error:218: comm kworker/u32:0: Error while async write back metadata
[30736.688292] Aborting journal on device sda2-8.
[30736.688311] JBD2: Error -5 detected when updating journal superblock for sda2-8.
[30736.690068] Read-error on swap-device (8:0:1923191372)
[30736.690076] Read-error on swap-device (8:0:1923191396)
[30736.690080] Read-error on swap-device (8:0:1923585988)
[30736.690082] Read-error on swap-device (8:0:1944820972)
[30736.690084] Read-error on swap-device (8:0:1923586108)
[30736.690086] Read-error on swap-device (8:0:1923586188)
[30736.690094] Read-error on swap-device (8:0:1944820980)
[30736.690097] Read-error on swap-device (8:0:1944820988)
[30736.690100] Read-error on swap-device (8:0:1944820996)
[30736.690230] EXT4-fs error (device sda2): ext4_journal_check_start:83: comm auditd: Detected aborted journal
[30736.690264] Read-error on swap-device (8:0:1925158524)
[30736.690281] EXT4-fs (sda2): I/O error while writing superblock
[30736.690296] EXT4-fs (sda2): Remounting filesystem read-only
[30736.690321] systemd-journald[632]: /run/log/journal/36c69b8628a042c082017f103223e773/system.journal: Journal file corrupted, rotating.
[30736.690515] Core dump to |/bin/false pipe failed
[30736.690566] Core dump to |/bin/false pipe failed
[30736.691202] Core dump to |/bin/false pipe failed
[30736.691304] Core dump to |/bin/false pipe failed
[30736.691346] Core dump to |/bin/false pipe failed
[30736.692218] audit: type=1701 audit(1712159895.486:1861): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=unconfined pid=1543 comm="systemd-logind" exe="/usr/lib/systemd/systemd-logind" sig=7 res=1
[30736.692367] Core dump to |/bin/false pipe failed
[30736.692758] audit: type=1701 audit(1712159895.486:1862): auid=1000 uid=1000 gid=100 ses=2 subj=unconfined pid=4064 comm="QDBusConnection" exe="/usr/bin/ksmserver" sig=7 res=1
[30736.693044] Core dump to |/bin/false pipe failed
[30736.693161] audit: type=1701 audit(1712159895.486:1863): auid=4294967295 uid=499 gid=499 ses=4294967295 subj=unconfined pid=1448 comm="dbus-daemon" exe="/usr/bin/dbus-daemon" sig=7 res=1
[30736.693686] audit: type=1701 audit(1712159895.486:1864): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=unconfined pid=632 comm="systemd-journal" exe="/usr/lib/systemd/systemd-journald" sig=6 res=1
[30736.693805] Core dump to |/bin/false pipe failed
[30736.694229] audit: type=1701 audit(1712159895.490:1865): auid=1000 uid=1000 gid=100 ses=2 subj=unconfined pid=5054 comm="pulseaudio" exe="/usr/bin/pulseaudio" sig=6 res=1
[30736.694394] audit: type=1701 audit(1712159895.490:1866): auid=1000 uid=1000 gid=100 ses=2 subj=unconfined pid=4238 comm="gdbus" exe="/usr/lib/org_kde_powerdevil" sig=7 res=1
[30736.694434] audit: type=1701 audit(1712159895.490:1867): auid=1000 uid=1000 gid=100 ses=2 subj=unconfined pid=5324 comm="gdbus" exe="/usr/lib/evolution-data-server/evolution-addressbook-factory" sig=7 res=1
[30736.694510] audit: type=1701 audit(1712159895.490:1868): auid=1000 uid=1000 gid=100 ses=2 subj=unconfined pid=4039 comm="gdbus" exe="/usr/lib/xdg-desktop-portal" sig=7 res=1
[30736.694609] Core dump to |/bin/false pipe failed
[30736.697546] audit: type=1701 audit(1712159895.490:1869): auid=1000 uid=1000 gid=100 ses=2 subj=unconfined pid=5176 comm="gdbus" exe="/usr/lib/goa-daemon" sig=7 res=1
[30736.697552] audit: type=1701 audit(1712159895.490:1870): auid=1000 uid=1000 gid=100 ses=2 subj=unconfined pid=5273 comm="gdbus" exe="/usr/lib/evolution-data-server/evolution-calendar-factory" sig=7 res=1
[30736.698184] Core dump to |/bin/false pipe failed
[30736.698231] Core dump to |/bin/false pipe failed
[30736.698237] Core dump to |/bin/false pipe failed
[30736.698254] Core dump to |/bin/false pipe failed
[30736.698258] Core dump to |/bin/false pipe failed
[30736.698274] Core dump to |/bin/false pipe failed
[30736.698299] Core dump to |/bin/false pipe failed
[30736.698356] Core dump to |/bin/false pipe failed
[30736.698366] Core dump to |/bin/false pipe failed
[30736.698385] Core dump to |/bin/false pipe failed
[30736.698396] Core dump to |/bin/false pipe failed
[30736.698409] Core dump to |/bin/false pipe failed
[30736.698631] Core dump to |/bin/false pipe failed
[30736.698711] Core dump to |/bin/false pipe failed
[30736.698716] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007
[30736.698733] CPU: 8 PID: 1 Comm: systemd Kdump: loaded Tainted: G                  N 5.14.21-150500.55.52-default #1 SLE15-SP5 16dce122fa9976f628762b347f683c987c5bef4c
[30736.698741] Hardware name: LENOVO 82JD/LNVNB161216, BIOS H1CN56WW 09/19/2023
[30736.698745] Call Trace:
[30736.698752]  <TASK>
[30736.698759]  dump_stack_lvl+0x45/0x5b
[30736.698774]  panic+0x118/0x2f0
[30736.698778]  do_exit+0x962/0xa80
[30736.698785]  do_group_exit+0x3a/0xa0
[30736.698790]  get_signal+0x121/0x8c0
[30736.698794] Core dump to |/bin/false pipe failed
[30736.698799]  arch_do_signal_or_restart+0xc2/0x730
[30736.698808]  ? force_sig_info_to_task+0xab/0xf0
[30736.698813]  exit_to_user_mode_prepare+0xbb/0x240
[30736.698821]  irqentry_exit_to_user_mode+0x5/0x30
[30736.698828]  asm_exc_page_fault+0x59/0x60
[30736.698840] RIP: 0033:0x7f01197a33ec
[30736.698847] Code: c4 10 49 39 f7 0f 87 13 01 00 00 49 8b 04 24 48 85 c0 0f 84 a9 00 00 00 49 8b 54 24 f8 48 3b 15 9a 8b 01 00 0f 87 1a 01 00 00 <4c> 8b 90 58 04 00 00 49 39 d6 48 8b b8 50 04 00 00 4c 0f 42 f2 4c
[30736.698852] RSP: 002b:00007ffe24c893b0 EFLAGS: 00010246
[30736.698854] Core dump to |/bin/false pipe failed
[30736.698854] 
[30736.698855] RAX: 00007f01194233d0 RBX: 0000000000000006 RCX: 0000000000000000
[30736.698857] RDX: 0000000000000001 RSI: 0000000000000006 RDI: 00007f01159fe4a2
[30736.698858] RBP: 00007f01190b0000 R08: 0000000000801000 R09: 0000000000800000
[30736.698858] R10: 0000000000000005 R11: 000000000000025f R12: 00007f01190b0078
[30736.698859] R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000006
[30736.698861]  </TASK>
[30736.698866] Core dump to |/bin/false pipe failed

the system is running on /dev/sda:
df -h

Dateisystem    Größe Benutzt Verf. Verw% Eingehängt auf
devtmpfs        4,0M    8,0K  4,0M    1% /dev
tmpfs           7,5G    4,0K  7,5G    1% /dev/shm
tmpfs           3,0G    2,4M  3,0G    1% /run
tmpfs           4,0M       0  4,0M    0% /sys/fs/cgroup
/dev/sda2       293G     20G  259G    8% /
/dev/sda1       511M     21M  491M    5% /boot/efi
/dev/sda3       607G    413G  164G   72% /home
tmpfs           1,5G    156K  1,5G    1% /run/user/1000

crash /boot/vmlinux-5.14.21-150500.55.52-default.gz /var/crash/2024-04-03-17:58/vmcore

...
crash: /var/tmp/vmlinux-5.14.21-150500.55.52-default.gz_CTtYqd: no debugging data available
crash: vmlinux-5.14.21-150500.55.52-default.debug: debuginfo file not found

crash: either install the appropriate kernel debuginfo package, or
       copy vmlinux-5.14.21-150500.55.52-default.debug to this machine

vmlinux-5.14.21-150500.55.52-default.debug is located in /boot
how can I make it accessible by crash?

hui · April 3, 2024, 5:49pm

You need to install the kernel debug package. For that you need to enable the debug repository.

YaST → Software repositories
mark “Debug repository” and check “Activated” → Ok

Then

sudo zypper ref
sudo zypper in kernel-default-debuginfo

suse_paul · April 3, 2024, 6:01pm

...
(1/2) Installing: kernel-default-debugsource-5.14.21-150500.53.2.x86_64 ...................................................................................................................[done]
(2/2) Installing: kernel-default-debuginfo-5.14.21-150500.53.2.x86_64 .....................................................................................................................[done]

vmlinux-5.14.21-150500.55.52-default.debug is still missing

suse_paul · April 9, 2024, 12:07pm

since the -55.52 debug information is not in the debug repository (only for -53.2):
can it be found somewhere else?

arvidjaar · April 9, 2024, 12:16pm

andrei@leap155:~/src/systemd> zypper se -sx kernel-default-debuginfo
Loading repository data...
Reading installed packages...

S | Name                     | Type    | Version                | Arch   | Repository
--+--------------------------+---------+------------------------+--------+---------------------------------------------------------------------------
  | kernel-default-debuginfo | package | 5.14.21-150500.55.52.1 | x86_64 | Update repository with debuginfo for updates from SUSE Linux Enterprise 15
  | kernel-default-debuginfo | package | 5.14.21-150500.55.49.1 | x86_64 | Update repository with debuginfo for updates from SUSE Linux Enterprise 15
  | kernel-default-debuginfo | package | 5.14.21-150500.55.44.1 | x86_64 | Update repository with debuginfo for updates from SUSE Linux Enterprise 15
  | kernel-default-debuginfo | package | 5.14.21-150500.55.39.1 | x86_64 | Update repository with debuginfo for updates from SUSE Linux Enterprise 15
  | kernel-default-debuginfo | package | 5.14.21-150500.55.36.1 | x86_64 | Update repository with debuginfo for updates from SUSE Linux Enterprise 15
  | kernel-default-debuginfo | package | 5.14.21-150500.55.31.1 | x86_64 | Update repository with debuginfo for updates from SUSE Linux Enterprise 15
  | kernel-default-debuginfo | package | 5.14.21-150500.55.28.1 | x86_64 | Update repository with debuginfo for updates from SUSE Linux Enterprise 15
  | kernel-default-debuginfo | package | 5.14.21-150500.55.22.1 | x86_64 | Update repository with debuginfo for updates from SUSE Linux Enterprise 15
  | kernel-default-debuginfo | package | 5.14.21-150500.55.19.1 | x86_64 | Update repository with debuginfo for updates from SUSE Linux Enterprise 15
  | kernel-default-debuginfo | package | 5.14.21-150500.55.12.1 | x86_64 | Update repository with debuginfo for updates from SUSE Linux Enterprise 15
  | kernel-default-debuginfo | package | 5.14.21-150500.55.7.1  | x86_64 | Update repository with debuginfo for updates from SUSE Linux Enterprise 15
  | kernel-default-debuginfo | package | 5.14.21-150500.53.2    | x86_64 | Debug Repository
andrei@leap155:~/src/systemd>

suse_paul · April 9, 2024, 1:30pm

 zypper se -sx kernel-default-debuginfo
Refreshing service 'NVIDIA'.
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...

S  | Name                     | Type    | Version             | Arch   | Repository
---+--------------------------+---------+---------------------+--------+-----------------
i+ | kernel-default-debuginfo | package | 5.14.21-150500.53.2 | x86_64 | Debug Repository

what (repository) did I miss?
I activated additionally “Update Repository (Debug)” → no difference

arvidjaar · April 9, 2024, 1:33pm

andrei@leap155:~/src/systemd> zypper lr repo-sle-debug-update
Alias          : repo-sle-debug-update
Name           : Update repository with debuginfo for updates from SUSE Linux Enterprise 15
URI            : http://download.opensuse.org/debug/update/leap/15.5/sle/
Enabled        : No
GPG Check      : ----
Priority       : 99 (default priority)
Autorefresh    : On
Keep Packages  : Off
Type           : rpm-md
GPG Key URI    :
Path Prefix    : /
Parent Service :
Keywords       : debug
Repo Info Path : /etc/zypp/repos.d/repo-sle-debug-update.repo
MD Cache Path  : /var/cache/zypp/raw/repo-sle-debug-update

suse_paul · April 9, 2024, 2:03pm

thanks, now crash could find the debug info.

crash /boot/vmlinux-5.14.21-150500.55.52-default.gz /var/crash/2024-04-08-16\:01/vmcore 
...
      KERNEL: /boot/vmlinux-5.14.21-150500.55.52-default.gz  [TAINTED] 
   DEBUGINFO: /usr/lib/debug/boot/vmlinux-5.14.21-150500.55.52-default.debug
    DUMPFILE: /var/crash/2024-04-08-16:01/vmcore  [PARTIAL DUMP]
        CPUS: 16
        DATE: Mon Apr  8 16:01:13 CEST 2024
      UPTIME: 2 days, 13:24:08
LOAD AVERAGE: 0.60, 0.47, 0.39
       TASKS: 2286
    NODENAME: legion
     RELEASE: 5.14.21-150500.55.52-default
     VERSION: #1 SMP PREEMPT_DYNAMIC Tue Mar 5 16:53:41 UTC 2024 (a62851f)
     MACHINE: x86_64  (2300 Mhz)
      MEMORY: 15.8 GB
       PANIC: "Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b"
         PID: 1
     COMMAND: "systemd"
        TASK: ffff974880e38000  [THREAD_INFO: ffff974880e38000]
         CPU: 8
       STATE: TASK_RUNNING (PANIC)

crash> bt
PID: 1      TASK: ffff974880e38000  CPU: 8   COMMAND: "systemd"
 #0 [ffffa3d9c007bc08] machine_kexec at ffffffffb80840f3
 #1 [ffffa3d9c007bc60] __crash_kexec at ffffffffb818736a
 #2 [ffffa3d9c007bd20] panic at ffffffffb8a61377
 #3 [ffffa3d9c007bda8] do_exit at ffffffffb80b6aa2
 #4 [ffffa3d9c007be00] do_group_exit at ffffffffb80b6d7a
 #5 [ffffa3d9c007be28] get_signal at ffffffffb80c52b1
 #6 [ffffa3d9c007be70] arch_do_signal_or_restart at ffffffffb803d9c2
 #7 [ffffa3d9c007bf30] exit_to_user_mode_prepare at ffffffffb8159b8b
 #8 [ffffa3d9c007bf48] irqentry_exit_to_user_mode at ffffffffb8a6dc35
 #9 [ffffa3d9c007bf50] asm_exc_page_fault at ffffffffb8c00f39
    RIP: 00005633dd7b52d0  RSP: 00007ffe2f9d4878  RFLAGS: 00010206
    RAX: 0000000000000000  RBX: 00005633ddf76620  RCX: 0000000000000010
    RDX: 00007ffe2f9d4880  RSI: 00007ffe2f9d49b0  RDI: 0000000000000007
    RBP: 00007ffe2fad2dc8   R8: 0000000000000000   R9: 0000000000000002
    R10: 00007fbc6e30ac20  R11: 00005633ddef52a0  R12: 00005633dd8e19a0
    R13: 00005633de074640  R14: 0000000000000015  R15: ffffffffffffff01
    ORIG_RAX: ffffffffffffffff  CS: 0033  SS: 002b
crash>

does that tell anything about the reason for the kernel panic ans/or where to lo further?

suse_paul · April 21, 2024, 12:02pm

after activating kexec/kdump via yast, it caught two crashes, but then it stopped.
the last crashes where not caught.

I deactivated and reactivated kexec/kdump again, to no avail.

how can I reactivate it again?

suse_paul · April 24, 2024, 12:37pm

now the screen just froze and I could switch with Alt-Ctrl-F1 to a console.

Is there anything I can do FROM THE COMMAND LINE to “reset” the screen, or “properly” logoff?

arvidjaar · April 25, 2024, 4:22am

In case of GUI session you would need to send request to your GUI session manager, which is DE specific.

You can simply kill all processes in a session using

loginctl kill-session

You will need session number from

loginctl

output.