Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 2072785

Summary: Bug in mt7921e causes kernel crash on reboot (not on cold boot)
Product: [Fedora] Fedora Reporter: Thomas M Steenholdt <tmus>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 36CC: acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, hpa, jarodwilson, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: kernel-5.17.2-300.fc36 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-11 03:34:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Photo of kernel crash none

Description Thomas M Steenholdt 2022-04-07 00:16:29 UTC 
Created attachment 1871173 [details]
Photo of kernel crash

1. Please describe the problem:
I get a kernel crash in mt7921e on reboot (not cold boot). This happens on the installed system as well as when rebooting to the installer, or rebooting after installation.

2. What is the Version-Release number of the kernel:
kernel-5.17.1-300.fc36.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 :
Don't know for sure, but a similar report exist for Fedora 35

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
On a system with mt7921e wireless card (such as ThinkPad P14s ADM gen2), reboot fedora.

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``:
No. The problem appears to be fixed in 5.18-rc1. Tested with kernel-5.18.0-0.rc1.18.vanilla.1.fc36.x86_64 from the vanilla kernel mainline repo.

Upstream fix appears to be this one: https://github.com/torvalds/linux/commit/602cc0c9618a819ab00ea3c9400742a0ca318380

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.
I have no logs showing the error but will include a photo instead
Comment 1 Thomas M Steenholdt 2022-04-07 00:19:59 UTC 
See Bug #2072000 for similar F35 bug
Comment 2 Fedora Update System 2022-04-08 17:48:30 UTC 
FEDORA-2022-af492757d9 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-af492757d9
Comment 3 Fedora Update System 2022-04-08 18:57:55 UTC 
FEDORA-2022-af492757d9 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-af492757d9`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-af492757d9

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Thomas M Steenholdt 2022-04-08 21:51:55 UTC 
Appears to be resolved in kernel-5.17.2-300.fc36.x86_64
Comment 5 Fedora Update System 2022-04-11 03:34:07 UTC 
FEDORA-2022-af492757d9 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.