Kernel 6.17.3 cannot boot, kernel panic [FIXED]

Ask Fedora
, ,
21

I don’t have windows encrypted, so no bitlocker.
I also have secure boot disabled btw

Inxi fxzz

System:
  Kernel: 6.17.2-300.fc43.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
  Desktop: GNOME v: 49.0 tk: GTK v: 3.24.51 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 43 (Workstation Edition)
Machine:
  Type: Laptop System: ASUSTeK product: ASUS TUF Gaming F15 FX507ZE_FX507ZE
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: FX507ZE v: 1.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: FX507ZE.316 date: 05/03/2023
Battery:
  ID-1: BAT1 charge: 45.5 Wh (100%) condition: 45.5/56 Wh (81.3%) volts: 16.67
    min: 15.93 model: ASUS A32-K55 serial: N/A charging: status: full
    cycles: N/A
CPU:
  Info: 14-core (6-mt/8-st) model: 12th Gen Intel Core i7-12700H bits: 64
    type: MST AMCP arch: Alder Lake rev: 3 cache: L1: 1.2 MiB L2: 11.5 MiB
    L3: 24 MiB
  Speed (MHz): avg: 400 min/max: 400/4600:4700:3500 cores: 1: 400 2: 400
    3: 400 4: 400 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400
    13: 400 14: 400 15: 400 16: 400 17: 400 18: 400 19: 400 20: 400
    bogomips: 107520
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
  Device-1: Intel Alder Lake-P GT2 [Iris Xe Graphics] vendor: ASUSTeK
    driver: i915 v: kernel arch: Xe ports: active: none empty: DP-1,DP-2
    bus-ID: 0000:00:02.0 chip-ID: 8086:46a6
  Device-2: NVIDIA GA107M [GeForce RTX 3050 Ti Mobile] vendor: ASUSTeK
    driver: nvidia v: 580.95.05 arch: Ampere ports: active: eDP-1
    empty: DP-3,HDMI-A-1 bus-ID: 0000:01:00.0 chip-ID: 10de:25a0
  Device-3: Sonix USB2.0 HD UVC WebCam driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 3-7:3 chip-ID: 322e:202c
  Display: wayland server: Xwayland v: 24.1.8 compositor: gnome-shell
    driver: gpu: nv_platform,nvidia,nvidia-nvswitch display-ID: 0
  Monitor-1: eDP-1 model: ChiMei InnoLux 0x153c res: 1920x1080 dpi: 142
    diag: 394mm (15.5")
  API: OpenGL v: 4.6.0 vendor: nvidia v: 580.95.05 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce RTX 3050 Ti Laptop GPU/PCIe/SSE2
    display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: glxinfo gpu: nvidia-settings,nvidia-smi x11: xdriinfo,
    xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Alder Lake PCH-P High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 0000:00:1f.3 chip-ID: 8086:51c8
  Device-2: NVIDIA GA107 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 0000:01:00.1 chip-ID: 10de:2291
  Device-3: ASUSTek C-Media Audio driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 3-9:4 chip-ID: 0b05:6203
  API: ALSA v: k6.17.2-300.fc43.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.4.9 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 Alder Lake-P PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 0000:00:14.3 chip-ID: 8086:51f0
  IF: wlo1 state: down mac: <filter>
  Device-2: Intel Ethernet I219-LM vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 0000:00:1f.6 chip-ID: 8086:1a1e
  IF: eno2 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 3-10:5 chip-ID: 8087:0026
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
    lmp-v: 11
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
    v: 0.6 bus-ID: 0000:00:0e.0 chip-ID: 8086:467f
Drives:
  Local Storage: total: 476.94 GiB used: 15.55 GiB (3.3%)
  ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKNU512GZ size: 476.94 GiB
    speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 39.9 C
Partition:
  ID-1: / size: 129.13 GiB used: 15.51 GiB (12.0%) fs: ext4
    dev: /dev/nvme0n1p6
  ID-2: /boot/efi size: 256 MiB used: 40.4 MiB (15.8%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 43.0 C mobo: N/A
  Fan Speeds (rpm): cpu: 3000
Info:
  Memory: total: 16 GiB available: 15.27 GiB used: 2.71 GiB (17.8%)
  Processes: 454 Power: uptime: 4m wakeups: 0 Init: systemd v: 258
    default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm Compilers: gcc: 15.2.1
    Shell: Bash v: 5.3.0 running-in: ptyxis-agent inxi: 3.3.39

And lsblk

zram0       swap   1     zram0  08a63245-4e87-4e61-bd1e-499e4efe3a8d                [SWAP]
nvme0n1                                                                             
├─nvme0n1p1 vfat   FAT32 SYSTEM 40A7-0E0D                             215,6M    16% /boot/efi
├─nvme0n1p2                                                                         
├─nvme0n1p3 ntfs         OS     961EA8DA1EA8B4A1                                    
├─nvme0n1p4 ntfs                C602875802874BFD                                    
├─nvme0n1p5 vfat   FAT32 MYASUS F49B-9B8F                                           
└─nvme0n1p6 ext4   1.0          f0de5123-896a-4fc4-9a48-4b70fbc321c9    107G    12% /

and fdisk -l

Disk /dev/nvme0n1: 476,94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: INTEL SSDPEKNU512GZ                     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 72628070-24A1-453D-B25E-CD8E6D93276C

Device             Start        End   Sectors   Size Type
/dev/nvme0n1p1      2048     534527    532480   260M EFI System
/dev/nvme0n1p2    534528     567295     32768    16M Microsoft reserved
/dev/nvme0n1p3    567296  720784014 720216719 343,4G Microsoft basic data
/dev/nvme0n1p4 998160384  999804927   1644544   803M Windows recovery environment
/dev/nvme0n1p5 999804928 1000214527    409600   200M Windows recovery environment
/dev/nvme0n1p6 720785408  998160383 277374976 132,3G Linux filesystem

Partition table entries are not in disk order.


Disk /dev/zram0: 8 GiB, 8589934592 bytes, 2097152 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
22

So should I disable VMD if windows is not encrypted. I heard that VMD is only enterprise stuff that Intel for some reason pushed for consumers and OEMs even enable it by default (which is in my case)… Can you tell me if this is the way to make sure windows doesn’t break if I disable VMD?

  1. Before disabling VMD in UEFI:
    • Boot into Windows
    • Open Device Manager
    • Look under “Storage controllers”
    • You’ll see “Intel Volume Management Device” or similar
    • Right-click → Update Driver → Browse → Let me pick → Choose “Standard NVMe Controller” or “Standard SATA AHCI Controller”
    • Reboot Windows to confirm it still works
      then disable VMD. Is this safe or this method even valid? (I asked claude since it’s hard to find answers for that.
23

If the SSD also has a second device ( Optane?) then this device would appear as a 2nd smaller ssd. You could give that a go. But it probably won’t change the outcome.
Best to open a bug report on bugzilla.redhat.com and sit this one out and hope 6.17.4 will have a fix.

1 Like
24

No, optane is discontinued, and not included in laptops like mine ASUS TUF F15 from 2023.
I will file a bug report on bugzilla, thanks.

25

In that fdisk ouput I seem to see space between p3 which ends at 720784014 and p6 which begins at 720785408
I also see in the screenshots that it appears to be running fsck on p6.

The more concerning thing is that /boot/efi seems to be the original efi partion for windows at only 260M in size and that you seem to have an additional efi partition (p5) according to lsblk.

What is the output of df -h?

26 
Filesystem      Size  Used Avail Use% Mounted on
/dev/nvme0n1p6  130G   16G  107G  13% /
devtmpfs        7,6G     0  7,6G   0% /dev
tmpfs           7,7G   92K  7,7G   1% /dev/shm
efivarfs        192K  128K   60K  69% /sys/firmware/efi/efivars
tmpfs           3,1G  2,5M  3,1G   1% /run
tmpfs           1,0M     0  1,0M   0% /run/credentials/systemd-journald.service
tmpfs           7,7G  8,0K  7,7G   1% /tmp
/dev/nvme0n1p1  256M   41M  216M  16% /boot/efi
tmpfs           1,0M     0  1,0M   0% /run/credentials/systemd-resolved.service
tmpfs           1,6G  168K  1,6G   1% /run/user/1000

The more concerning thing is that /boot/efi seems to be the original efi partion for windows at only 260M in size and that you seem to have an additional efi partition (p5) according to lsblk.

Yeah I use the original EFI partition, as I didn’t have the need to create another one, and everything worked fine before this kernel update for months. But an additional efi partition? I don’t think so, it must be windows recovery or MYSASUS recovery partition, because I have a lot of those partitions, I think whole 2 recovery partitions

Edit: yeah it’s not an EFI partition, it’s MYASUS app stuff. Don’t worry about that

27

I wouldn’t touch windows yet. You can change VMD to AHCI and try booting linux. Changing back to VMD should enable booting Windows again.

1 Like
28

Actually no, I won’t disable VMD yet. I will just file a bugreport and play it safe since the word “SHOULD” worries me. Unless you got a 100% proven safe method of doing that.

29

this is some pre-loaded windows stuff

/dev/nvme0n1p4 998160384  999804927   1644544   803M Windows recovery environment
/dev/nvme0n1p5 999804928 1000214527    409600   200M Windows recovery environment

/dev/nvme0n1p3 was shrunk and /dev/nvme0n1p6 created to install fedora. The installer created the new patition at certain block boundaries. So you could add that space to your windows partition /dev/nvme0n1p3

30

I don’t need that space for windows

31

no one will give you 100% proven safe method. I’ve done that switch with an old h10 optane intel ssd. Switching back to VMD restored Windows boot capabilities on that system. :slight_smile:

32

I’m not risking that

1 Like
33

Kernel failures happen. Happened a lot on 6.16 :slight_smile:

Test days are on https://fedoraproject.org/wiki/Test_Day:2025-10-12_Kernel_6.17_Test_Week

Says to report bugs under kernel in bugzilla.redhat.com

I would not bother fixing a . . n kernel failure on your own machine.

1 Like
34

I forgot that ASUS now does the extra recovery partition. p5 is labeled MYASUS so that is accounted for.

With the repeated failure to boot the 6.17.3 kernel (which ends with the fsck service) I would consider booting to the live media then run fsck manually on p6 (your system partition) to ensure the device file system is 100% clean. This error seems like something within the space used for the initramfs image may have gotten corrupted and thus the file system needs to be totally clean before creating a new image for booting that kernel.

35

This ain’t the problem at all, if it was corrupted, I wouldn’t be able to boot other kernels like the previous minor version 6.17.2.
Something is wrong with VMD, as the actual panic happened ABOVE that in the call trace, above this service.

If it were filesystem corruption, I’d see I/O errors, read/write failures, other kernels would also have problems, the panic would be in filesystem code, not interrupt handling.

The initramfs is fine, because if it weren’t, the kernel wouldn’t load at all, I’d get “Failed to load initramfs” errors, I wouldn’t get this specific VMD interrupt panic

I may be totally wrong here, so you can correct me if you can. I’m new to this.

36

I cannot argue against the potential hardware/bios (VMD) problem.
I just installed the 6.17.3 kernel on my desktop with nvidia drivers and the system booted properly with the new kernel.

$ uname -r
6.17.3-300.fc43.x86_64

It does not appear to be a kernel specific problem unless it is a hardware related regression.

One other thing you may try would be to totally remove the new kernel then reinstall it and see if anything changes.
sudo dnf remove kernel\*6.17.3\*

37

Well, do you have VMD enabled?
Also i don’t think wasting time trying to reinstall the kernel will do anything.

And yes it is hardware specific kernel regression most likely.

I already filed a bug report, let’s wait and see.

1 Like
38

Well, there is a difference.

  1. My bios does not have VMD
  2. I installed the kernel from the f43 updates-testing repo and it appears you might have gotten it from bodhi.? Is that correct?
    Potentially there may be a difference in what was installed.
39

No I have also gotten it from updates-testing repo.

And yeah see, that confirms it’s a VMD related issue, since on your machine, you do not have VMD and it works. Great

40

It seams the test-days are still for F42, the OP is on F43.


koji download-build --arch=$(uname -m) kernel-6.17.1-300.fc42

F42 is still on 6.17.1