1. Please describe the problem: Kernel 6.17.3 fails to boot with kernel panic or just gets stuck at a job dev-disk-by. The panic occurs during idle state with VMD (Volume Management Device) interrupt handling. The system freezes at boot showing a kernel panic with call trace through vmd_irq → generic_handle_irq → handle_edge_irq → common_interrupt. The panic happens when CPU enters idle state (cpuidle_enter_state visible in trace). System has Intel VMD enabled in UEFI. Previous kernel 6.17.2 boots normally without issues. 2. What is the Version-Release number of the kernel: 6.17.3-300.fc43.x86_64 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : Yes, it worked previously. Issue first appeared in kernel 6.17.3. Kernel earlier versions work fine. This is a regression specific to 6.17.3. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Yes, 100% reproducible: 1. Boot kernel 6.17.3-300.fc43.x86_64 2. System gets past GRUB and starts loading 3. Kernel panic occurs during boot process as system enters idle state 4. Panic shows VMD interrupt handling in call trace 5. System becomes unresponsive Hardware: ASUS TUF F15 laptop with Intel VMD enabled in UEFI Dual boot setup: Windows 11 + Fedora 43 Beta KERNEL PANIC! Please reboot your computer. Fatal exception in interrupt 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: Not tested. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No, using stock Fedora kernel only, but I do have Nvidia proprietary driver installed from RPMFusion, or the open driver I'm not sure. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. Kernel panic prevents normal boot, so full journalctl logs are not available. Photos of kernel panic screen showing call trace are in the discussion forum. Discussion and logs available at: https://discussion.fedoraproject.org/t/kernel-6-17-3-cannot-boot-kernel-panic/168976/20 Reproducible: Always
Created attachment 2109945 [details] Images of boot logs
Created attachment 2109946 [details] Images of boot logs other half
Some logs so you don't have to search for them in the discussion: 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). 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) =========================================================================================== 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 =========================================================================================== 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% / =========================================================================================== 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 =========================================================================================== 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
Want to give https://koji.fedoraproject.org/koji/taskinfo?taskID=138203144 a try?
Yeah, I will try it tomorrow. Thanks!
Created attachment 2110011 [details] NEW bootlog Something related to SELinux, is this fine?
(In reply to Justin M. Forbes from comment #4) > Want to give https://koji.fedoraproject.org/koji/taskinfo?taskID=138203144 a > try? Bravo! It works. Booted just fine, NVDIA works too. Checked the logs while it was booting, nothing crazy except "Received SIGTERM from PID 1 (systemd), etc..", you can take a look at the image (look at attachment named NEW bootlog to see if it's fine). Can you tell me what you did that made it work, I'm curious?
Pulled back and additional patch: PCI: vmd: override irq_startup()/irq_shutdown() in vmd_init_dev_msi_info() I will do a 6.17.3-301 build and push that.
Thanks!
FEDORA-2025-95d3b19dcb (kernel-6.17.3-301.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-95d3b19dcb
FEDORA-2025-95d3b19dcb has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-95d3b19dcb` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-95d3b19dcb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-ae16e384fa (kernel-6.17.4-300.fc43 and kernel-headers-6.17.4-300.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.