Bug 2390635 - kernel-6.16.3-200.fc42 crashes during boot
Summary: kernel-6.16.3-200.fc42 crashes during boot
Keywords:
Status: CLOSED EOL
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-08-24 20:44 UTC by Ronald Warsow
Modified: 2026-06-08 18:18 UTC (History)
18 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-06-08 18:18:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
journalctl --no-hostname -k (100.49 KB, text/plain)
2025-08-24 20:46 UTC, Ronald Warsow
no flags Details
defconfig (32.86 KB, text/plain)
2025-08-25 21:42 UTC, Ronald Warsow
no flags Details
dmesg output from kernel 6.16.3-200, showing error similar to original poster's (99.97 KB, text/plain)
2025-08-30 19:54 UTC, Stan King
no flags Details
dmesg output from kernel 6.15.10-200, showing lack of kernel oops (94.34 KB, text/plain)
2025-08-30 19:58 UTC, Stan King
no flags Details

Description Ronald Warsow 2025-08-24 20:44:07 UTC
1. Please describe the problem:
see dmesg.txt (see last third !)

2. What is the Version-Release number of the kernel:
6.16.3-200.fc42.x86_64

3. Did it work previously in Fedora? 
elder kernel 6.15.9-201.fc42 and
homebrewed 6.16.3 are working

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
yes

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

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``. 
attached

Reproducible: Always

Comment 1 Ronald Warsow 2025-08-24 20:46:21 UTC
Created attachment 2104589 [details]
journalctl --no-hostname -k

Comment 2 Justin M. Forbes 2025-08-25 20:19:55 UTC
I am rather curious about your home brewed kernel.  Given the first failure in the existing log, it appears to be a problem stemming from the ASUS WMI driver, and we do not patch that at all.  I would expect a similar failure in your homebrewed kernel.  Might I ask for a quick summary of what is different in your kernel?

Comment 3 Ronald Warsow 2025-08-25 21:41:35 UTC
 no WMI driver failures with homebrewed

I upload my defconfig

(generated with make savedefconfig)

Comment 4 Ronald Warsow 2025-08-25 21:42:35 UTC
Created attachment 2104768 [details]
defconfig

defconfig (from "make savedefconfig")

Comment 5 Stan King 2025-08-30 19:54:44 UTC
Created attachment 2105301 [details]
dmesg output from kernel 6.16.3-200, showing error similar to original poster's

Comment 6 Stan King 2025-08-30 19:58:40 UTC
Created attachment 2105302 [details]
dmesg output from kernel 6.15.10-200, showing lack of kernel oops

(lesson learned: attach files first?)

I decided to piggy-back on this error report because it was so similar to what I've seen starting with 6.16.3-200.  The Oops is immediately preceded by "kernel BUG at lib/list_debug.c:35!" just like with the original poster, and asus_wmi_probe appears in the call trace.  We both have an ASUS motherboard.

Hopefully my use of a standard kernel will make debugging this easier.

I also have the hanging restart, but numerous others have that, too, so that might be a separate problem.

Comment 7 Eduardo 2025-08-31 11:03:59 UTC
I have the same issue on my system. I also have an ASUS motherboard (PRIME Z790-P WIFI) with standard kernel and integrated Intel Graphics (no additional modules). It does not hang every time. Maybe about 40% of the boots, though the kernel error with the ASUS module always shows up.

The system hangs on shutdown and reboot as well (every time). I see other reports about it. They seem to be cause by the same issue though. Both are avoided by blacklisting asus_nb_wmi (#1). Are there any issues that could happen because of blacklisting this module?

Both problems also happen on rawhide (6.17.0-0.rc3.250826gfab1beda7597.32.fc44.x86_64)

#1: https://www.reddit.com/r/Fedora/comments/1n3uwvh/comment/nbmgbvh/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Comment 8 Ronald Warsow 2025-09-01 22:24:23 UTC
thanks @Eduardo

NO crash 
booting kernel-6.16.4-200.fc42 with /etc/modprobe.d/asus-nb-wmi-blacklist.conf

Comment 9 Eduardo 2025-10-05 01:27:42 UTC
Kernel 6.16.9-200.fc42.x86_64 solved the problem for me. I removed the blacklist (depmod + dracut) and the system boots without error and shuts down without hanging.

Comment 10 Fedora Release Engineering 2026-05-06 13:53:32 UTC
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '42'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 42 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 11 Aoife Moloney 2026-06-08 18:18:24 UTC
Fedora Linux 42 entered end-of-life (EOL) status on 2026-05-27.

Fedora Linux 42 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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