Bug 2367697
| Summary: | kernel: wifi: ath12k crashes during sleep for 6.13.12, 6.4.x | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Christopher R. Palmer <crpalmer> | ||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
| Status: | NEW --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 42 | CC: | acaringi, adscvr, airlied, haitham.ghaida, hdegoede, hpa, josef, kernel-maint, linville, masami256, mchehab, mpearson, ptalbert, steved, suraj.ghimire7 | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | --- | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | Type: | --- | |||||||
| 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
Christopher R. Palmer
2025-05-20 23:23:54 UTC
Created attachment 2090954 [details]
Full dmesg.txt from the the 6.14.7 crash, all crashes look similar
Created attachment 2090955 [details]
dmesg ffrom 6.14.6
In case anyone thinks its a regression in 6.14.7, here's the dmesg from a 6.14.6 officially released kernel.
Actually, I'm having a hard time reproducing it with 6.15-rc7. I had something bad happen on the first boot and I (stupidly) assumed it was the same problem and didn't look at the journalctl. Now I've been trying to reproduce it and haven't been able to. (In reply to Christopher R. Palmer from comment #3) > Actually, I'm having a hard time reproducing it with 6.15-rc7. I had > something bad happen on the first boot and I (stupidly) assumed it was the > same problem and didn't look at the journalctl. Now I've been trying to > reproduce it and haven't been able to. Hi Chris, thanks for posting this and letting me know that you are not having these issues with 6.15rc7. I had the same issue for a while now, recently firmware received an update that completely broke the ath12k driver. Downgrading brings me back to this crashing problem that you describe, and upgrading removes Wi-Fi completely, which is actually better that dealing with all these crashes, just using a wifi usb dongle for now. I'm wondering how do you exactly upgrade to 6.15rc7 on fedora (probably dumb question, but I'm no expert) can't seem to find a straightforward guide or documentation on this. FWIW, I did have some problems with 6.15 last night which I didn't look into at all, instead just turning off the laptop and calling it day. To build the kernel, I followed this set of instructions https://docs.fedoraproject.org/en-US/quick-docs/kernel-build-custom/ Specifically, I used the section "Building a Kernel from the Fedora dist-git" and ran "git switch rawhide" to switch to the rawhide (6.15-rc7) branch. Mark Pearson, you linked this commit in another bug and I thought it might apply to this bug. Here's an update on my testing with this commit. The testing is looking promising. The commit is: https://web.git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git/commit/?id=1ab2e9046b4f3b298274ad4cc08ff456d3e4274e I booted the official fc42 6.14.6 and ran sudo iw wlp194s0 scan and then within a second or so I closed the lid of my laptop which caused a NULL pointer exception in: May 22 19:17:49 lambtop kernel: Call Trace: May 22 19:17:49 lambtop kernel: <TASK> May 22 19:17:49 lambtop kernel: cancel_delayed_work_sync+0x5e/0x80 May 22 19:17:49 lambtop kernel: ath12k_mac_remove_link_interface.isra.0+0x26/0x70 [ath12k] May 22 19:17:49 lambtop kernel: ath12k_scan_vdev_clean_work+0x8b/0xd0 [ath12k] May 22 19:17:49 lambtop kernel: cfg80211_wiphy_work+0x11b/0x190 [cfg80211] May 22 19:17:49 lambtop kernel: process_one_work+0x17b/0x340 May 22 19:17:49 lambtop kernel: worker_thread+0x255/0x390 May 22 19:17:49 lambtop kernel: ? __pfx_worker_thread+0x10/0x10 May 22 19:17:49 lambtop kernel: kthread+0xec/0x230 May 22 19:17:49 lambtop kernel: ? __pfx_kthread+0x10/0x10 May 22 19:17:49 lambtop kernel: ret_from_fork+0x31/0x50 May 22 19:17:49 lambtop kernel: ? __pfx_kthread+0x10/0x10 May 22 19:17:49 lambtop kernel: ret_from_fork_asm+0x1a/0x30 May 22 19:17:49 lambtop kernel: </TASK> With my source built 6.14.7 and this commit, I performed the same test (run the command and then within a second or a few I closed the lid of my laptop) and this succeeded 10 times. Each time I was able to wake up the laptop and the WiFi was functional. Previously, I'm not sure I could just close the lid 10 times without encountering a crash and a failure to wake up let alone trying to trigger it with an intentional scan operation. Thanks for the update - reviewing with the Qualcomm engineers. 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. |