Bug 2401607 - Black screen at boot since kernel 6.16.9-200
Summary: Black screen at boot since kernel 6.16.9-200
Keywords:
Status: CLOSED DUPLICATE of bug 2399738
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 42
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-04 22:06 UTC by Tachikoma
Modified: 2025-10-06 17:56 UTC (History)
15 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-10-06 17:56:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
The result of the command journalctl --no-hostname -k > dmesg.txt (116.85 KB, text/plain)
2025-10-04 22:08 UTC, Tachikoma
no flags Details
The result of the command journalctl -b --no-hostname -k > dmesg-bb.txt (118.43 KB, text/plain)
2025-10-04 22:22 UTC, Tachikoma
no flags Details
Actual log for the fail (124.17 KB, text/plain)
2025-10-04 23:03 UTC, Tachikoma
no flags Details

Description Tachikoma 2025-10-04 22:06:50 UTC
1. Please describe the problem:

Hi,

I'm using Fedora 42 Workstation on my laptop, a Dell Inc. Dell 16 Plus 2-in-1 DB06250, this is a Intel® Core™ Ultra 7 258V × 8, there is no discrete GPU, I use the integrated graphics that is recognized as "Intel® Graphics (LNL)" in system informations.

Basically, after I powered it on, the computer used to boot and I had to enter my password when asked by luks for the system to launch. But since kernel 6.16.9-200 I just have a black screen. I end up pressing the power button for a few seconds to shut the computer down. I power it on again and this time I arrive on the GRUB screen where I have to choose between the different kernel. If I choose 6.16.9-200, I'm on a black screen again, but if I choose 6.16.8-200, the computer works fine.

I tried to type my password blindly, it didn't work. I updated the laptop to the latest firmware 1.6.0 in hope to solve the problem, but it didn't change anything.

Best regards


2. What is the Version-Release number of the kernel: 6.16.9-200


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear? 6.16.9-200
It was still working with kernel 6.16.8-200
 


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below: I just have to power on the the computer for the problem to occur.


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``:


6. Are you running any modules that not shipped with directly Fedora's kernel?:
I don't know what this means. I didn't patch the kernel, I didn't touch anything in GRUB.


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

Steps to Reproduce:
1.Power on the computer
2.Wait
3.
Actual Results:
Black screen only

Expected Results:
luks2 asking to enter my password unlock my drive and launch my system

Comment 1 Tachikoma 2025-10-04 22:08:36 UTC
Created attachment 2108523 [details]
The result of the command journalctl --no-hostname -k > dmesg.txt

Comment 2 Tachikoma 2025-10-04 22:22:30 UTC
Created attachment 2108524 [details]
The result of the command journalctl -b --no-hostname -k > dmesg-bb.txt

I only see reference to the kernel 6.16.8, so I tried --b instead of -b but it's the same. I successfully got the computer to reset with Ctrl+Alt+Del when I got the black screen, but I still get the same result where I don't see the kernel 6.16.9 being mentioned for this command.

Comment 3 Tachikoma 2025-10-04 23:03:47 UTC
Created attachment 2108525 [details]
Actual log for the fail

I added -1 to the command : journalctl -b -1 --no-hostname -k and I got the log entry for the actual event, where we can see the errors.
There are lines in red starting at : 
oct. 05 00:12:28 kernel: intel_ish_ipc 0000:00:12.0: ISH loader: cmd 2 failed 10
And lines in yellow after that.

Comment 4 Justin M. Forbes 2025-10-06 17:56:14 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.