[regression] Bug 217183 - AR9462/ath9k: running wifi scan freezes the laptop

["Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>]

Hi, Thorsten here, the Linux kernel's regression tracker.

I noticed a regression report in bugzilla.kernel.org. As many (most?)
kernel developer don't keep an eye on it, I decided to forward it by
mail. Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=217183 :

>  primalmotion@pm.me 2023-03-12 19:27:05 UTC
> 
> Since 6.2.1 (and onward), running a wifi scan freezes the laptop completely. The screen is frozen, caps lock led is on, and there's nothing left to do but force reboot.
> 
> Step to reproduce:
> 1) iwctl station wlan0 scan
> 
> This works just fine on 6.1.12 and below. 
> This is 100% reproducible. 
> 
> I can't find any relevant log. I tried to collect dmesg and journalctl -k while I was performing the command, but the laptop freezes before I can get anything.
> 
> Card: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
> Driver: ath9k
> 
> module parameters:
> /sys/module/ath9k/parameters/blink 0
> /sys/module/ath9k/parameters/bt_ant_diversity 0
> /sys/module/ath9k/parameters/btcoex_enable 1
> /sys/module/ath9k/parameters/led_active_high -1
> /sys/module/ath9k/parameters/ps_enable 1
> /sys/module/ath9k/parameters/use_chanctx 0
> /sys/module/ath9k/parameters/use_msi 0
> 
> Let me know if you need any additional logs from other places I don't know

See the ticket for more details.


[TLDR for the rest of this mail: I'm adding this report to the list of
tracked Linux kernel regressions; the text you find below is based on a
few templates paragraphs you might have encountered already in similar
form.]

BTW, let me use this mail to also add the report to the list of tracked
regressions to ensure it's doesn't fall through the cracks:

#regzbot introduced: v6.1..v6.2
https://bugzilla.kernel.org/show_bug.cgi?id=217183
#regzbot title: net: wifi: ath9k: wifi scan freezes laptop
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (e.g. the buzgzilla ticket and maybe this mail as well, if
this thread sees some discussion). See page linked in footer for details.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.