1. Please describe the problem: Lenovo P1 Gen7 laptop does not boot with kernel 6.16.9. This is a Fedora 42 KDE installation with LUKS FDE. 2. What is the Version-Release number of the kernel: kernel-6.16.9-200.fc42 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernel kernel-6.16.8-200.fc42 works fine 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: - Install 6.16.9 kernel - Rebooot - Select new kernel in grub 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``: Have not tried it 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. There is no boot attempt in logs with 6.16.9 kernel and the screen is black, so hard to tell what is happening. Reproducible: Always
kernel-6.17.0-0.rc7.56.fc43 boots fine
What happens if you edit the kernel command line and remove rhgb and quiet?
@jforbes there was nothing obvious after removing rhgb and quiet, at least no errors that I can see (I can send a link to a video), but one line about blacklisting i915 reminded me that I have xe driver enabled instead of i915 with `i915.force_probe=!7d55` and `xe.force_probe=7d55`. After removing it it booted fine. There are few commits in 6.16.9 what touches drm/xe.
Ah, found a relevant issue upstream: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/6239
*** Bug 2399838 has been marked as a duplicate of this bug. ***
I would raise the priority then, since Lunar Lake (at least) relies on Xe driver solely. @jforbes is it possible to try to revert mentioned specific commit 97207a4fed5348ff5c5e71a7300db9b638640879 (drm/xe/guc: Enable extended CAT error reporting) ?
It is staged to be reverted with the 6.16.10 kernel this week.
It seems there are two commits which must be reverted: "Yes, reverting both dd1a415dcfd5 "drm/xe/guc: Set RCS/CCS yield policy" and 97207a4fed53 "drm/xe/guc: Enable extended CAT error reporting" from 6.16.y fixes the issue for me." https://lore.kernel.org/stable/616f634e-63d2-45cb-a4f9-b34973cc5dfd@iyanmv.com/T/#m71801634ea93ddb2affeaf8918ca1d4bdaa17be3 I suppose those reverts will be in next stable kernel release.
6.16.10 has been in updates testing for a while and should get to stable today. It has the reverts.
*** Bug 2401865 has been marked as a duplicate of this bug. ***
*** Bug 2401607 has been marked as a duplicate of this bug. ***
*** Bug 2401233 has been marked as a duplicate of this bug. ***
*** Bug 2401264 has been marked as a duplicate of this bug. ***
I confirm that T14 Gen6 Lunar Lake works fine on kernel 6.16.10.
Issue was resolved as of 6.16.10 and xe driver is currently functional.