Bug 217183
Summary: | AR9462/ath9k: running wifi scan freezes the laptop | ||
---|---|---|---|
Product: | Drivers | Reporter: | primalmotion (primalmotion) |
Component: | network-wireless | Assignee: | drivers_network-wireless (drivers_network-wireless) |
Status: | NEW --- | ||
Severity: | normal | CC: | kvalo, malocascio, toke |
Priority: | P1 | ||
Hardware: | Intel | ||
OS: | Linux | ||
Kernel Version: | >= 6.2.1 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: | journalctl -k output on kernel 6.2.6 |
Description
primalmotion
2023-03-12 19:27:05 UTC
Can you do a git bisect to find the commit which broke this? Also setting up a netconsole to catch the logs before the crash is nice, but you need ethernet for that. I did more tests playing with the driver parameters. What seems to cause the freeze is enabling the option btcoex_enable=1. Without this option set, scanning works as expected. Does 6.1 work regardless of the value of the btcoex_enable parameter? In fact, nothing has really changed *at all* in the driver between those two versions apart from compile fixes. So that suggest this is a mac80211-induced regression; perhaps the same underlying issue as https://bugzilla.kernel.org/show_bug.cgi?id=217119 ? Yes, it does work with btcoex_enable on 6.1 Hmm, okay, don't really see any obvious connection here, then. Not sure we can get any closer without a bisect and/or a kernel log when the crash happens :( I've been having the same issue on Arch Linux. The 6.1.9 kernel works fine, but kernels 6.2 and above are unstable. The system isn't always totally unusable, though, so I was able to get the output of `journalctl -k`. I have attached it here. The system is an Acer C720 with an Atheros AR9462 wireless interface. Created attachment 303981 [details]
journalctl -k output on kernel 6.2.6
Ah! That stack trace did indeed narrow it down, and I'm pretty sure I see the change that caused this. Sent a fix, here: https://lore.kernel.org/r/20230413214118.153781-1-toke@toke.dk I confirm this patch fixes my issue! Thanks! Great, thank you for testing! |