Kernel 6.17.3 cannot boot, kernel panic [FIXED]

mrfox · October 16, 2025, 12:31pm

Opening a topic from Making sure you're not a bot! (check this site for more info about this)

So basically, when booting kernel 6.17.3-300.fc43, my loading screen gets enlarged, and stuck in a loading loop. However, kernel 6.17.2 works seamlessly.

Some info:
12Device-2 NVIDIA GA107M [GeForce RTX 3050 Ti Mobile] 12driver nvidia 12v 580.95.05 12Display wayland 12server [X.Org](http://X.Org) 12v 24.1.8 12with Xwayland 12v 24.1.8 12compositor gnome-shell 12v 49.0 12driver 12gpu nv_platform,nvidia,nvidia-nvswitch 12resolution 1920x1080~144Hz 12API OpenGL 12v 4.6.0 12vendor nvidia 12v 580.95.05 12renderer NVIDIA GeForce RTX 3050 Ti Laptop GPU/PCIe/SSE2

Asus TUF F15 (FX507ZE).

I did both dracut -f --regenerate-all, and also akmods --rebuild --force --kernels , and checked the logs, and it was successfully built (the modules were successfully built). But still same issue nothing changed. Boot logs only seem to be for the 6.17.2 kernel boots, none about 6.17.3 not in journal, not even in /var

sudo dmesg | grep -iE “secure|nvidia”

[    0.000000] secureboot: Secure boot disabled
[    0.015898] secureboot: Secure boot disabled
[    5.935236] Bluetooth: hci0: Secure boot is enabled
[    5.967260] nvidia: loading out-of-tree module taints kernel.
[    5.967271] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[    6.062099] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[    6.068027] nvidia 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
[    6.119263] NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64  580.95.05  Release Build  (dvs-builder@U22-I3-B17-02-5)  Tue Sep 23 09:55:41 UTC 2025
[    6.140297] nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for x86_64  580.95.05  Release Build  (dvs-builder@U22-I3-B17-02-5)  Tue Sep 23 09:42:01 UTC 2025
[    6.142801] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[    6.147016] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input24
[    6.147071] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input25
[    6.147107] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input26
[    6.147143] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input27
[    7.749509] [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 2
[    7.777643] nvidia 0000:01:00.0: vgaarb: deactivate vga console
[    7.786432] fbcon: nvidia-drmdrmfb (fb0) is primary device
[    7.786436] nvidia 0000:01:00.0: [drm] fb0: nvidia-drmdrmfb frame buffer device

uname -a
Linux fedora 6.17.2-300.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Oct 12 17:36:07 UTC 2025 x86_64 GNU/Linux (because only 6.17.2 boots)

output of journalctl -b -0 | grep -iE “secure|nvidia|fail”

okt 16 18:09:33 fedora systemd-vconsole-setup[327]: /usr/bin/setfont failed with a "system error" (EX_OSERR), ignoring.
okt 16 18:09:33 fedora systemd-vconsole-setup[327]: Configuration of first virtual console failed, ignoring remaining ones.
okt 16 18:09:34 fedora systemd-vconsole-setup[516]: /usr/bin/setfont failed with a "system error" (EX_OSERR), ignoring.
okt 16 18:09:34 fedora systemd-vconsole-setup[516]: Configuration of first virtual console failed, ignoring remaining ones.
okt 16 18:09:34 fedora kernel: pci 10000:e0:06.0: bridge window [io  size 0x1000]: failed to assign
okt 16 18:09:34 fedora kernel: pci 10000:e0:06.0: bridge window [io  size 0x1000]: failed to assign
okt 16 18:09:36 fedora kernel: i915 0000:00:02.0: [drm] [ENCODER:261:DDI A/PHY A] failed to retrieve link info, disabling eDP
okt 16 15:09:37 fedora systemd[1]: systemd-boot-clear-sysfail.service - Clear SysFail Entry If The Boot Is Successful was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderEntrySysFail-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
okt 16 15:09:38 fedora kernel: Bluetooth: hci0: Secure boot is enabled
okt 16 15:09:38 fedora systemd[1]: systemd-boot-clear-sysfail.service - Clear SysFail Entry If The Boot Is Successful was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderEntrySysFail-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
okt 16 15:09:38 fedora systemd[1]: systemd-boot-clear-sysfail.service - Clear SysFail Entry If The Boot Is Successful was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderEntrySysFail-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
okt 16 15:09:38 fedora kernel: nvidia: loading out-of-tree module taints kernel.
okt 16 15:09:38 fedora kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
okt 16 15:09:38 fedora systemd-vconsole-setup[784]: /usr/bin/setfont failed with a "system error" (EX_OSERR), ignoring.
okt 16 15:09:38 fedora kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 509
okt 16 15:09:38 fedora kernel: nvidia 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
okt 16 15:09:38 fedora systemd-vconsole-setup[784]: Configuration of first virtual console failed, ignoring remaining ones.
okt 16 15:09:38 fedora kernel: asus_wmi: fan_curve_get_factory_default (0x00110032) failed: -19
okt 16 15:09:38 fedora kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64  580.95.05  Release Build  (dvs-builder@U22-I3-B17-02-5)  Tue Sep 23 09:55:41 UTC 2025
okt 16 15:09:38 fedora systemd[1]: systemd-boot-clear-sysfail.service - Clear SysFail Entry If The Boot Is Successful was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderEntrySysFail-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
okt 16 15:09:38 fedora kernel: nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for x86_64  580.95.05  Release Build  (dvs-builder@U22-I3-B17-02-5)  Tue Sep 23 09:42:01 UTC 2025
okt 16 15:09:38 fedora kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
okt 16 15:09:38 fedora systemd[1]: systemd-boot-clear-sysfail.service - Clear SysFail Entry If The Boot Is Successful was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderEntrySysFail-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
okt 16 15:09:38 fedora kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input24
okt 16 15:09:38 fedora kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input25
okt 16 15:09:38 fedora kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input26
okt 16 15:09:38 fedora kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input27
okt 16 15:09:38 fedora systemd[1]: systemd-boot-clear-sysfail.service - Clear SysFail Entry If The Boot Is Successful was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderEntrySysFail-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
okt 16 15:09:38 fedora systemd[1]: systemd-boot-clear-sysfail.service - Clear SysFail Entry If The Boot Is Successful was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderEntrySysFail-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
okt 16 15:09:40 fedora kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 2
okt 16 15:09:40 fedora kernel: nvidia 0000:01:00.0: vgaarb: deactivate vga console
okt 16 15:09:40 fedora kernel: fbcon: nvidia-drmdrmfb (fb0) is primary device
okt 16 15:09:40 fedora kernel: nvidia 0000:01:00.0: [drm] fb0: nvidia-drmdrmfb frame buffer device
okt 16 15:09:40 fedora systemd[1]: systemd-boot-clear-sysfail.service - Clear SysFail Entry If The Boot Is Successful was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderEntrySysFail-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
okt 16 15:09:40 fedora systemd[1]: systemd-boot-clear-sysfail.service - Clear SysFail Entry If The Boot Is Successful was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderEntrySysFail-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
okt 16 15:09:40 fedora systemd[1]: Starting systemd-backlight@backlight:nvidia_0.service - Load/Save Screen Backlight Brightness of backlight:nvidia_0...
okt 16 15:09:40 fedora systemd[1]: Finished systemd-backlight@backlight:nvidia_0.service - Load/Save Screen Backlight Brightness of backlight:nvidia_0.
okt 16 15:09:40 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-backlight@backlight:nvidia_0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
okt 16 15:09:40 fedora systemd[1]: akmods-keygen@akmods-keygen.service - Akmods Secure boot MOK Key Generation was skipped because no trigger condition checks were met.
okt 16 15:09:40 fedora systemd[1]: Started nvidia-powerd.service - nvidia-powerd service.
okt 16 15:09:40 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nvidia-powerd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
okt 16 15:09:40 fedora nvidia-powerd[987]: nvidia-powerd version:2.0 (build 1)
okt 16 15:09:40 fedora nvidia-powerd[987]: DBus Connection is established
okt 16 15:09:40 fedora nvidia-powerd[987]: ERROR! DC power limits table is not supported
okt 16 15:09:40 fedora nvidia-powerd[987]: ERROR! Failed to get SysPwrLimitGetInfo!!
okt 16 15:09:40 fedora nvidia-powerd[987]: CRITICAL! Failed to get SysPwrLimitGetInfo
okt 16 15:09:40 fedora nvidia-powerd[987]: ERROR! JPAC is not created/already destroyed, ignoring request.
okt 16 15:09:40 fedora boltd[1150]: [c39e8780-d01b-domain0                    ] udev: failed to determine if uid is stable: unknown NHI PCI id '0x463e'
okt 16 15:09:40 fedora systemd[1]: nvidia-fallback.service - Fallback to nouveau as nvidia did not load was skipped because of an unmet condition check (ConditionPathExists=!/sys/module/nvidia).
okt 16 15:09:41 fedora nvidia-powerd[987]: ERROR! Failed to get SysPwrLimitGetInfo!!
okt 16 15:09:41 fedora dbus-broker-launch[969]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.
okt 16 15:09:41 fedora nvidia-powerd[987]: CRITICAL! Failed to get SysPwrLimitGetInfo
okt 16 15:09:41 fedora audit[1326]: AUDIT1103 pid=1326 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='op=PAM:setcred grantors=? acct="gdm-greeter" exe="/usr/lib/systemd/systemd-executor" hostname=fedora addr=? terminal=/dev/tty1 res=failed'
okt 16 15:09:41 fedora wireplumber[1377]: wp-event-dispatcher: wp_event_dispatcher_unregister_hook: assertion 'already_registered_dispatcher == self' failed
okt 16 15:09:41 fedora wireplumber[1377]: wp-event-dispatcher: wp_event_dispatcher_unregister_hook: assertion 'already_registered_dispatcher == self' failed
okt 16 15:09:41 fedora wireplumber[1377]: wp-event-dispatcher: wp_event_dispatcher_unregister_hook: assertion 'already_registered_dispatcher == self' failed
okt 16 15:09:41 fedora wireplumber[1377]: wp-event-dispatcher: wp_event_dispatcher_unregister_hook: assertion 'already_registered_dispatcher == self' failed
okt 16 15:09:42 fedora gnome-shell[1385]: Added device '/dev/dri/card2' (nvidia-drm) using atomic mode setting.
okt 16 15:09:43 fedora gsd-media-keys[1504]: Failed to grab accelerator for keybinding settings:hibernate
okt 16 15:09:43 fedora gsd-media-keys[1504]: Failed to grab accelerator for keybinding settings:playback-repeat
okt 16 15:09:43 fedora gsd-usb-protection[1523]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
okt 16 15:09:43 fedora gsd-xsettings[2603]: Failed to get current UI scaling factor: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Destination does not exist
okt 16 15:09:50 fedora nvidia-powerd[987]: ERROR! JPAC is not created/already destroyed, ignoring request.
okt 16 15:09:51 fedora nvidia-powerd[987]: ERROR! JPAC is not created/already destroyed, ignoring request.
okt 16 15:09:52 fedora audit[3365]: AUDIT1103 pid=3365 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='op=PAM:setcred grantors=? acct="rinalds" exe="/usr/lib/systemd/systemd-executor" hostname=fedora addr=? terminal=/dev/tty1 res=failed'
okt 16 15:09:52 fedora wireplumber[3689]: wp-event-dispatcher: wp_event_dispatcher_unregister_hook: assertion 'already_registered_dispatcher == self' failed
okt 16 15:09:52 fedora wireplumber[3689]: wp-event-dispatcher: wp_event_dispatcher_unregister_hook: assertion 'already_registered_dispatcher == self' failed
okt 16 15:09:52 fedora wireplumber[3689]: wp-event-dispatcher: wp_event_dispatcher_unregister_hook: assertion 'already_registered_dispatcher == self' failed
okt 16 15:09:52 fedora wireplumber[3689]: wp-event-dispatcher: wp_event_dispatcher_unregister_hook: assertion 'already_registered_dispatcher == self' failed
okt 16 15:09:52 fedora nvidia-powerd[987]: ERROR! JPAC is not created/already destroyed, ignoring request.
okt 16 15:09:52 fedora gnome-shell[3692]: Added device '/dev/dri/card2' (nvidia-drm) using atomic mode setting.
okt 16 15:09:53 fedora gsd-keyboard[3828]: g_variant_unref: assertion 'value != NULL' failed
okt 16 15:09:53 fedora systemd[3365]: Started app-gnome-nvidia\x2dsettings\x2duser-3890.scope - Application launched by gnome-session-service.
okt 16 15:09:53 fedora abrt-applet[4023]: Failed to rename ‘/home/rinalds/.abrt/spool’ to ‘/home/rinalds/.cache/abrt/spool’: No such file or directory
okt 16 15:09:53 fedora abrt-applet[4023]: Failed to rename ‘/home/rinalds/.abrt/settings’ to ‘/home/rinalds/.config/abrt/settings’: No such file or directory
okt 16 15:09:53 fedora gsd-usb-protection[3902]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
okt 16 15:09:53 fedora gsd-media-keys[3830]: Failed to grab accelerator for keybinding settings:hibernate
okt 16 15:09:53 fedora gsd-media-keys[3830]: Failed to grab accelerator for keybinding settings:playback-repeat
okt 16 15:09:54 fedora libcanberra-login-sound.desktop[3865]: Failed to play sound: File or data not found
okt 16 15:09:54 fedora gsd-xsettings[5258]: Failed to get current UI scaling factor: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Destination does not exist
                                     (pkla-check-authorization:5390): GLib-GObject-CRITICAL **: 15:09:54.527: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
okt 16 15:09:54 fedora gnome-shell[1385]: Failed to store screen time limits data: Error opening file “/run/gdm/home/gdm-greeter/.local/share/gnome-shell/session-active-history.json”: No such file or directory
okt 16 15:09:54 fedora systemd[1326]: dbus-:1.2-org.gnome.Settings.GlobalShortcutsProvider@0.service: Main process exited, code=exited, status=1/FAILURE
okt 16 15:09:54 fedora systemd[1326]: dbus-:1.2-org.gnome.Settings.GlobalShortcutsProvider@0.service: Failed with result 'exit-code'.
                                     (pkla-check-authorization:5419): GLib-GObject-CRITICAL **: 15:09:54.655: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
                                     (pkla-check-authorization:5423): GLib-GObject-CRITICAL **: 15:09:54.666: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

anotheruser · October 16, 2025, 12:37pm

remove ‘rhgb quiet’ from kernel command line and see where the boot hangs. The absence of journal logs for kernel 6.17.3 seems to indicate that the boot process gets stuck at a very early stage.

mrfox · October 16, 2025, 12:49pm

Alright, so.
I saw some jobs running multiple times each 30 seconds something about dev-disk-by, and then after they completed, boom, a kernel panic about some interrupt.

barryascott · October 16, 2025, 12:50pm

Take a photo of the kernel panic and post here please.

mrfox · October 16, 2025, 12:51pm

I mean, there’s nothing much about the kernel panic.

It basically says on full screen

KERNEL PANIC!
Please reboot your computer.
Fatal exception in interrupt

nothing else.

I can also try booting with loglevel=7 if you want

barryascott · October 16, 2025, 1:10pm

Boot after removing “rhgb quiet” from the kernel command line.

Then you will see a stack trace for the panic with lots of info.

mrfox · October 16, 2025, 1:22pm

Yeah I did indeed, but now it seems to be stuck at the jobs again, no kernel panic anymore, or I just have to wait even longer than 6 minutes? Seems absurd, but should I? Should I restart till i get a kernel panic somehow

Here are some photos:

mrfox · October 16, 2025, 1:29pm

Oh yeah I did get the kernel panic now very quickly somehow, but like, even with the parameters quiet and rhbg removed, even with/without loglevel=7, it opens the fullscreen linux kernel panic where there is the ascii penguin, and the same text which I sent you earlier

Note: I did not change any partition stuff before updating the system.
I have a dual boot with Windows 11 setup.
I did mount everything correct, i have ext4 fs for root.
Only /boot/efi 260MB and /, 132gb

barryascott · October 16, 2025, 1:31pm

That suggests that you have a problem with the initramfs not matching the disks in your /etc/fstab.

I take it that this was working and then something was changed.

Do you remember what has changed since it was last working?

mrfox · October 16, 2025, 1:33pm

No nothing changed really, because it was only one day, before I installed this update and it does this.
I remember 6.17.2 installed seamlessly though with no issues, so this definitely is related to this .3 version.

I did not change anything related to partitions, I was just browsing firefox.

Maybe windows messed something up? Even though it didn’t have any updates

barryascott · October 16, 2025, 1:34pm

Can you boot from the 6.17.2?

mrfox · October 16, 2025, 1:34pm

Yeah I can indeed with no issues. Currently I’m on 6.17.2

barryascott · October 16, 2025, 1:37pm

Check in dmesg for any kernel stack traces, like you took a photo of.

If your dmesg is clean then it looks like you may have a regression on your hardware for the 6.17.3 kernel.

anothermindbomb · October 16, 2025, 1:38pm

If you look at the systemd-fsck entry for the disks in question, if they are like mine, they have this at the end of the file.

You can view this via systemctl cat systemd-fsck@dev-disk-by\\x2duuid-aa9d5fa9\\x2d811f\\x2d406e\\x2dbfc2\\x2debc488cc168e.service where you obviously plug in the uuid of your disk in question.

# /usr/lib/systemd/system/service.d/10-timeout-abort.conf
# This file is part of the systemd package.
# See https://fedoraproject.org/wiki/Changes/Shorter_Shutdown_Timer.
#
# To facilitate debugging when a service fails to stop cleanly,
# TimeoutStopFailureMode=abort is set to "crash" services that fail to stop in
# the time allotted. This will cause the service to be terminated with SIGABRT
# and a coredump to be generated.
#
# To undo this configuration change, create a mask file:
#   sudo mkdir -p /etc/systemd/system/service.d
#   sudo ln -sv /dev/null /etc/systemd/system/service.d/10-timeout-abort.conf

[Service]
TimeoutStopFailureMode=abort

I’m wondering if the crash/coredump was triggered deliberately by systemd as the “service failed to stop in the time allotted”.

anotheruser · October 16, 2025, 1:40pm

Do you have VMD enabled in UEFI settings?
There are two RIPs in the first image. the first seems to come from vmd controller.

mrfox · October 16, 2025, 1:48pm

Yes that file has that line at the end for me too

mrfox · October 16, 2025, 1:49pm

dmesg is clean - only shows the successfull kernel boot logs 6.17.2.

mrfox · October 16, 2025, 1:51pm

Yes, VMD controller is enabled. Should I disable it?

I have a dual boot setup with windows though, so disabling VMD will mess with windowd

anotheruser · October 16, 2025, 2:09pm

not yet. Only if you have windows bitlocker recovery keys available.
pls post output of inxi -Fxxz and lsblk -f
But there were no changes to vmd.c between 6.17.2 and 6.17.3 as far as I can tell.

mrfox · October 16, 2025, 2:10pm

I tried messing with boot parameters now like: pci=nomsi intel_iommu=off vmd.dyndbg=+p

Also asked AI (claude) about this so take this text below with a grain of salt but it said this:

The panic occurs when:

System goes idle
CPU tries to enter a low-power state
An interrupt comes through the VMD controller
Something in the interrupt handling path is broken in 6.17.3
System panics

The Problem

The call trace shows:

vmd_irq - VMD interrupt handler
generic_handle_irq
handle_irq_event_percpu
handle_edge_irq
common_interrupt

And critically at the bottom of image 2: cpuidle_enter_state and do_idle - the system is panicking during idle state.

Topic		Replies	Views
Fedora hangs on boot after upgrading to kernel 6.3.4 Ask Fedora f38 , gnome , intel , kernel	89	11446	July 8, 2023
Can't boot with latest kernel, may be another nVidia problem Ask Fedora f35 , nvidia	21	3216	February 18, 2022
[SOLVED] No boot with 6.4.7 kernel, everything is fine with 6.2.9. I'm stuck! Ask Fedora f38 , boot , desktop	25	2379	August 8, 2023
Fedora 37 Workstations Can't Boot 6.2.7 Ask Fedora f37 , amd , radeon , kernel , workstation	14	1270	April 24, 2023
Laptop fails to boot after update to kernel-6.4.4-200.fc38.x86_64 Ask Fedora f38	28	3033	August 14, 2023

Kernel 6.17.3 cannot boot, kernel panic [FIXED]

The Problem

Related topics