Kernel 6.15 unbootable

Support
1

Hello,

Requirements:

I have [Searched] the forum for my issue and found nothing related or helpful
I have checked the [Resources category ]([Resources Index])
I have reviewed the [Wiki] for relevant information
I have read the the [Release Notes and Errata]

OpenMandriva Lx version:

Rome latest kernel

Desktop environment (KDE, LXQT…):

KDE plasma 6 Wayland

Description of the issue (screenshots if relevant):

Kernel 6.15 does not boot and checking logs to my untrained eyes could not uncover anything.

Relevant informations (hardware involved, software version, logs or output…):

After updating with the built in update feature the latest kernel causes the system to crash, blinking the caps lock key. I have tried uninstalling and installing the kernel and updating grub2. This is the extent of the things I have tried besides the obvious of trying to run the commands the updater runs as per the wiki page.

Which logs should I look in and/or post? I followed many kernel panic threads but none of them have posted logs relevant to my issues. The logs indicate the system stops responding before it can post an error.

Using an intel evo with built in intel arc graphics. Booting off a USB ssd drive. on an MSI prestige 16 AI evo B1MG

Booting old kernel works fine. I looked for other kernels in the repos that were 6.15 but there is only one from what I saw.

Thanks for any help. It’s been 10 years it feels like since I’ve had to post in a forum, usually I can figure it out from other posts.
Sucsessful and unsucsessful boot respectively:

-- Boot ef21ba8e91cb430fa7b10cc449b64c5d --
May 12 05:37:09 kernel: CPU topo: Boot CPU APIC ID not the first enumerated APIC ID: 20 != 10
May 12 05:37:09 kernel: CPU topo: [Firmware Bug]: APIC enumeration order not specification compliant
May 12 05:37:09 kernel: Spectre V2 : WARNING: Unprivileged eBPF is enabled with eIBRS on, data leaks possible via Spectre v2 BHB attacks!
May 12 05:37:09 kernel:   #2  #4  #5  #7  #9 #11
May 12 05:37:09 kernel: pnp 00:03: disabling [mem 0x00000000-0x00000fff] because it overlaps 0000:00:02.0 BAR 7 [mem 0x00000000-0x06ffffff 64bit pref]
May 12 05:37:09 kernel: pnp 00:03: disabling [mem 0x00000000-0x00000fff] because it overlaps 0000:00:02.0 BAR 7 [mem 0x00000000-0x06ffffff 64bit pref]
May 12 05:37:09 kernel: hpet_acpi_add: no address or irqs in _CRS
May 12 05:37:09 kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
May 12 05:37:09 kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
May 12 05:37:10 kernel: wmi_bus wmi_bus-PNP0C14:00: [Firmware Bug]: WQAK data block query control method not found
May 12 05:37:10 kernel: wmi_bus wmi_bus-PNP0C14:00: [Firmware Bug]: WQAL data block query control method not found
May 12 05:37:10 kernel: wmi_bus wmi_bus-PNP0C14:00: [Firmware Bug]: WMAJ method block execution control method not found
May 12 05:37:10 kernel: pci 10000:e0:06.2: Primary bus is hard wired to 0
May 12 05:37:10 kernel: pci 10000:e0:06.2: Primary bus is hard wired to 0
May 12 05:37:11 kernel: pci 10000:e1:00.0: can't override BIOS ASPM; OS doesn't have ASPM control
May 12 05:37:11 kernel: pcieport 10000:e0:06.2: can't derive routing for PCI INT C
May 12 05:37:11 kernel: pcieport 10000:e0:06.2: PCI INT C: no GSI
May 12 05:37:11 kernel: pcieport 10000:e0:06.2: can't derive routing for PCI INT A
May 12 05:37:11 kernel: nvme 10000:e1:00.0: PCI INT A: no GSI
-- Boot fab80a9cea9c41fd8fa8684d29a1ed24 --
May 12 05:39:00 kernel: CPU topo: Boot CPU APIC ID not the first enumerated APIC ID: 20 != 10
May 12 05:39:00 kernel: CPU topo: [Firmware Bug]: APIC enumeration order not specification compliant
May 12 05:39:00 kernel: Spectre V2 : WARNING: Unprivileged eBPF is enabled with eIBRS on, data leaks possible via Spectre v2 BHB attacks!
May 12 05:39:00 kernel:   #2  #4  #5  #7  #9 #11
May 12 05:39:00 kernel: pnp 00:03: disabling [mem 0x00000000-0x00000fff] because it overlaps 0000:00:02.0 BAR 7 [mem 0x00000000-0x06ffffff 64bit pref]
May 12 05:39:00 kernel: pnp 00:03: disabling [mem 0x00000000-0x00000fff] because it overlaps 0000:00:02.0 BAR 7 [mem 0x00000000-0x06ffffff 64bit pref]
May 12 05:39:00 kernel: hpet_acpi_add: no address or irqs in _CRS
May 12 05:39:00 kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
May 12 05:39:00 kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
May 12 05:39:01 kernel: wmi_bus wmi_bus-PNP0C14:00: [Firmware Bug]: WQAK data block query control method not found
May 12 05:39:01 kernel: wmi_bus wmi_bus-PNP0C14:00: [Firmware Bug]: WQAL data block query control method not found
May 12 05:39:01 kernel: wmi_bus wmi_bus-PNP0C14:00: [Firmware Bug]: WMAJ method block execution control method not found
May 12 05:39:01 kernel: pci 10000:e0:06.2: Primary bus is hard wired to 0
May 12 05:39:01 kernel: pci 10000:e0:06.2: Primary bus is hard wired to 0
May 12 05:39:02 kernel: pci 10000:e1:00.0: can't override BIOS ASPM; OS doesn't have ASPM control
May 12 05:39:02 kernel: pcieport 10000:e0:06.2: can't derive routing for PCI INT C
May 12 05:39:02 kernel: pcieport 10000:e0:06.2: PCI INT C: no GSI
May 12 05:39:02 kernel: pcieport 10000:e0:06.2: can't derive routing for PCI INT A
May 12 05:39:02 kernel: nvme 10000:e1:00.0: PCI INT A: no GSI
May 12 05:39:06 systemd-journald[708]: File /var/log/journal/9794c032fb424b1fb580ab91cfa70fe0/system.journal corrupted or uncleanly shut down, renaming and replacing.
May 12 05:39:07 kernel: resource: resource sanity check: requesting [mem 0x00000000fedc0000-0x00000000fedcffff], which spans more than pnp 00:03 [mem 0xfedc0000-0xfedc7fff]
May 12 05:39:07 kernel: caller igen6_probe+0x199/0xb00 [igen6_edac] mapping multiple BARs
May 12 05:39:07 kernel: intel_pmc_core INT33A1:00: Assuming a default substate order for this platform
May 12 05:39:08 kernel: FAT-fs (sda1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
May 12 05:39:08 kernel: msi_ec: Firmware version is not supported: '15A1EMS1.109'
May 12 05:39:08 kernel: spi-nor spi0.0: supply vcc not found, using dummy regulator
May 12 05:39:08 kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: Parent card not yet available, widget card binding deferred
May 12 05:39:08 kernel: skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 3
May 12 05:39:10 kernel: Bluetooth: hci0: Failed to read codec capabilities (-95)
May 12 05:39:10 kernel: Bluetooth: hci0: Failed to read codec capabilities (-95)
May 12 05:39:15 (uetoothd)[931]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
May 12 05:39:15 kernel: nvme nvme0: using unchecked data buffer
May 12 05:39:16 kernel: Bluetooth: hci0: Failed to read codec capabilities (-95)
May 12 05:39:16 kernel: Bluetooth: hci0: Failed to read codec capabilities (-95)
May 12 05:39:17 dbus-broker-launch[927]: Activation request for 'org.freedesktop.Avahi' failed: The systemd unit 'dbus-org.freedesktop.Avahi.service' could not be found.
May 12 05:39:18 dbus-broker-launch[927]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.
May 12 05:39:18 systemd-xdg-autostart-generator[1035]: Configuration file /home/dillon/.config/autostart/draketray.desktop is marked executable. Please remove executable permission bits>
May 12 05:39:18 dbus-broker-launch[1040]: Service file '/usr/share//dbus-1/services/obex-client.service' is not named after the D-Bus name 'org.bluez.obex.client'.
May 12 05:39:18 dbus-broker-launch[1040]: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1>
May 12 05:39:18 dbus-broker-launch[1040]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
May 12 05:39:18 dbus-broker-launch[1040]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notification>
May 12 05:39:19 systemd-xdg-autostart-generator[1112]: Configuration file /home/dillon/.config/autostart/draketray.desktop is marked executable. Please remove executable permission bits>
May 12 05:39:21 xdg-desktop-por[1131]: Choosing gtk.portal for org.freedesktop.impl.portal.Lockdown as a last-resort fallback
May 12 05:39:21 kernel: block nvme0n1: No UUID available providing old NGUID
May 12 05:39:21 wireplumber[1049]: default: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner
May 12 05:39:22 baloo_file[1123]: qt.dbus.integration: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.28'
May 12 05:39:22 baloo_file[1123]: qt.dbus.integration: QDBusConnection: name 'org.freedesktop.UPower' had owner '' but we thought it was ':1.30'
May 12 05:39:24 wireplumber[1049]: s-monitors-utils: skipping device libcamera:\_SB_.PC00.XHCI.RHUB.HS05-5:1.0-5986:1193
May 12 05:39:24 wireplumber[1049]: s-monitors-utils: skipping device libcamera:\_SB_.PC00.XHCI.RHUB.HS05-5:1.2-5986:1193
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 124 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 124 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 146 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 146 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 33 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 33 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 220 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 220 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 219 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 219 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 209 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 209 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 217 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 217 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 215 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 215 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 223 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 223 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 213 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 213 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 221 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 221 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 211 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 211 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 218 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 218 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 216 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 216 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 224 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 224 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 214 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 214 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 222 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 222 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 212 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 212 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 164 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 164 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 122 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 122 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 32 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 32 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 202 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 202 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 136 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 136 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 144 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 144 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 134 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 134 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 142 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 142 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 132 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 132 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 140 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 140 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 130 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 130 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 139 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 139 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 129 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 129 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 137 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 137 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 127 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 127 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 145 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 145 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 135 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 135 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 143 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 143 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 133 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 133 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 141 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 141 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 131 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 131 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 138 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 138 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 128 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 128 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 123 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 123 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 165 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 165 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 174 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 174 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 182 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 182 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 172 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 172 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 180 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 180 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 170 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 170 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 179 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 179 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 169 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 169 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 177 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 177 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 167 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 167 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 175 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 175 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 183 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 183 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 173 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 173 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 181 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 181 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 171 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 171 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 178 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 178 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 168 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 168 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 176 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 176 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 166 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 166 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 155 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 155 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 18 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 18 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 125 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 125 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 187 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 187 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 186 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 186 affinity is now unmanaged
May 12 05:39:25 irqbalance[933]: Cannot change IRQ 208 affinity: Read-only file system
May 12 05:39:25 irqbalance[933]: IRQ 208 affinity is now unmanaged
May 12 05:39:29 kded6[1254]: QDBusObjectPath: invalid path "/modules/oom-notifier"
May 12 05:39:29 kded6[1254]: kf.dbusaddons: The kded module name "oom-notifier" is invalid!
May 12 05:39:29 kactivitymanagerd[1304]: kf.windowsystem: virtual void KX11Extras::connectNotify(const QMetaMethod &) may only be used on X11
May 12 05:39:29 kactivitymanagerd[1304]: kf.windowsystem: virtual void KX11Extras::connectNotify(const QMetaMethod &) may only be used on X11
May 12 05:39:29 plasmashell[1271]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:178:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutA>
                                   file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:201:9
May 12 05:39:30 kded6[1254]: QDBusObjectPath: invalid path "/modules/plasma-session-shortcuts"
May 12 05:39:30 kded6[1254]: kf.dbusaddons: The kded module name "plasma-session-shortcuts" is invalid!
May 12 05:39:30 kded6[1254]: QDBusObjectPath: invalid path "/modules/wpad-detector"
May 12 05:39:30 kded6[1254]: kf.dbusaddons: The kded module name "wpad-detector" is invalid!
May 12 05:39:30 plasmashell[1271]: Toolbox not loading, toolbox package is either invalid or disabled.
May 12 05:39:30 kconf_update[1383]: kf.config.kconf_update: /usr/share/kconf_update/ark.upd defined Version=5 but Version=6 was expected
May 12 05:39:30 kconf_update[1383]: kf.config.kconf_update: /usr/share/kconf_update/dolphin_directorysizemode.upd defined Version=5 but Version=6 was expected
May 12 05:39:30 kconf_update[1383]: kf.config.kconf_update: /usr/share/kconf_update/konsole.upd defined Version=5 but Version=6 was expected
May 12 05:39:30 kconf_update[1383]: kf.config.kconf_update: /usr/share/kconf_update/okular.upd defined Version=5 but Version=6 was expected
May 12 05:39:30 dbus-broker-launch[927]: Activation request for 'org.freedesktop.ModemManager1' failed: The systemd unit 'dbus-org.freedesktop.ModemManager1.service' could not be found.
May 12 05:39:30 kded6[1254]: kf.modemmanagerqt: Failed enumerating MM objects: "org.freedesktop.DBus.Error.NameHasNoOwner" 
                              "Could not activate remote peer 'org.freedesktop.ModemManager1': activation request failed: unknown unit"
May 12 05:39:30 bluetoothd[931]: /builddir/build/BUILD/bluez-5.82-build/bluez-5.82/src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon pow>
May 12 05:39:30 kded6[1254]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.stereo-fallback.monitor"
May 12 05:39:31 org_kde_powerdevil[1317]: org.kde.powerdevil: [DDCutilDetector]: Failed to initialize callback
May 12 05:39:31 org_kde_powerdevil[1317]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this ha>
May 12 05:39:31 org_kde_powerdevil[1317]: org.kde.powerdevil: Handle button events action could not check for screen configuration
May 12 05:39:31 org_kde_powerdevil[1317]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this ha>
May 12 05:39:32 kernel: warning: `kdeconnectd' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
May 12 05:39:32 kdeconnectd[1467]: 2025-05-12T05:39:32 default: Error sending UDP packet: QAbstractSocket::NetworkError
May 12 05:39:32 kdeconnectd[1467]: 2025-05-12T05:39:32 kdeconnect.core: Failed to open any MDNS client sockets
May 12 05:39:32 kdeconnectd[1467]: 2025-05-12T05:39:32 kdeconnect.core: Failed to open any MDNS server sockets
May 12 05:39:32 kdeconnectd[1467]: 2025-05-12T05:39:32 qt.bluetooth.bluez: Bluetooth device is powered off
May 12 05:39:32 kdeconnectd[1530]: QThreadStorage: entry 8 destroyed before end of thread 0x55a497235a20
May 12 05:39:32 kdeconnectd[1530]: QThreadStorage: entry 3 destroyed before end of thread 0x55a497235a20
May 12 05:39:32 kdeconnectd[1530]: QThreadStorage: entry 2 destroyed before end of thread 0x55a497235a20
May 12 05:39:33 xdg-desktop-por[1131]: Choosing gtk.portal for org.freedesktop.impl.portal.Wallpaper as a last-resort fallback
May 12 05:39:37 plasmashell[1271]: org.kde.applets.brightness: D-Bus action "KeyboardBrightnessControl" is not available at service "org.kde.Solid.PowerManagement"
May 12 05:39:37 plasmashell[1271]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.stereo-fallback.monitor"
May 12 05:39:42 kwalletd6[1672]: Application "Chromium" using kwallet without parent window!
May 12 05:39:57 kwin_wayland[1121]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
May 12 05:40:04 plasmashell[1271]: kf.windowsystem: static void KX11Extras::forceActiveWindow(WId, long) may only be used on X11
May 12 05:40:06 plasmashell[1271]: kf.windowsystem: static void KX11Extras::forceActiveWindow(WId, long) may only be used on X11
May 12 05:40:24 baloorunner[1946]: qt.dbus.integration: QDBusConnection: couldn't handle call to Teardown, no slot matched
May 12 05:40:24 baloorunner[1946]: qt.dbus.integration: QDBusConnection: couldn't handle call to Teardown, no slot matched
May 12 05:40:24 baloorunner[1946]: qt.dbus.integration: Could not find slot Krunner1Adaptor::Teardown
May 12 05:40:24 konsole[1957]: QLayout: Cannot add a null widget to QHBoxLayout/
May 12 05:41:38 kernel: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=5661 end=5662) time 271 us, min 2385, max 2399, scanline start 2372, end 2374
May 12 05:43:51 kwin_wayland[1121]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
May 12 05:44:09 kdeconnectd[1467]: 2025-05-12T05:44:09 kdeconnect.core: Failed to send mDNS query: Cannot assign requested address
May 12 05:44:10 plasmashell[1271]: qrc:/qt/qml/org/kde/plasma/components/ScrollView.qml:53:29: QML ScrollBar: Binding loop detected for property "visible":
                                   qrc:/qt/qml/org/kde/plasma/components/ScrollBar.qml:24:5
May 12 05:44:10 plasmashell[1271]: qrc:/qt/qml/org/kde/plasma/components/ScrollView.qml:53:29: QML ScrollBar: Binding loop detected for property "visible":
                                   qrc:/qt/qml/org/kde/plasma/components/ScrollBar.qml:24:5
May 12 05:44:11 systemd-coredump[2332]: [🡕] Process 2313 (chrome) of user 1001 dumped core.
                                        
                                        Stack trace of thread 1:
                                        #0  0x00007ff9049fb262 __mmap (libc.so.6 + 0x10d262)
                                        #1  0x00007ff9049317b3 getrandom_vdso (libc.so.6 + 0x437b3)
                                        #2  0x00007ff905ffc316 startParsing (libexpat.so.1 + 0x2c316)
                                        #3  0x00007ff906001caf XML_ParseBuffer (libexpat.so.1 + 0x31caf)
                                        #4  0x00007ff906182208 FcConfigParseAndLoadFromMemoryInternal (libfontconfig.so.1 + 0x58208)
                                        #5  0x00007ff90616a318 FcInitLoadOwnConfig (libfontconfig.so.1 + 0x40318)
                                        #6  0x00007ff90616a4fe FcInitLoadConfigAndFonts (libfontconfig.so.1 + 0x404fe)
                                        #7  0x00007ff90616a651 FcInit (libfontconfig.so.1 + 0x40651)
                                        #8  0x00005563b3454c32 _ZN4base12NoDestructorIN3gfx12_GLOBAL__N_116GlobalFontConfigEEC2IJEEEDpOT_ (/usr/lib64/chromium/chrome + 0x7f63c32)
                                        ELF object binary architecture: AMD x86-64
May 12 05:44:11 drkonqi-coredump-launcher[2345]: Unable to find file for pid 2313 expected at "kcrash-metadata/chrome.fab80a9cea9c41fd8fa8684d29a1ed24.2313.ini"
May 12 05:44:11 drkonqi-coredump-launcher[2344]: Unable to find file for pid 2313 expected at "kcrash-metadata/chrome.fab80a9cea9c41fd8fa8684d29a1ed24.2313.ini"
May 12 05:44:11 drkonqi-coredump-launcher[2345]: Nothing handled the dump :O
May 12 05:44:11 drkonqi-coredump-launcher[2344]: Nothing handled the dump :O
May 12 05:46:04 (pcscd)[2636]: pcscd.service: Referenced but unset environment variable evaluates to an empty string: PCSCD_ARGS
May 12 05:46:55 irqbalance[933]: Cannot change IRQ 210 affinity: Read-only file system
May 12 05:46:55 irqbalance[933]: IRQ 210 affinity is now unmanaged
2

Welcome! We are happy to see you here and we hope you decide to make this your home.

How do you have 6.15? I am up to date and on 6.14.2-3 and 6.15 is a long way off.

3

I’d hazard a guess @Roadsurfer has installed the kernel-rc-desktop package.

That package contains kernel release candidates from the upstream mainline / development tree, currently in Rome the latest version of that package is on 6.15.0.rc2 as the 6.15.0 kernel is still in development.

It is not recommended to run those RC kernels unless you have a specific issue they may address.

As they are mainline release candidates you can expect breakages/regressions with them until they make it to final release after the usual kernel development cycle finalises which I am sure you are already aware of.

@Roadsurfer in order to get back into a working kernel you can boot into your previous working kernel version which should be 6.14.2 and then once on the desktop you can safely remove the desktop-rc-kernel package to remove the 6.15.0.rc2 kernel to prevent accidentally booting into that version since it is not working for you.

Unless of course there is a specific reason you are requiring the mainline / development kernel which you never mentioned in your post, so we are flying blind on that part. :slightly_smiling_face:

I will tag @bero for further advices on the kernel topic.

4

Yes, but I saw no "whys and wherefores’

1 Like
5

I have kernel-rc-desktop-6.15.0-0.rc5.1 installed in 2 Cooker VM’s and it works there. I also have it installed on my laptop where it also works.

6

When posting logs of over about 20-25 lines please put them in a .txt file and post the file. And please post all of the log. In your post I only see log of a successful boot.

To create journal log of previous failed boot if it was the last boot before the current one:

journalctl -b -1 > journal-1.txt

For kernel and systemd only log:

journalctl -k -b -1 > dmesg-1.txt

And post the .txt files here.

7

I have this kernel running on rolling OM:
6.15.0-desktop-0.rc2.3omv2590 and at least in my case it is stable.

However, if I remember correctly, the system upgrdaed from 6.14 to this one automatically just by running disrto-sync. I haven’t actively installed or selected it.

1 Like
8

And I remember when that happened. That was why I was asking how he got it. Did he get it by accident, like you, or did he install it manually?

9

Edit: Apologies for this off topic explanation but it seemed important.

Note: The rc in kernel-rc-desktop means release candidate. These usually work pretty well but they are for testing purposes.

I hope this explanation makes sense to others. Your using the package version number which is not relevant to this. It is package names that are relevant. What can happen automatically is the an installed version of kernel-desktop will upgrade to a newer version of kernel-desktop just like other packages. kernel-desktop can not upgrade to kernel-rc-desktop they are separate packages. So if any user did not themselves install kernel-rc-desktop yet you have it on your system something triggered that install, and that something would for sure be a bug.

Once kernel-rc-desktop gets installed then and only then can it automatically upgrade to a newer version. But no kernel-desktop can become kernel-rc-desktop. As an example no version of kate would ever upgrade to kwrite though they are sister packages.

There were kernel-rc-desktop-6.14.x version before whereas now we have kernel-rc-desktop-6.15.x. Currently we have kernel-desktop-6.14.x where previously it was kernel-desktop-6.13.x and when kernel.org releases it we will have kernel-desktop-6.15.x and then we will see kernel-rc-desktop-6.16.x.

Further we did have something not to long ago that did trigger incorrect installation of kernel-rc-desktop along with I think kernel-rc-desktop-modules-hfs. My memory tells me it was hfsutils but my memory is not perfect. That was a bug that has been fixed. Users that have those modules should remove them and unless you wish to be a kernel tester you should also remove any instance of kernel-rc-desktop.

Most users do not need any kernel-desktop-modules-hfs or kernel-rc-desktop-modules-hfs so unless you know you need it for something these should be removed. These were installed as a part of that bug mentioned in the above paragraph.

10

Indeed.
In my case the installation was triggered by a distro-sync

2025-04-18T00:47:46+0300 DDEBUG Command: dnf distro-sync --refresh --allowerasing 
...
...
2025-04-18T00:47:56+0300 DEBUG Completion plugin: Generating completion cache...
2025-04-18T00:47:57+0300 DEBUG --> Starting dependency resolution
...
...
2025-04-18T00:47:57+0300 DEBUG ---> Package kernel-desktop.x86_64 6.14.2-2 will be installed
2025-04-18T00:47:57+0300 DEBUG ---> Package kernel-desktop-modules-hfs.x86_64 6.14.2-2 will be installed
2025-04-18T00:47:57+0300 DEBUG ---> Package kernel-rc-desktop.x86_64 6.15.0-0.rc2.2 will be installed
2025-04-18T00:47:57+0300 DEBUG ---> Package kernel-rc-desktop-modules-hfs.x86_64 6.15.0-0.rc2.2 will be installed
...
...

And as @ben79 mentioned, unless you really need those modules or want to be a kernel tester, you should just unintall them and have the regular desktop-kernel only.

I’m ok with testing the kernel and it was treating me very well so far :slight_smile:

1 Like
11

My whole point is that dnf can not do this. There was a bug in the hfs-utils package that caused the installation or kernel-desktop-modules-hfs, Package kernel-rc-desktop, and kernel-rc-desktop-modules-hfs. The solution is to remove all of those and hfs-utils. Had hfs-utils been removed before the dnf distro-sync --refresh --allowerasing this would not have happened. That was the bug.

Edit: As I recall (that pesky memory again) some other package upgrade was supposed to trigger the removal or obseletion of hfs-utils but it only did that after the unwanted kernel package got installed.

1 Like
12

I think we are talking about the same thing here :slight_smile: andi n total agreement, but great to clarify it for occasional user that will read it.

And indeed the hfs-utils was removed a few days later.

1 Like
13

It installed itself after running the official software updater. I’ve already been booting the older working kernel so nothing is of concern.

I had a feeling some config was messed up and that this RC candidate was not supposed to be on my system. I don’t know why this kernel decided to install itself but this is essentially a brand new install. I installed netcat to diagnose a problem but that is the only package I had to install so far. I used dnf.

14

I guess on paper it can’t upgrade to an rc kernel but it did. I’m new to this distribution so maybe I did something to trigger that but I have no idea what that could be. I’ve done nothing but install netcat. I guess I was caught in that bug time period. (Updated yesterday) I’ll post the log for you guys anyway since it could help someone in the future.

15

Also on 6.15. Just went to the OM website and downloaded Rome, installed it, and didn’t think anything about it since. I’ve booted into 6.14.2 and 6.15 in playing around. Just reporting my experience for reference.

I thought 6.15 was the standard Rome release :grin:

1 Like
16

Good to hear it wasn’t user error. I thought the same, the RC was ready for primetime hence inclusion in the rome release. This could be a major problem for the newbie population that don’t know how to boot a pervious kernal in grub.

I’d be willing to bet there are many people on kernal 6.15 that booted into it fine that have no idea they are running the new kernal; considering I am on essentially a fresh installation.

1 Like
17

My bad, i copied the sucessful boot and the unsucessful boot from the log, into that post. I thought that was all that was relevant.

dmesg.txt (101.8 KB)
journal-b.txt (193.8 KB)

These timestamps are not going to help you guys, allow me to boot the busted kernel again to bring the relevent info into these files.

1 Like
18

It’s all relevant. We appreciate knowing how many are still affected by this.

1 Like
19

dmesg.txt (101.6 KB)
journal-b.txt (184.1 KB)

Here’s the same files reprinted after rebooting into the broken kernel. I timestamped 4:48 pm as the time that the caps lock started blinking.

I don’t think I understand how these logs work, as there is no timestamp of 4:48 pm. Sorry I cannot offer an interpretation. I’m an embedded developer. I patched a kernal extension once but that was just luck on my part that I could tell what I needed to change.

20

I did a little research on journalctl, journalctl -b -1 posts previous boot, seems to post relevent info to the broken kernal. The other log was for my sucessful boot. I don’t know how to get dmesg to do the same, read previous boot log that had relevant timestamp, but here is journalctl -b -1.

previous-boot.txt (98.3 KB)

Update: I just tried dmesg --since “2025-05-11 16:30:00” but there is nothing listed before 4:52 PM so I guess the log file is not long enough to store the relevent timestamp.

Update 2: according to a stackexchange, this is the dmesg output using journalctl because dmesg can’t display previous boot (from my understanding)

Output from journalctl -k -b -1:
previous-dmesg.txt (84.5 KB)