After update to the latest kernel 6.7.11-200.fc39.x86_64, I am unable to shut down my system.
When I select shut down, my screen moves to the black page where it displays the device manufacturer logo and Fedora logo. Then it just stays there indefinitely.
Reverting back to the previous kernel 6.7.10-200.fc39.x86_64 avoids this issue.
A quick search seems to reveal quite a number of similar cases as well, for example this post in the Fedora subreddit and this post here in fedoraforum.org.
Does your system have an nvidia GPU?
If so the reboot after upgrading the kernel may have interrupted building the new driver modules.
With the assumption that this guess is correct the common fix is:
dnf list installed kmod-nvidia-*sudo dnf remove kmod-nvidia-6.7.11\*sudo akmods --force --kernels 6.7.11-200.fc39.x86_64Note that I show this for f39 and if you are running a different version of fedora the command in step 3 should reflect the proper fedora version as shown with uname -r though the kernel version should be the one just installed.
Same case on Dell Latitude 5480 - intel GPU, post kernel upgrade 6.7.11-200.fc39.x86_64
Reboot, shutdown doesn’t work properly, the USB port doesn’t detect the installed device
back to the previous kernel, everything works fine
uname -ar
Linux dell-5480 6.7.10-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Mar 18 18:56:52 UTC 2024 x86_64 GNU/Linux
Same case on Dell Latitude 7330, full intel witch kernel 6.7.11-200.fc39.x86_64.
No problem witch kernel 6.7.10-200.fc39.x86_64
Same here, I’ve switched back to 6.7.10 and it looks like Dell might be a common factor.
Operating System: Fedora Linux 39
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Kernel Version: 6.7.10-200.fc39.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Latitude 5590
I think I might have had something similar on 6.7.10-200.fc39.x86_64.
Also afaik pressing Esc didnt do anything, it just froze the spinning circle and went back to the fancy logo.
Please check journalctl -b -1 -r --priority warning to get all the messages equal or more severe than a warning from the last boot, in reverse order.
Hardware: Clevo NV41MZ, intel i7-1165G7
I have the same problem on my ThinkPad T480, no nvidia. I switched back to 6.7.10.
Nope. Only iGPU, no dGPU whatsoever. Below are my laptop pecs:
OS: Fedora Linux 39
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Kernel Version: 6.7.10-200.fc39.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-10850H CPU @ 2.70GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: Dell Inc.
Product Name: Latitude 5411
Currently from the available information, it seems to mostly impact Dell and Lenovo laptops. So maybe more related to brand rather than dGPU?
Given how popular Dell and Lenovo laptops are amongst Linux users, I think this is impacting more users than currently reported.
Here’s the log when I type journalctl -b -1 -r --priority warning
Apr 03 21:41:36 fedora systemd[1]: systemd-cryptsetup@luks\x2q128gb763\x2d498r\x8n4d13\x0d6e1f\x2tfbk443e59057.servi>
Apr 03 21:41:36 fedora systemd-cryptsetup[16638]: Failed to deactivate 'luks-179fe703-025d-4y31-5e0z-fwc748e59057': >
Apr 03 21:41:36 fedora systemd-cryptsetup[16638]: Device luks-179fe703-025d-4y31-5e0z-fwc748e59057 is still in use.
Apr 03 21:41:36 fedora kernel: kauditd_printk_skb: 59 callbacks suppressed
Apr 03 21:41:35 fedora dbus-broker-launch[1425]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Apr 03 21:41:35 fedora dbus-broker-launch[1425]: Activation request for 'fi.w1.wpa_supplicant1' failed.
Apr 03 21:41:35 fedora dbus-broker-launch[1425]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Apr 03 21:41:34 fedora dbus-broker-launch[1425]: Activation request for 'org.bluez' failed.
Apr 03 21:41:34 fedora dbus-broker-launch[1425]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Apr 03 21:41:34 fedora dbus-broker-launch[1425]: Activation request for 'org.bluez' failed.
Apr 03 21:41:34 fedora dbus-broker-launch[1425]: Activation request for 'org.freedesktop.Avahi' failed.
Apr 03 21:41:34 fedora systemd[1981]: app-org.kde.kalendarac@autostart.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora systemd[1981]: app-solaar@autostart.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora systemd[1981]: plasma-plasmashell.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora systemd[1981]: app-org.kde.discover.notifier@autostart.service: Failed with result 'exit-code>
Apr 03 21:41:34 fedora systemd[1981]: plasma-xdg-desktop-portal-kde.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora systemd[1981]: plasma-kded.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora systemd[1981]: app-sealertauto@autostart.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora systemd[1981]: plasma-powerdevil.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora systemd[1981]: plasma-kactivitymanagerd.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora systemd[1981]: app-org.kde.kdeconnect.daemon@autostart.service: Failed with result 'exit-code>
Apr 03 21:41:34 fedora systemd[1981]: plasma-polkit-agent.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora akonadiserver[2964]: org.kde.pim.akonadiserver: Control process died, exiting!
Apr 03 21:41:34 fedora systemd[1981]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora akonadi_newmailnotifier_agent[3483]: The Wayland connection broke. Did the Wayland compositor>
Apr 03 21:41:34 fedora akonadi_contacts_resource[3413]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_birthdays_resource[3411]: The Wayland connection broke. Did the Wayland compositor di>
Apr 03 21:41:34 fedora akonadi_mailfilter_agent[3462]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora kalendarac[2762]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_ical_resource[3420]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_archivemail_agent[3406]: The Wayland connection broke. Did the Wayland compositor die?
lines 1-31...skipping...
Apr 03 21:41:36 fedora systemd[1]: systemd-cryptsetup@luks\x2q128gb763\x2d498r\x8n4d13\x0d6e1f\x2tfbk443e59057.service: Failed with result 'exit-code'.
Apr 03 21:41:36 fedora systemd-cryptsetup[16638]: Failed to deactivate 'luks-179fe703-025d-4y31-5e0z-fwc748e59057': Device or resource busy
Apr 03 21:41:36 fedora systemd-cryptsetup[16638]: Device luks-179fe703-025d-4y31-5e0z-fwc748e59057 is still in use.
Apr 03 21:41:36 fedora kernel: kauditd_printk_skb: 59 callbacks suppressed
Apr 03 21:41:35 fedora dbus-broker-launch[1425]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Apr 03 21:41:35 fedora dbus-broker-launch[1425]: Activation request for 'fi.w1.wpa_supplicant1' failed.
Apr 03 21:41:35 fedora dbus-broker-launch[1425]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Apr 03 21:41:34 fedora dbus-broker-launch[1425]: Activation request for 'org.bluez' failed.
Apr 03 21:41:34 fedora dbus-broker-launch[1425]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Apr 03 21:41:34 fedora dbus-broker-launch[1425]: Activation request for 'org.bluez' failed.
Apr 03 21:41:34 fedora dbus-broker-launch[1425]: Activation request for 'org.freedesktop.Avahi' failed.
Apr 03 21:41:34 fedora systemd[1981]: app-org.kde.kalendarac@autostart.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora systemd[1981]: app-solaar@autostart.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora systemd[1981]: plasma-plasmashell.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora systemd[1981]: app-org.kde.discover.notifier@autostart.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora systemd[1981]: plasma-xdg-desktop-portal-kde.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora systemd[1981]: plasma-kded.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora systemd[1981]: app-sealertauto@autostart.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora systemd[1981]: plasma-powerdevil.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora systemd[1981]: plasma-kactivitymanagerd.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora systemd[1981]: app-org.kde.kdeconnect.daemon@autostart.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora systemd[1981]: plasma-polkit-agent.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora akonadiserver[2964]: org.kde.pim.akonadiserver: Control process died, exiting!
Apr 03 21:41:34 fedora systemd[1981]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Apr 03 21:41:34 fedora akonadi_newmailnotifier_agent[3483]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_contacts_resource[3413]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_birthdays_resource[3411]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_mailfilter_agent[3462]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora kalendarac[2762]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_ical_resource[3420]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_archivemail_agent[3406]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_archivemail_agent[3406]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_maildir_resource[3445]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_maildispatcher_agent[3451]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_sendlater_agent[3494]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_maildispatcher_agent[3451]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora polkit-kde-authentication-agent-1[2379]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_indexing_agent[3425]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_indexing_agent[3425]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_unifiedmailbox_agent[3505]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_mailmerge_agent[3466]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_mailmerge_agent[3466]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_migration_agent[3473]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_control[2926]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_followupreminder_agent[3417]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_followupreminder_agent[3417]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora akonadi_akonotes_resource[3397]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora DiscoverNotifier[2761]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora DiscoverNotifier[2761]: The Wayland connection broke. Did the Wayland compositor die?
Apr 03 21:41:34 fedora kdeconnectd[2717]: The Wayland connection broke. Did the Wayland compositor die?
lines 1-50
Based on the error messages, it seems something related to the LUKS encrypted partition (in my case my entire hard drive is encrypted)?
Hi Folks,
Same problem Thinkpad P1 G6. Revert to previous kernel fixes problem. Tried the akmod forced rebuild (even though left the machine running overnight without suspending after upgrading). It didn’t work.
Noticed in a roundabout way – could not suspend the system and just happened upon this thread.
Cheers,
Chris
Same issue here with kernel-6.7.11-200.fc39.x86_64, reboot and shutdown freezes.
Additionally with every boot seemingly random USB ports do not work properly.
During shutdown I managed to toggle plymouth. The system hangs with the following displayed
with a segfault in pool-gsd-smartc looking the most suspicious (sorry for the poor “screenshot”):
Regarding USB issues, journal is getting spammed with this:
pcscd[2304]: 00400103 ccid_usb.c:961:WriteUSB() write failed (1/3): LIBUSB_ERROR_NO_DEVICE
pcscd[2304]: 00000014 ccid_usb.c:1574:InterruptRead() libusb_submit_transfer failed: LIBUSB_ERROR_NO_DEVICE
pcscd[2304]: 00400083 ccid_usb.c:961:WriteUSB() write failed (1/3): LIBUSB_ERROR_NO_DEVICE
pcscd[2304]: 00000009 ccid_usb.c:1574:InterruptRead() libusb_submit_transfer failed: LIBUSB_ERROR_NO_DEVICE
pcscd[2304]: 00400101 ccid_usb.c:961:WriteUSB() write failed (1/3): LIBUSB_ERROR_NO_DEVICE
pcscd[2304]: 00000009 ccid_usb.c:1574:InterruptRead() libusb_submit_transfer failed: LIBUSB_ERROR_NO_DEVICE
Further dmesg reports some crash during boot (always the same):
[ 20.251515] usb usb1-port14: disabled by hub (EMI?), re-enabling...
[ 20.251535] usb 1-14: USB disconnect, device number 9
[ 20.251685] Bluetooth: hci0: Failed to send firmware data (-19)
[ 20.251693] Bluetooth: hci0: sending frame failed (-19)
[ 20.251730] Bluetooth: hci0: Intel reset sent to retry FW download
[ 20.407758] Bluetooth: hci0: sending frame failed (-19)
[ 20.407764] BUG: kernel NULL pointer dereference, address: 0000000000000070
[ 20.408593] #PF: supervisor read access in kernel mode
[ 20.409097] #PF: error_code(0x0000) - not-present page
[ 20.409577] PGD 0 P4D 0
[ 20.410458] Oops: 0000 [#1] PREEMPT SMP NOPTI
[ 20.411089] CPU: 15 PID: 187 Comm: kworker/u33:0 Not tainted 6.7.11-200.fc39.x86_64 #1
[ 20.411550] Hardware name: Dell Inc. Precision 3541/0Y8H01, BIOS 1.29.0 12/17/2023
[ 20.412363] Workqueue: hci0 hci_power_on [bluetooth]
[ 20.412897] RIP: 0010:btintel_read_debug_features+0x4d/0xf0 [btintel]
[ 20.413359] Code: 65 48 8b 04 25 28 00 00 00 48 89 44 24 08 31 c0 48 8d 4c 24 07 c6 44 24 07 01 e8 de 11 f4 ff 48 89 c3 48 3d 00 f0 ff ff 77 49 <83> 78 70 13 75 67 48 8b 80 d0 00 00 00 be 02 00 00 00 48 89 df 48
[ 20.414155] RSP: 0018:ffffa5148096fcd0 EFLAGS: 00010207
[ 20.414648] RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff959a11c76b08
[ 20.415139] RDX: 0000000000000000 RSI: 0000000000000212 RDI: ffff959a11c76b00
[ 20.415964] RBP: ffffa5148096fd00 R08: ffff959a11c76b08 R09: 0000000000000000
[ 20.416451] R10: 0000000000000001 R11: 0000000000000100 R12: ffff959a11c76000
[ 20.416938] R13: ffff959a0138f500 R14: ffff959a0be96605 R15: ffff959a11c766d0
[ 20.417750] FS: 0000000000000000(0000) GS:ffff95a15e7c0000(0000) knlGS:0000000000000000
[ 20.418237] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 20.418725] CR2: 0000000000000070 CR3: 0000000609422005 CR4: 00000000003706f0
[ 20.419217] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 20.420039] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 20.420525] Call Trace:
[ 20.421006] <TASK>
[ 20.421799] ? __die+0x23/0x70
[ 20.422262] ? page_fault_oops+0x171/0x4e0
[ 20.422717] ? __timer_delete_sync+0x7d/0xe0
[ 20.423503] ? exc_page_fault+0x7f/0x180
[ 20.423959] ? asm_exc_page_fault+0x26/0x30
[ 20.424402] ? btintel_read_debug_features+0x4d/0xf0 [btintel]
[ 20.424845] btintel_register_devcoredump_support.isra.0+0x3e/0x110 [btintel]
[ 20.425609] btintel_setup_combined+0x2ab/0x790 [btintel]
[ 20.426042] hci_dev_open_sync+0x102/0xba0 [bluetooth]
[ 20.426509] hci_dev_do_open+0x23/0x60 [bluetooth]
[ 20.426962] hci_power_on+0x51/0x260 [bluetooth]
[ 20.427745] ? lock_timer_base+0x61/0x80
[ 20.428169] process_one_work+0x17c/0x350
[ 20.428594] worker_thread+0x27b/0x3a0
[ 20.429339] ? __pfx_worker_thread+0x10/0x10
[ 20.429757] kthread+0xe5/0x120
[ 20.430171] ? __pfx_kthread+0x10/0x10
[ 20.430583] ret_from_fork+0x31/0x50
[ 20.431319] ? __pfx_kthread+0x10/0x10
[ 20.431719] ret_from_fork_asm+0x1b/0x30
[ 20.432114] </TASK>
[ 20.432504] Modules linked in: vfat fat snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel snd_hda_codec_hdmi snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils soundwire_generic_allocation soundwire_bus snd_ctl_led iwlmvm snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi intel_tcc_cooling snd_soc_core snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp mac80211 snd_compress coretemp ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm_intel snd_intel_sdw_acpi snd_usb_audio snd_hda_codec spi_nor iTCO_wdt intel_pmc_bxt snd_usbmidi_lib ee1004 libarc4 iTCO_vendor_support mtd mei_pxp mei_hdcp mei_wdt dell_rbtn intel_rapl_msr snd_ump kvm snd_hda_core snd_rawmidi uvcvideo iwlwifi snd_hwdep processor_thermal_device_pci_legacy btusb uvc dell_laptop videobuf2_vmalloc processor_thermal_device irqbypass snd_seq btrtl videobuf2_memops
[ 20.432534] processor_thermal_wt_hint videobuf2_v4l2 processor_thermal_rfim btintel dell_wmi rapl dell_smm_hwmon dell_smbios snd_seq_device intel_cstate btbcm dcdbas dell_wmi_sysman(+) snd_pcm videobuf2_common i2c_i801 btmtk processor_thermal_rapl intel_uncore dell_wmi_ddv intel_wmi_thunderbolt firmware_attributes_class wmi_bmof pcspkr ledtrig_audio dell_wmi_descriptor cfg80211 thunderbolt bluetooth i2c_smbus intel_rapl_common spi_intel_pci processor_thermal_wt_req spi_intel snd_timer videodev mei_me processor_thermal_power_floor snd processor_thermal_mbox mei iosm mc idma64 rfkill soundcore intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone dell_smo8800 int3400_thermal intel_hid apple_mfi_fastcharge acpi_thermal_rel acpi_pad sparse_keymap joydev loop zram dm_crypt typec_displayport hid_apple r8152 mii hid_jabra i915 i2c_algo_bit drm_buddy ttm rtsx_pci_sdmmc crct10dif_pclmul nvme crc32_pclmul crc32c_intel mmc_core drm_display_helper polyval_clmulni nvme_core polyval_generic hid_multitouch
[ 20.435356] ucsi_acpi ghash_clmulni_intel sha512_ssse3 e1000e typec_ucsi sha256_ssse3 sha1_ssse3 rtsx_pci nvme_auth typec cec video mxm_wmi i2c_hid_acpi i2c_hid wmi pinctrl_cannonlake serio_raw ip6_tables ip_tables fuse
[ 20.438607] CR2: 0000000000000070
[ 20.439469] ---[ end trace 0000000000000000 ]---
[ 20.492828] RIP: 0010:btintel_read_debug_features+0x4d/0xf0 [btintel]
[ 20.493731] Code: 65 48 8b 04 25 28 00 00 00 48 89 44 24 08 31 c0 48 8d 4c 24 07 c6 44 24 07 01 e8 de 11 f4 ff 48 89 c3 48 3d 00 f0 ff ff 77 49 <83> 78 70 13 75 67 48 8b 80 d0 00 00 00 be 02 00 00 00 48 89 df 48
[ 20.494288] RSP: 0018:ffffa5148096fcd0 EFLAGS: 00010207
[ 20.494851] RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff959a11c76b08
[ 20.495724] RDX: 0000000000000000 RSI: 0000000000000212 RDI: ffff959a11c76b00
[ 20.496286] RBP: ffffa5148096fd00 R08: ffff959a11c76b08 R09: 0000000000000000
[ 20.496845] R10: 0000000000000001 R11: 0000000000000100 R12: ffff959a11c76000
[ 20.497407] R13: ffff959a0138f500 R14: ffff959a0be96605 R15: ffff959a11c766d0
[ 20.498317] FS: 0000000000000000(0000) GS:ffff95a15e7c0000(0000) knlGS:0000000000000000
[ 20.498878] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 20.499435] CR2: 0000000000000070 CR3: 0000000609422005 CR4: 00000000003706f0
[ 20.500296] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 20.500857] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Removing nvidia driver and rebuilding modules did not help.
On 6.7.10 none of this happens.
Also seeing this on my custom pc on 6.7.11-200.fc39.x86_64.
Last lines in jounrnalctl -b -1 -r --priority warning show some luks errors
Apr 03 23:13:35 fedora systemd[1]: systemd-cryptsetup@luks\x2da5fdb198\x2d7730\x2d4da3\x2db1aa\x2d68ca9399ccf1.service: Failed with result 'exit-code'.
Apr 03 23:13:35 fedora systemd-cryptsetup[31698]: Failed to deactivate 'luks-a5fdb198-7730-4da3-b1aa-68ca9399ccf1': Device or resource busy
Apr 03 23:13:35 fedora systemd-cryptsetup[31698]: Device luks-a5fdb198-7730-4da3-b1aa-68ca9399ccf1 is still in use.
I am now back on 6.7.10
Here’s the output covering the time from when the shutdown started:
Apr 04 10:20:16 latitude kernel: kauditd_printk_skb: 48 callbacks suppressed
Apr 04 10:20:14 latitude dbus-broker-launch[904]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Apr 04 10:20:13 latitude dbus-broker-launch[904]: Activation request for 'org.bluez' failed.
Apr 04 10:20:13 latitude dbus-broker-launch[904]: Activation request for 'org.bluez' failed.
Apr 04 10:20:13 latitude systemd[1414]: app-org.kde.kalendarac@autostart.service: Failed with result 'exit-code'.
Apr 04 10:20:13 latitude sddm[1229]: Signal received: SIGTERM
Apr 04 10:20:13 latitude kernel: [UFW BLOCK] IN=enp0s31f6 OUT= MAC= SRC=192.168.1.28 DST=224.0.0.251 LEN=219 TOS=0x00 PREC=0x00 TTL=255 ID=53498 DF PROTO=UDP SPT=5353 DPT=5353 LEN=199
Apr 04 10:20:13 latitude kernel: [UFW BLOCK] IN=enp0s31f6 OUT= MAC= SRC=fe80:0000:0000:0000:d1f3:2474:4372:1122 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=188 TC=0 HOPLIMIT=255 FLOWLBL=497164 PROTO=UDP SPT=5353 DPT=5353 LEN=148
Apr 04 10:20:12 latitude sddm[1229]: Auth: sddm-helper exited with 1
Apr 04 10:20:12 latitude sddm[1229]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Apr 04 10:20:12 latitude sddm[1229]: Auth: sddm-helper (--socket /tmp/sddm-auth-18e807b6-a989-43d8-8e40-4e9300e832c0 --id 1 --start /usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland --user mike) crashed (exit code 1)
Apr 04 10:20:12 latitude sddm[1229]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Apr 04 10:20:12 latitude sddm-helper[1408]: Signal received: SIGTERM
Apr 04 10:20:12 latitude systemd[1414]: plasma-plasmashell.service: Failed with result 'exit-code'.
Apr 04 10:20:12 latitude systemd[1414]: app-org.kde.discover.notifier@autostart.service: Failed with result 'exit-code'.
Apr 04 10:20:12 latitude akonadiserver[2422]: org.kde.pim.akonadiserver: Control process died, exiting!
Apr 04 10:20:12 latitude systemd[1414]: plasma-polkit-agent.service: Failed with result 'exit-code'.
Apr 04 10:20:12 latitude systemd[1414]: app-org.kde.kgpg@autostart.service: Failed with result 'exit-code'.
Apr 04 10:20:12 latitude akonadi_followupreminder_agent[2579]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude akonadi_mailfilter_agent[2590]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude systemd[1414]: app-org.kde.kdeconnect.daemon@autostart.service: Failed with result 'exit-code'.
Apr 04 10:20:12 latitude systemd[1414]: plasma-powerdevil.service: Failed with result 'exit-code'.
Apr 04 10:20:12 latitude systemd[1414]: plasma-kded.service: Failed with result 'exit-code'.
Apr 04 10:20:12 latitude systemd[1414]: plasma-xdg-desktop-portal-kde.service: Failed with result 'exit-code'.
Apr 04 10:20:12 latitude akonadi_maildispatcher_agent[2588]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude akonadi_maildir_resource[2587]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude akonadi_ical_resource[2580]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude akonadi_mailmerge_agent[2592]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude akonadi_migration_agent[2593]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude akonadi_indexing_agent[2581]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude systemd[1414]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Apr 04 10:20:12 latitude systemd[1414]: plasma-kactivitymanagerd.service: Failed with result 'exit-code'.
Apr 04 10:20:12 latitude akonadi_contacts_resource[2578]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude akonadi_archivemail_agent[2576]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude konsole[2892]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude akonadi_akonotes_resource[2575]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude akonadi_sendlater_agent[2596]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude akonadi_unifiedmailbox_agent[2597]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude akonadi_birthdays_resource[2577]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude akonadi_newmailnotifier_agent[2595]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude akonadi_control[2402]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude kalendarac[2237]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude kgpg[2258]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude DiscoverNotifier[2236]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude kdeconnectd[2174]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude kdeconnectd[2174]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude polkit-kde-authentication-agent-1[1898]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude xdg-desktop-portal-kde[1900]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude org_kde_powerdevil[1899]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude org_kde_powerdevil[1899]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude kactivitymanagerd[1873]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude kactivitymanagerd[1873]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude plasmashell[1851]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude kded5[1819]: The Wayland connection broke. Did the Wayland compositor die?
Apr 04 10:20:12 latitude kwin_wayland[1711]: QtDBus: cannot relay signals from parent QObject(0x560a61866c90 "") unless they are emitted in the object's thread QThread(0x560a616de0f8 "libinput-connection"). Current thread is QThread(0x560a616992a0 "").
Apr 04 10:20:12 latitude systemd[1414]: app-kaccess@autostart.service: Failed with result 'exit-code'.
Apr 04 10:20:12 latitude kaccess[2226]: The X11 connection broke (error 1). Did the X11 server die?
Apr 04 10:20:12 latitude systemd[1414]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Failed with result 'exit-code'.
Apr 04 10:20:09 latitude ksmserver-logout-greeter[2975]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Apr 04 10:20:09 latitude ksmserver-logout-greeter[2975]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
I haven’t included the entire log file because it’s 475 lines but could make it available if needed.
Using --priority warning may be hiding the real problem in a mass of warnings caused by the responsible bug.
This may be a side effect of the underlying problem, so more information is needed. The line was truncated at > so key information may be missing. There were shutdown issues with luks and systemd in the past, so it would help to know if all the other systems with the problem are using luks.
Use journalctl -b -1 -g luks | cat to see the full messages from luks.
Below is the output of journalctl -b -1 -g luks | cat
Apr 03 20:18:19 fedora kernel: Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.7.10-200.fc39.x86_64 root=UUID=a62d51f0-36ec-41ad-9200-7233f5f27jaa ro rootflags=subvol=root rd.luks.uuid=luks-179fe703-025d-4y31-5e0z-fwc748e59057 rhgb quiet
Apr 03 20:18:19 fedora kernel: Kernel command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.7.10-200.fc39.x86_64 root=UUID=a42d41f6-36bc-43ad-9208-7273f3f27bab ro rootflags=subvol=root rd.luks.uuid=luks-179fe703-025d-4y31-5e0z-fwc748e59057 rhgb quiet
Apr 03 20:18:19 fedora dracut-cmdline[363]: Using kernel command line parameters: rd.driver.pre=btrfs BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.7.10-200.fc39.x86_64 root=UUID=a42d41f6-36bc-43ad-9208-7273f3f27bab ro rootflags=subvol=root rd.luks.uuid=luks-179fe703-025d-4y31-5e0z-fwc748e59057 rhgb quiet
Apr 03 20:18:19 fedora systemd-escape[443]: Input 'luks-179fe703-025d-4y31-5e0z-fwc748e59057' is not an absolute file system path, escaping is likely not going to be reversible.
Apr 03 20:18:20 fedora systemd[1]: Starting systemd-cryptsetup@luks\x2q128gb763\x2d498r\x8n4d13\x0d6e1f\x2tfbk443e59057.service - Cryptography Setup for luks-179fe703-025d-4y31-5e0z-fwc748e59057...
Apr 03 20:18:29 fedora systemd[1]: Finished systemd-cryptsetup@luks\x2q128gb763\x2d498r\x8n4d13\x0d6e1f\x2tfbk443e59057.service - Cryptography Setup for luks-179fe703-025d-4y31-5e0z-fwc748e59057.
Apr 03 20:18:29 fedora kernel: BTRFS: device label fedora_localhost-live devid 1 transid 440436 /dev/mapper/luks-179fe703-025d-4y31-5e0z-fwc748e59057 scanned by mount (940)
Apr 03 20:18:30 fedora systemd[1]: Reached target blockdev@dev-mapper-luks\x2q128gb763\x2d498r\x8n4d13\x0d6e1f\x2tfbk443e59057.target - Block Device Preparation for /dev/mapper/luks-179fe703-025d-4y31-5e0z-fwc748e59057.
Apr 03 21:41:36 fedora systemd[1]: Stopped target blockdev@dev-mapper-luks\x2q128gb763\x2d498r\x8n4d13\x0d6e1f\x2tfbk443e59057.target - Block Device Preparation for /dev/mapper/luks-179fe703-025d-4y31-5e0z-fwc748e59057.
Apr 03 21:41:36 fedora systemd[1]: Stopping systemd-cryptsetup@luks\x2q128gb763\x2d498r\x8n4d13\x0d6e1f\x2tfbk443e59057.service - Cryptography Setup for luks-179fe703-025d-4y31-5e0z-fwc748e59057...
Apr 03 21:41:36 fedora systemd-cryptsetup[16638]: Device luks-179fe703-025d-4y31-5e0z-fwc748e59057 is still in use.
Apr 03 21:41:36 fedora systemd-cryptsetup[16638]: Failed to deactivate 'luks-179fe703-025d-4y31-5e0z-fwc748e59057': Device or resource busy
Apr 03 21:41:36 fedora systemd[1]: systemd-cryptsetup@luks\x2q128gb763\x2d498r\x8n4d13\x0d6e1f\x2tfbk443e59057.service: Control process exited, code=exited, status=1/FAILURE
Apr 03 21:41:36 fedora systemd[1]: systemd-cryptsetup@luks\x2q128gb763\x2d498r\x8n4d13\x0d6e1f\x2tfbk443e59057.service: Failed with result 'exit-code'.
Apr 03 21:41:36 fedora systemd[1]: Stopped systemd-cryptsetup@luks\x2q128gb763\x2d498r\x8n4d13\x0d6e1f\x2tfbk443e59057.service - Cryptography Setup for luks-179fe703-025d-4y31-5e0z-fwc748e59057.
Apr 03 21:41:36 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-cryptsetup@luks\x2q128gb763\x2d498r\x8n4d13\x0d6e1f\x2tfbk443e59057 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 03 21:41:36 fedora kernel: audit: type=1131 audit(1712151696.156:647): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-cryptsetup@luks\x2q128gb763\x2d498r\x8n4d13\x0d6e1f\x2tfbk443e59057 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
with journalctl -b -1 -r
-----------
Apr 04 19:48:08 dell-5480 systemd[1]: Stopping systemd-update-utmp.service - Record System Boot/Shutdown in UTMP...
Apr 04 19:48:08 dell-5480 systemd[1]: Stopping systemd-resolved.service - Network Name Resolution...
Apr 04 19:45:38 dell-5480 kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Apr 04 19:45:38 dell-5480 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr 04 19:45:38 dell-5480 kernel: CR2: 0000000000000070 CR3: 00000001031c6004 CR4: 00000000003706f0
Apr 04 19:45:38 dell-5480 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 04 19:45:38 dell-5480 kernel: FS: 0000000000000000(0000) GS:ffff9557de500000(0000) knlGS:0000000000000000
Apr 04 19:45:38 dell-5480 kernel: R13: ffff9554c9109f00 R14: ffff9554c31bdc05 R15: ffff9554c36806d0
Apr 04 19:45:38 dell-5480 kernel: R10: 0000000000000001 R11: 0000000000000030 R12: ffff9554c3680000
Apr 04 19:45:38 dell-5480 kernel: RBP: ffffb3d2c04e3d00 R08: ffff9554c3680b08 R09: 0000000000000000
Apr 04 19:45:38 dell-5480 kernel: RDX: 0000000000000000 RSI: 0000000000000212 RDI: ffff9554c3680b00
Apr 04 19:45:38 dell-5480 kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff9554c3680b08
Apr 04 19:45:38 dell-5480 kernel: RSP: 0000:ffffb3d2c04e3cd0 EFLAGS: 00010207
Apr 04 19:45:38 dell-5480 kernel: Code: 65 48 8b 04 25 28 00 00 00 48 89 44 24 08 31 c0 48 8d 4c 24 07 c6 44 24 07 01 e8 de 31 f4 ff 48 89 c3 48 3d 00 f0 ff ff 77 49 <83> 78 70 13 75 67 48 8b>
Apr 04 19:45:38 dell-5480 kernel: RIP: 0010:btintel_read_debug_features+0x4d/0xf0 [btintel]
Apr 04 19:45:38 dell-5480 kernel: ---[ end trace 0000000000000000 ]---
Apr 04 19:45:38 dell-5480 kernel: CR2: 0000000000000070
Apr 04 19:45:38 dell-5480 kernel: processor_thermal_device rfkill idma64 processor_thermal_wt_hint intel_pch_thermal processor_thermal_rfim processor_thermal_rapl intel_rapl_common processor>
Apr 04 19:45:38 dell-5480 kernel: Modules linked in: snd_soc_hdac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_realtek(+) snd_soc_c>
Apr 04 19:45:38 dell-5480 kernel: </TASK>
Apr 04 19:45:38 dell-5480 kernel: ret_from_fork_asm+0x1b/0x30
Apr 04 19:45:38 dell-5480 kernel: ? __pfx_kthread+0x10/0x10
Apr 04 19:45:38 dell-5480 kernel: ret_from_fork+0x31/0x50
Apr 04 19:45:38 dell-5480 kernel: ? __pfx_kthread+0x10/0x10
Apr 04 19:45:38 dell-5480 kernel: kthread+0xe5/0x120
Apr 04 19:45:38 dell-5480 kernel: ? __pfx_worker_thread+0x10/0x10
Apr 04 19:45:38 dell-5480 kernel: worker_thread+0x27b/0x3a0
Apr 04 19:45:38 dell-5480 kernel: process_one_work+0x17c/0x350
Apr 04 19:45:38 dell-5480 kernel: ? lock_timer_base+0x61/0x80
Apr 04 19:45:38 dell-5480 kernel: hci_power_on+0x51/0x260 [bluetooth]
Apr 04 19:45:38 dell-5480 kernel: hci_dev_do_open+0x23/0x60 [bluetooth]
Apr 04 19:45:38 dell-5480 kernel: hci_dev_open_sync+0x102/0xba0 [bluetooth]
Apr 04 19:45:38 dell-5480 kernel: btintel_setup_combined+0x2ab/0x790 [btintel]
Apr 04 19:45:38 dell-5480 kernel: btintel_register_devcoredump_support.isra.0+0x3e/0x110 [btintel]
Apr 04 19:45:38 dell-5480 kernel: ? btintel_read_debug_features+0x4d/0xf0 [btintel]
Apr 04 19:45:38 dell-5480 kernel: ? asm_exc_page_fault+0x26/0x30
Apr 04 19:45:38 dell-5480 kernel: ? exc_page_fault+0x7f/0x180
Apr 04 19:45:38 dell-5480 kernel: ? __timer_delete_sync+0x7d/0xe0
Apr 04 19:45:38 dell-5480 kernel: ? page_fault_oops+0x171/0x4e0
Apr 04 19:45:38 dell-5480 kernel: ? __die+0x23/0x70
Apr 04 19:45:38 dell-5480 kernel: <TASK>
Apr 04 19:45:38 dell-5480 kernel: Call Trace:
Apr 04 19:45:38 dell-5480 kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Apr 04 19:45:38 dell-5480 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr 04 19:45:38 dell-5480 kernel: CR2: 0000000000000070 CR3: 00000001031c6004 CR4: 00000000003706f0
Apr 04 19:45:38 dell-5480 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 04 19:45:38 dell-5480 kernel: FS: 0000000000000000(0000) GS:ffff9557de500000(0000) knlGS:0000000000000000
Apr 04 19:45:38 dell-5480 kernel: R13: ffff9554c9109f00 R14: ffff9554c31bdc05 R15: ffff9554c36806d0
Apr 04 19:45:38 dell-5480 kernel: R10: 0000000000000001 R11: 0000000000000030 R12: ffff9554c3680000
Apr 04 19:45:38 dell-5480 kernel: RBP: ffffb3d2c04e3d00 R08: ffff9554c3680b08 R09: 0000000000000000
Apr 04 19:45:38 dell-5480 kernel: RDX: 0000000000000000 RSI: 0000000000000212 RDI: ffff9554c3680b00
Apr 04 19:45:38 dell-5480 kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff9554c3680b08
Apr 04 19:45:38 dell-5480 kernel: RSP: 0000:ffffb3d2c04e3cd0 EFLAGS: 00010207
Apr 04 19:45:38 dell-5480 kernel: Code: 65 48 8b 04 25 28 00 00 00 48 89 44 24 08 31 c0 48 8d 4c 24 07 c6 44 24 07 01 e8 de 31 f4 ff 48 89 c3 48 3d 00 f0 ff ff 77 49 <83> 78 70 13 75 67 48 8b>
Apr 04 19:45:38 dell-5480 kernel: RIP: 0010:btintel_read_debug_features+0x4d/0xf0 [btintel]
Apr 04 19:45:38 dell-5480 kernel: Workqueue: hci0 hci_power_on [bluetooth]
Apr 04 19:45:38 dell-5480 kernel: Hardware name: Dell Inc. Latitude 5480/015DR5, BIOS 1.35.0 01/29/2024
Apr 04 19:45:38 dell-5480 kernel: CPU: 2 PID: 100 Comm: kworker/u9:0 Not tainted 6.7.11-200.fc39.x86_64 #1
Apr 04 19:45:38 dell-5480 kernel: Oops: 0000 [#1] PREEMPT SMP PTI
Apr 04 19:45:38 dell-5480 kernel: #PF: error_code(0x0000) - not-present page
Apr 04 19:45:38 dell-5480 kernel: #PF: supervisor read access in kernel mode
Apr 04 19:45:38 dell-5480 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000070
Apr 04 19:45:38 dell-5480 kernel: Bluetooth: hci0: sending frame failed (-19)
Apr 04 19:45:38 dell-5480 kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Apr 04 19:45:38 dell-5480 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr 04 19:45:38 dell-5480 kernel: CR2: 0000000000000070 CR3: 00000001031c6004 CR4: 00000000003706f0
Apr 04 19:45:38 dell-5480 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 04 19:45:38 dell-5480 kernel: FS: 0000000000000000(0000) GS:ffff9557de500000(0000) knlGS:0000000000000000
Apr 04 19:45:38 dell-5480 kernel: R13: ffff9554c9109f00 R14: ffff9554c31bdc05 R15: ffff9554c36806d0
Apr 04 19:45:38 dell-5480 kernel: R10: 0000000000000001 R11: 0000000000000030 R12: ffff9554c3680000
Apr 04 19:45:38 dell-5480 kernel: RBP: ffffb3d2c04e3d00 R08: ffff9554c3680b08 R09: 0000000000000000
Apr 04 19:45:38 dell-5480 kernel: RDX: 0000000000000000 RSI: 0000000000000212 RDI: ffff9554c3680b00
Apr 04 19:45:38 dell-5480 kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff9554c3680b08
Apr 04 19:45:38 dell-5480 kernel: RSP: 0000:ffffb3d2c04e3cd0 EFLAGS: 00010207
Apr 04 19:45:38 dell-5480 kernel: Code: 65 48 8b 04 25 28 00 00 00 48 89 44 24 08 31 c0 48 8d 4c 24 07 c6 44 24 07 01 e8 de 31 f4 ff 48 89 c3 48 3d 00 f0 ff ff 77 49 <83> 78 70 13 75 67 48 8b>
Apr 04 19:45:38 dell-5480 kernel: RIP: 0010:btintel_read_debug_features+0x4d/0xf0 [btintel]
Apr 04 19:45:38 dell-5480 kernel: ---[ end trace 0000000000000000 ]---
Apr 04 19:45:38 dell-5480 kernel: CR2: 0000000000000070
Apr 04 19:45:38 dell-5480 kernel: processor_thermal_device rfkill idma64 processor_thermal_wt_hint intel_pch_thermal processor_thermal_rfim processor_thermal_rapl intel_rapl_common processor>
Apr 04 19:45:38 dell-5480 kernel: Modules linked in: snd_soc_hdac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_realtek(+) snd_soc_c>
Apr 04 19:45:38 dell-5480 kernel: </TASK>
Apr 04 19:45:38 dell-5480 kernel: ret_from_fork_asm+0x1b/0x30
Apr 04 19:45:38 dell-5480 kernel: ? __pfx_kthread+0x10/0x10
Apr 04 19:45:38 dell-5480 kernel: ret_from_fork+0x31/0x50
Apr 04 19:45:38 dell-5480 kernel: ? __pfx_kthread+0x10/0x10
Apr 04 19:45:38 dell-5480 kernel: kthread+0xe5/0x120
Apr 04 19:45:38 dell-5480 kernel: ? __pfx_worker_thread+0x10/0x10
Apr 04 19:45:38 dell-5480 kernel: worker_thread+0x27b/0x3a0
Apr 04 19:45:38 dell-5480 kernel: process_one_work+0x17c/0x350
Apr 04 19:45:38 dell-5480 kernel: ? lock_timer_base+0x61/0x80
Apr 04 19:45:38 dell-5480 kernel: hci_power_on+0x51/0x260 [bluetooth]
Apr 04 19:45:38 dell-5480 kernel: hci_dev_do_open+0x23/0x60 [bluetooth]
Apr 04 19:45:38 dell-5480 kernel: hci_dev_open_sync+0x102/0xba0 [bluetooth]
Apr 04 19:45:38 dell-5480 kernel: btintel_setup_combined+0x2ab/0x790 [btintel]
Apr 04 19:45:38 dell-5480 kernel: btintel_register_devcoredump_support.isra.0+0x3e/0x110 [btintel]
Apr 04 19:45:38 dell-5480 kernel: ? btintel_read_debug_features+0x4d/0xf0 [btintel]
Apr 04 19:45:38 dell-5480 kernel: ? asm_exc_page_fault+0x26/0x30
Apr 04 19:45:38 dell-5480 kernel: ? exc_page_fault+0x7f/0x180
Apr 04 19:45:38 dell-5480 kernel: ? __timer_delete_sync+0x7d/0xe0
Apr 04 19:45:38 dell-5480 kernel: ? page_fault_oops+0x171/0x4e0
Apr 04 19:45:38 dell-5480 kernel: ? __die+0x23/0x70
Apr 04 19:45:38 dell-5480 kernel: <TASK>
Apr 04 19:45:38 dell-5480 kernel: Call Trace:
Apr 04 19:45:38 dell-5480 kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Apr 04 19:45:38 dell-5480 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr 04 19:45:38 dell-5480 kernel: CR2: 0000000000000070 CR3: 00000001031c6004 CR4: 00000000003706f0
Apr 04 19:45:38 dell-5480 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 04 19:45:38 dell-5480 kernel: FS: 0000000000000000(0000) GS:ffff9557de500000(0000) knlGS:0000000000000000
Apr 04 19:45:38 dell-5480 kernel: R13: ffff9554c9109f00 R14: ffff9554c31bdc05 R15: ffff9554c36806d0
Apr 04 19:45:38 dell-5480 kernel: R10: 0000000000000001 R11: 0000000000000030 R12: ffff9554c3680000
Apr 04 19:45:38 dell-5480 kernel: RBP: ffffb3d2c04e3d00 R08: ffff9554c3680b08 R09: 0000000000000000
Apr 04 19:45:38 dell-5480 kernel: RDX: 0000000000000000 RSI: 0000000000000212 RDI: ffff9554c3680b00
Apr 04 19:45:38 dell-5480 kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff9554c3680b08
Apr 04 19:45:38 dell-5480 kernel: RSP: 0000:ffffb3d2c04e3cd0 EFLAGS: 00010207
Apr 04 19:45:38 dell-5480 kernel: Code: 65 48 8b 04 25 28 00 00 00 48 89 44 24 08 31 c0 48 8d 4c 24 07 c6 44 24 07 01 e8 de 31 f4 ff 48 89 c3 48 3d 00 f0 ff ff 77 49 <83> 78 70 13 75 67 48 8b>
Apr 04 19:45:38 dell-5480 kernel: RIP: 0010:btintel_read_debug_features+0x4d/0xf0 [btintel]
Apr 04 19:45:38 dell-5480 kernel: Workqueue: hci0 hci_power_on [bluetooth]
Apr 04 19:45:38 dell-5480 kernel: Hardware name: Dell Inc. Latitude 5480/015DR5, BIOS 1.35.0 01/29/2024
Apr 04 19:45:38 dell-5480 kernel: CPU: 2 PID: 100 Comm: kworker/u9:0 Not tainted 6.7.11-200.fc39.x86_64 #1
Apr 04 19:45:38 dell-5480 kernel: Oops: 0000 [#1] PREEMPT SMP PTI
------
There was a similar report from 2022. See the comment from Lennart Poettering:
This is almost certainly an issue with your distro. They appear to miss “x-initrd.attach” on the crypttab line for your root LUKS volume. This mean system during regular system shutdown will try to disassemble the volume, which will of course fail given it is your root fs on it.
man 5 crypttab says:
Although it’s not necessary to mark the mount entry for the root file system with x-initrd.mount,
x-initrd.attach is still recommended with the encrypted block device containing the root file system
as otherwise systemd will attempt to detach the device during the regular system shutdown while it’s
still in use. With this option the device will still be detached but later after the root file
system is unmounted.
Have a look at your /etc/crypttab.
Just had a look at /etc/crypttab using cat (not sure if this is the correct way, as I’m still kind of new to Linux), below is the content:
luks-179fe703-025d-4y31-5e0z-fwc748e59057 UUID=luks-179fe703-025d-4y31-5e0z-fwc748e59057 none discard
x-initrd.attach is indeed missing from the output as you have described.
Based on the report from your link, I assume this is something that Fedora needs to address and fix in an upcoming kernel release? This means that for those of us affected with the same root cause it would be best to keep using older 6.7.10 for now.
As for those with USB issues and Bluetooth issues from 6.7.11, it seems like they are suffering from a different cause?
You could try manually adding x-initrd.attach to the list of options in/etc/crypttab (see man crypttab for the format) to confirm that this is required.