Bug 2392523 - Kernel 6.16.3 panics on ASUSTeK PRIME Z690-P WIFI
Summary: Kernel 6.16.3 panics on ASUSTeK PRIME Z690-P WIFI
Keywords:
Status: NEW
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-09-02 09:16 UTC by Barry Scott
Modified: 2025-09-05 17:59 UTC (History)
14 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)
panic image 1 (4.59 MB, image/jpeg)
2025-09-02 09:34 UTC, Barry Scott
no flags Details
panic image 2 (4.68 MB, image/jpeg)
2025-09-02 09:34 UTC, Barry Scott
no flags Details
panic image 3 (3.80 MB, image/jpeg)
2025-09-02 09:35 UTC, Barry Scott
no flags Details
panic image 4 (3.58 MB, image/jpeg)
2025-09-02 09:35 UTC, Barry Scott
no flags Details

Description Barry Scott 2025-09-02 09:16:25 UTC
1. Please describe the problem:
Intermitted panics that prevent boot to user space

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

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 :
Works on kernel-core-6.15.10-200.fc42.x86_64

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Yes, panic happens approx 50% of boots

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``:
Tested with kernel-core-6.17.0-0.rc3.250826gfab1beda7597.32.fc44.x86_64 and have not seen the issue. But only booted 6.17 3 times so far.


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.
No possible as kernel panics.
I have screen shots of panics that may help.


Reproducible: Always

Comment 1 Barry Scott 2025-09-02 09:34:08 UTC
Created attachment 2105569 [details]
panic image 1

Comment 2 Barry Scott 2025-09-02 09:34:33 UTC
Created attachment 2105570 [details]
panic image 2

Comment 3 Barry Scott 2025-09-02 09:35:00 UTC
Created attachment 2105571 [details]
panic image 3

Comment 4 Barry Scott 2025-09-02 09:35:28 UTC
Created attachment 2105572 [details]
panic image 4


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