Fedora Workstation 40 Fails to Boot from Kernel 6.9.x on

PasBern · 06-30-2024, 10:39 AM

Hi all,

my Fedora Workstation 40 fails to boot with all kernel 6.9.x.

I can still start the system with kernel 6.8.9-300.fc40.x86_64.

As I am not Linux-savvy enough to understand where I can find the issue in the boot log, I am searching for help here. I could detect some issue with plasma shell and then the system shutting down all service step by step. But I am not sure, the desktop environment is at fault here, as the system doesn't even proceed to asking my for my passphrase for the encrypted disks.

Since the text file is too large to paste here or another online pastebin provider, I share it via a NextCloud link

Suggestions for a better solution on how to share the log file are welcome.

In case this information helps if this is a hardware detection issue by the kernel here is the hardware info of my desktop computer

Code:

inxi -F
System:
  Host: Fedora-Kotik Kernel: 6.8.9-300.fc40.x86_64 arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.1.1 Distro: Fedora Linux 40 (KDE Plasma)
Machine:
  Type: Desktop Mobo: ASRock model: H470M-ITX/ac serial: <superuser required>
    BIOS: American Megatrends v: P1.20 date: 05/18/2020
CPU:
  Info: 8-core model: Intel Core i7-10700 bits: 64 type: MT MCP cache:
    L2: 2 MiB
  Speed (MHz): avg: 1681 min/max: 800/4800 cores: 1: 800 2: 800 3: 800
    4: 800 5: 4800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 4800 12: 2900 13: 800
    14: 800 15: 4800 16: 800
Graphics:
  Device-1: Intel CometLake-S GT2 [UHD Graphics 630] driver: i915 v: kernel
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 24.1.0
    compositor: kwin_wayland driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: iris gpu: i915 resolution: 1: 1920x1080 2: 1920x1080
  API: EGL v: 1.5 drivers: iris,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.1.2
    renderer: Mesa Intel UHD Graphics 630 (CML GT2)
  API: Vulkan v: 1.3.283 drivers: N/A surfaces: xcb,xlib,wayland
Audio:
  Device-1: Intel Comet Lake PCH cAVS driver: snd_hda_intel
  API: ALSA v: k6.8.9-300.fc40.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.7 status: active
Network:
  Device-1: Intel Ethernet I219-V driver: e1000e
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: a8:a1:59:23:2b:d6
  Device-2: Broadcom BCM4360 802.11ac Dual Band Wireless Network Adapter
    driver: bcma-pci-bridge
  Device-3: Realtek RTL8125 2.5GbE driver: r8169
  IF: enp3s0 state: down mac: a8:a1:59:23:2b:d8
Bluetooth:
  Device-1: Apple Bluetooth USB Host Controller driver: btusb type: USB
  Report: btmgmt ID: hci0 state: up address: C4:B3:01:8F:D1:C3 bt-v: 4.0
Drives:
  Local Storage: total: 1.38 TiB used: 591.73 GiB (42.0%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB
  ID-2: /dev/nvme1n1 vendor: A-Data model: SX8200PNP size: 476.94 GiB
Partition:
  ID-1: / size: 1.37 TiB used: 591.43 GiB (42.0%) fs: btrfs dev: /dev/dm-0
  ID-2: /boot size: 973.4 MiB used: 313.2 MiB (32.2%) fs: ext4
    dev: /dev/nvme1n1p2
  ID-3: /home size: 1.37 TiB used: 591.43 GiB (42.0%) fs: btrfs
    dev: /dev/dm-0
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 40.0 C pch: 56.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 64 GiB note: est. available: 62.45 GiB used: 7.18 GiB (11.5%)
  Processes: 470 Uptime: 25m Shell: Bash inxi: 3.3.34

Ideas, how I can track down the issue are highly appreciated.

mrmazda · 06-30-2024, 11:41 AM

To see where things go wrong, try striking ESC as soon as you leave the boot menu. If that doesn't work well enough to show boot messages as they happen, next time strike the E key at the Grub menu and modify the end of the linu line to exclude rhgb, quiet & splash, and add noplymouth plymouth=0 plymouth.enable=0 to more thoroughly enable boot messaging, and possibly avoid the whole problem. I haven't tried systemd-boot yet, so have no idea if it works the same way. I would expect it to be similar.

If /var/log/journal exists, you could boot 6.8.9 kernel, then run journalctl -b -1 | fpaste to upload the journal from the 6.9.x boot attempt for us to peruse. If fpaste is "not found", install it with dnf and try again. When X11 is used, one should also be able to find Xorg.0.log.old either in /var/log/ or ~/.local/share/xorg/. With Wayland, it's necessary to dig whatever log data it provides out of a -b -# journal. If you're configured with auto-login, then you'll probably need to disable it using 6.8.9 and then try 6.9.x again. If the SDDM login greeter then appears, try an X11 session instead of Wayland, and/or an IceWM session instead of Plasma.

Your log shows core dumps from plasmashell and discover. You might want to try asking on the kde@lists.fedoraproject.org mailing lists. This could be an already known issue. It's possible this is the same problem I had/have with the first Fedora I upgraded to Plasma 6, which is still waiting for me to get back to troubleshooting it over a week later.

PasBern · 06-30-2024, 01:21 PM

Hey,

thanks for your help.

Boot log uploaded via fpaste can be found here: https://paste.centos.org/view/63e65801

I have already set boot to verbose and disabled plymouth as I had had issue with it previously

Will also ask on the KDE mailing list

mrmazda · 06-30-2024, 11:59 PM

That log is from booting 6.8.9, not of any expected use diagnosing trouble booting 6.9.x. What may help is if failed 6.9.x boot writes to journal. If so, you can boot first 6.9.x, then on next boot with 6.8.9, do journalctl -b -1 | fpaste, as already suggested.