Hello,
I am not able to boot any of the 6.14 kernels. You can see the error messages in the attached image. I have never had that issue with previous kernels.
As a result, the boot process gets stuck and it does not go beyond the job dev-disk-by stage.
Any help is greatly appreciated.
Do you still have a 6.13 kernel installed so that you can at least use your system?
Yes, I do. I am currently using 6.13.10.
I have no immediate solutions, but this could be a kernel module error that would have to be fixed upstream.
Perhaps you want to list your hardware as well for information. You can install and use the command inxi for that to print an overview:
$ inxi -Fzxx
If you want to get a boot log more easily you can use the journalctl command with the -b parameter to show a previous boot, and -p for a specific error severity.
For example
# show log of previous boot
$ journalctl -b -1
# show log of 2 boots back
$ journalctl -b -2
# show log of previous boot and show only errors of the level [error] and [critical]
$ journalctl -b -1 -p 2 -p 3
The log levels are as follows:
"emerg" (0)
"alert" (1)
"crit" (2)
"err" (3)
"warning" (4)
"notice" (5)
"info" (6)
"debug" (7)
You may be able to find specific errors more easily in that case, which could help to track kernel bug reports upstream.
Yes, it does seem like a tricky one. I have a hard time uploading all the output since the discussion board limits messages to a certain length.
Let’s start with inxi:
System:
Kernel: 6.13.10-200.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 14.2.1
Desktop: GNOME v: 48.1 tk: GTK v: 3.24.49 wm: gnome-shell dm: GDM
Distro: Fedora Linux 42 (Workstation Edition)
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: Pro WS WRX80E-SAGE SE WIFI v: Rev 1.xx
serial: <superuser required> part-nu: SKU UEFI: American Megatrends v: 1003
date: 02/18/2022
CPU:
Info: 24-core model: AMD Ryzen Threadripper PRO 5965WX s bits: 64
type: MT MCP arch: Zen 3 rev: 2 cache: L1: 1.5 MiB L2: 12 MiB L3: 128 MiB
Speed (MHz): avg: 1429 min/max: 400/4569 boost: enabled cores: 1: 1429
2: 1429 3: 1429 4: 1429 5: 1429 6: 1429 7: 1429 8: 1429 9: 1429 10: 1429
11: 1429 12: 1429 13: 1429 14: 1429 15: 1429 16: 1429 17: 1429 18: 1429
19: 1429 20: 1429 21: 1429 22: 1429 23: 1429 24: 1429 25: 1429 26: 1429
27: 1429 28: 1429 29: 1429 30: 1429 31: 1429 32: 1429 33: 1429 34: 1429
35: 1429 36: 1429 37: 1429 38: 1429 39: 1429 40: 1429 41: 1429 42: 1429
43: 1429 44: 1429 45: 1429 46: 1429 47: 1429 48: 1429 bogomips: 364130
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: ASPEED Graphics Family driver: ast v: kernel ports: active: none
off: VGA-1 empty: none bus-ID: 2a:00.0 chip-ID: 1a03:2000
Device-2: NVIDIA GA102 [GeForce RTX 3080 Ti] vendor: Palit Microsystems
driver: nvidia v: 570.144 arch: Ampere pcie: speed: 2.5 GT/s lanes: 16
ports: active: none off: DP-1 empty: DP-2,DP-3,HDMI-A-1 bus-ID: 41:00.0
chip-ID: 10de:2208
Display: wayland server: X.Org v: 24.1.6 with: Xwayland v: 24.1.6
compositor: gnome-shell driver: X: loaded: modesetting,nouveau
failed: nvidia alternate: fbdev,nv,vesa gpu: ast,nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 3440x1440 s-dpi: 96
Monitor-1: DP-1 res: 3440x1440 hz: 144 dpi: 109 diag: 865mm (34.07")
API: OpenGL v: 4.6.0 vendor: nvidia v: 570.144 glx-v: 1.4
direct-render: yes renderer: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2
API: Vulkan v: 1.4.309 surfaces: xcb,xlib,wayland device: 0
type: discrete-gpu driver: N/A device-ID: 10de:2208 device: 1 type: cpu
driver: N/A device-ID: 10005:0000
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Info: Tools: api: glxinfo,vulkaninfo gpu: nvidia-settings x11: xdriinfo,
xdpyinfo, xprop, xrandr
Audio:
Device-1: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
vendor: ASUSTeK driver: N/A pcie: speed: 16 GT/s lanes: 16 bus-ID: 2d:00.4
chip-ID: 1022:1487
Device-2: NVIDIA GA102 High Definition Audio vendor: Palit Microsystems
driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
bus-ID: 41:00.1 chip-ID: 10de:1aef
Device-3: ASUSTek USB Audio driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 5-6:3 chip-ID: 0b05:1984
Device-4: Focusrite-Novation Focusrite Scarlett 2i2 driver: snd-usb-audio
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 9-2:2 chip-ID: 1235:8006
API: ALSA v: k6.13.10-200.fc41.x86_64 status: kernel-api
Server-1: PipeWire v: 1.4.2 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
Network:
Device-1: Intel Ethernet X550 vendor: ASUSTeK driver: ixgbe v: kernel pcie:
speed: 8 GT/s lanes: 4 port: N/A bus-ID: 25:00.0 chip-ID: 8086:1563
IF: enp37s0f0 state: down mac: <filter>
Device-2: Intel Ethernet X550 vendor: ASUSTeK driver: ixgbe v: kernel
pcie: speed: 8 GT/s lanes: 4 port: N/A bus-ID: 25:00.1 chip-ID: 8086:1563
IF: enp37s0f1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-3: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie:
speed: 5 GT/s lanes: 1 bus-ID: 26:00.0 chip-ID: 8086:2723
IF: wlp38s0 state: down mac: <filter>
IF-ID-1: br-056b60255bb8 state: down mac: <filter>
IF-ID-2: br-c17dea47ac65 state: down mac: <filter>
IF-ID-3: docker0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 bus-ID: 3-6:3 chip-ID: 8087:0029
Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: disabled
rfk-block: hardware: no software: yes address: N/A
Drives:
Local Storage: total: 1.82 TiB used: 696.93 GiB (37.4%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 2TB
size: 1.82 TiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 39.9 C
Partition:
ID-1: / size: 1.82 TiB used: 696.57 GiB (37.4%) fs: btrfs
dev: /dev/nvme0n1p3
ID-2: /boot size: 973.4 MiB used: 350.8 MiB (36.0%) fs: ext4
dev: /dev/nvme0n1p2
ID-3: /boot/efi size: 598.8 MiB used: 19.3 MiB (3.2%) fs: vfat
dev: /dev/nvme0n1p1
ID-4: /home size: 1.82 TiB used: 696.57 GiB (37.4%) fs: btrfs
dev: /dev/nvme0n1p3
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
Src: ipmi Permissions: Unable to run ipmi sensors. Root privileges required.
Src: lm-sensors System Temperatures: cpu: 43.1 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 64 GiB note: est. available: 62.61 GiB used: 8.45 GiB (13.5%)
Processes: 786 Power: uptime: 1h 48m wakeups: 0 Init: systemd v: 257
target: graphical (5) default: graphical
Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 91
Compilers: clang: 20.1.3 gcc: 15.0.1 Shell: Bash v: 5.2.37
running-in: ptyxis-agent inxi: 3.3.37
Here is the output of journalctl -b -1 -p 2 -p 3:
Apr 24 10:44:43 buba kernel: ee1004 4-0056: Failed to select page 0 (-6)
Apr 24 10:44:43 buba kernel:
Apr 24 10:44:44 buba /usr/bin/nvidia-powerd[1581]: Found unsupported configuration. Exiting...
Apr 24 10:44:45 buba abrtd[1690]: '/var/spool/abrt/Python3-2024-04-29-16:52:38-20372.new' is not a problem directory
Apr 24 10:44:45 buba abrtd[1690]: '/var/spool/abrt/Python3-2024-05-12-12:32:34-8163.new' is not a problem directory
Apr 24 10:44:46 buba abrtd[1690]: '/var/spool/abrt/oops-2024-12-11-09:44:16-2398-1' is not a problem directory
Apr 24 10:44:46 buba abrtd[1690]: '/var/spool/abrt/oops-2024-12-14-00:39:07-2412-1' is not a problem directory
Apr 24 10:44:51 buba firewalld[1687]: ERROR: NAME_CONFLICT: new_policy_object(): 'docker-forwarding'
Apr 24 10:45:08 buba polkitd[1583]: Error converting subject to JS object: Process 2575 terminated
Apr 24 10:45:08 buba dbus-broker-launch[1566]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Apr 24 10:45:09 buba kernel: watchdog: watchdog0: watchdog did not stop!
Here is the previous boot journalctl -b -1
Apr 24 10:44:43 buba kernel: ee1004 4-0056: Failed to select page 0 (-6)
Apr 24 10:44:43 buba kernel:
Apr 24 10:44:44 buba /usr/bin/nvidia-powerd[1581]: Found unsupported configuration. Exiting...
Apr 24 10:44:45 buba abrtd[1690]: '/var/spool/abrt/Python3-2024-04-29-16:52:38-20372.new' is not a problem directory
Apr 24 10:44:45 buba abrtd[1690]: '/var/spool/abrt/Python3-2024-05-12-12:32:34-8163.new' is not a problem directory
Apr 24 10:44:46 buba abrtd[1690]: '/var/spool/abrt/oops-2024-12-11-09:44:16-2398-1' is not a problem directory
Apr 24 10:44:46 buba abrtd[1690]: '/var/spool/abrt/oops-2024-12-14-00:39:07-2412-1' is not a problem directory
Apr 24 10:44:51 buba firewalld[1687]: ERROR: NAME_CONFLICT: new_policy_object(): 'docker-forwarding'
Apr 24 10:45:08 buba polkitd[1583]: Error converting subject to JS object: Process 2575 terminated
Apr 24 10:45:08 buba dbus-broker-launch[1566]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Apr 24 10:45:09 buba kernel: watchdog: watchdog0: watchdog did not stop!
Two boots back seems to be tricky to post since it is too long and I cannot attach it as a text file. @litemotiv , what would be the best way to to share it with you?
You would only have to post the log for a boot that failed with the 6.14 kernel, it should probably not be very long since the boot fails quite early.
If you boot once with a 6.14 kernel and afterwards into a working 6.13 kernel, then the -b -1 parameter would show the previous (failed) boot. If you boot twice into a working 6.13 kernel then the -b parameter would show the log of a working 6.13 kernel, which wouldn’t be needed at this point.
Does that make a difference? If the log is still too long you can also use an online pastebin to temporarily save the log.
I just tried booting 6.14 and then come back to 6.13. It does not seem that journalctl is able to pick up the fact that I have tried booting 6.14. It only comes up with information about booting 6.13.
Ahh i think i’m being a bit stupid yes, if the drive fails then obviously it’s not going to write any boot log either. 
I just wanted to clarify that I get the exact same issue when trying to boot the Fedora live usb. I have a laptop that boots it without any problems and I have not had any issues with kernel 6.14 on the laptop.
Did you by chance get this figured out? I also cant boot kernel 6.14.x on my Fedora 41 machine
Interestingly enough, our machines are in many ways similar. Mine has a 28-core i9-7940x + 128 gb ram + 1080ti, so both are high core count / high memory machines with higher end nvidia GPU’s. Also, both of our machines have the root filesystem on a nvme drive. Not sure why, but I have a gut feeling that i important.
I was able to get into a dracut emergency shell and look around a bit. The problem seems to be that a handful of kernel modules arent getting loaded because they fail to decompress properly. running dmegs/journalctl also tells me that iscsi was requested but that the kernel/initrd doesnt support iscsi (even though the dracut iscsi module is included and the iscsi kmods are present in the initrd).
a bunch of block devices are also missing from/dev. My sata HDDs are showing up ok e.g., as /dev/sda1). But, my nvme drives arent appearing as block devices, and plugging in a usb flash drive doesnt do anything either. Notably, /dev/disk is missing entirely. Assuming we are htting the same underlying bug, this would explain why your boot freezes on accessing /dev/disk/by-uuid/...
I finally managed to get kernel 6.14 to work on my machine. I needed modify the BIOS settings so that my NVME does not run in RAID mode. After making that change reinstalling the kernel was necessary. Now everything seems to run smoothly.