Fedora Account System
Red Hat Associate
Red Hat Customer
1. Please describe the problem: After updating to kernel 7.0.4-200.fc44.x86_64, my system experiences hard freezes at random times, specifically triggered when applications like Firefox use hardware acceleration, or when switching displays. Checking the logs reveals that the i915 graphics driver is failing to initialize the Graphics Security Controller (GSC) because it cannot find the Intel Management Engine Interface (mei) component. Checking lsmod confirms that the mei, mei_me, and mei_gsc_proxy modules are completely absent. Attempting to manually modprobe mei_me fails with a "Module not found" error, despite the kernel-modules and kernel-modules-extra packages being installed and freshly reinstalled. This is a regression, as booting into the previous kernel (6.19.14-300.fc44.x86_64) works perfectly. The mei modules load successfully, the i915 driver initializes, and the system is completely stable. 2. What is the Version-Release number of the kernel: Failing: kernel-7.0.4-200.fc44.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 : Working: kernel-6.19.14-300.fc44.x86_64 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Hardware setup: Machine: Lenovo ThinkPad P1 Gen 7 CPU/GPU: Intel Meteor Lake-P (Integrated Intel Arc Graphics, Device ID 7d55). No discrete GPU. BIOS Version: 1.20 (Intel ME is enabled in BIOS). Steps to reproduce: i. Boot into Fedora 44 using kernel 7.0.4-200.fc44.x86_64 on Intel Meteor Lake hardware. ii. Run lsmod | grep mei (returns blank). iii. Attempt to load the module: sudo modprobe mei_me (returns module not found). iv. Use the system normally or launch Firefox with hardware acceleration enabled. 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``: Haven't tried yet. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No. 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. Errors: kernel: i915 0000:00:02.0: [drm] GT1: can't init GSC proxy due to missing mei component kernel: i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy handler failed to init kernel: i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy component didn't bind within the expected timeout Expected Results: The mei modules should be present and loaded by the kernel, allowing the i915 driver to communicate with the GSC without timing out and crashing the display server. Additional Information: To rule out local corruption, I successfully executed sudo dnf reinstall kernel-modules-7.0.4-200.fc44.x86_64 kernel-modules-extra-7.0.4-200.fc44.x86_64 and rebuilt the module tree, but modprobe still cannot locate the files. This suggests the mei modules were either dropped from the build configuration (CONFIG_INTEL_MEI) for the 7.0 branch or are failing to build upstream for this architecture. Note: I am running the internal Fedora CSB image, but the kernel package appears to be the standard upstream Fedora build. Reproducible: Always
It looks like the mei.ko is not built in 7.0.4. $ grep -i CONFIG_INTEL_MEI /boot/config-6.19.14-300.fc44.x86_64 CONFIG_INTEL_MEI=m CONFIG_INTEL_MEI_ME=m CONFIG_INTEL_MEI_TXE=m CONFIG_INTEL_MEI_GSC=m CONFIG_INTEL_MEI_VSC_HW=m CONFIG_INTEL_MEI_VSC=m CONFIG_INTEL_MEI_LB=m CONFIG_INTEL_MEI_HDCP=m CONFIG_INTEL_MEI_PXP=m CONFIG_INTEL_MEI_GSC_PROXY=m CONFIG_INTEL_MEI_WDT=m $ grep -i CONFIG_INTEL_MEI /boot/config-7.0.4-200.fc44.x86_64 # CONFIG_INTEL_MEI is not set This appears to have been intentionally disabled in the 7.0.4 commit: https://src.fedoraproject.org/rpms/kernel/blob/3c67564ff09fe186a28de5e3f37a25e49802a9b3/f/kernel-x86_64-fedora.config#_3232 I'm looking in the upstream kernel source but I can't find any reason why the kmod was disabled in 7.0.4.
*** Bug 2476984 has been marked as a duplicate of this bug. ***
It looks like the mei kmod has been included in the new 7.0.6 kernel that's currently in f44-candidate: $ uname -r 7.0.6-200.fc44.x86_64 $ lsmod|grep mei mei_gsc_proxy 20480 0 mei_wdt 16384 0 mei_me 65536 2 mei 217088 5 mei_gsc_proxy,mei_wdt,mei_me Koji: https://koji.fedoraproject.org/koji/buildinfo?buildID=2995550
FEDORA-2026-cccb681166 (kernel-7.0.6-100.fc43 and kernel-headers-7.0.6-100.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-cccb681166
FEDORA-2026-4462efc052 (kernel-7.0.6-200.fc44 and kernel-headers-7.0.6-200.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-4462efc052
FEDORA-2026-4462efc052 (kernel-7.0.6-200.fc44 and kernel-headers-7.0.6-200.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-cccb681166 (kernel-7.0.6-100.fc43 and kernel-headers-7.0.6-100.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.