Bug 2399838 - 6.16.9 kernel does not boot on Thinkpad T14 Gen 6 Lunar Lake
Summary: 6.16.9 kernel does not boot on Thinkpad T14 Gen 6 Lunar Lake
Keywords:
Status: CLOSED DUPLICATE of bug 2399738
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 42
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-09-26 21:16 UTC by Mihai Harpau
Modified: 2025-10-03 13:02 UTC (History)
14 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-09-29 17:26:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg log (116.72 KB, text/plain)
2025-09-26 21:18 UTC, Mihai Harpau
no flags Details

Description Mihai Harpau 2025-09-26 21:16:53 UTC
1. Please describe the problem:
Thinkpad T14 Gen 6 Lunar Lake Ultra 7 258V does not boot on 6.16.9 kernel.

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 kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
Previous 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 by sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-36f34c04c2
- reboot
- boot with 6.16.9
- goot a black screen where you cannot do anything
- but that laptop is not totally frozen(caps_lock led is still working)

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``:
I didn'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.

Reproducible: Always

Comment 1 Mihai Harpau 2025-09-26 21:18:59 UTC
Created attachment 2107711 [details]
dmesg log

Comment 2 Mihai Harpau 2025-09-27 13:51:09 UTC
6.17.0-0.rc7.250924gcec1e6e5d1ab3.58.fc44.x86_64 boots fine

Comment 3 Gurenko Alex 2025-09-29 16:55:05 UTC
I would assume Lunar Lake can **only** be booted with Xe driver, hence it's the same as: https://bugzilla.redhat.com/show_bug.cgi?id=2399738

Comment 4 Mihai Harpau 2025-09-29 17:10:54 UTC
@agurenko I suppose we can make it a duplicate, right?

Comment 5 Mihai Harpau 2025-09-29 17:26:17 UTC

*** This bug has been marked as a duplicate of bug 2399738 ***


Note You need to log in before you can comment on or make changes to this bug.