Bug 2399738
| Summary: | 6.16.9 kernel does not boot on Lenovo P1 Gen7 with Xe driver enabled | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gurenko Alex <agurenko> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 42 | CC: | acaringi, adscvr, airlied, filosoho, hdegoede, hpa, jforbes, josef, kernel-maint, linville, masami256, mchehab, mihai, musashi.mugen, pplachy, ptalbert, robatino, shavel.tom, steved, suraj.ghimire7 |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-11-06 14:05:01 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Gurenko Alex
2025-09-26 13:39:49 UTC
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. |