Re: Compex WLE200NX: regdomain sanitized regression

[Thorsten Leemhuis <regressions@leemhuis.info>]

Hi, this is your Linux kernel regression tracker speaking.

Thanks for the report. CCing regression mailing list, which should be in
the loop for all regressions, as explained here:
https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html

Also adding the ath10k maintainer and the author of the likely culprit
of this regressions to the recipients.

On 27.11.21 09:17, Sebastian Bachmann wrote:
> 
> I recently upgraded my Debian based AP from buster to bullseye, just to
> find out that hostapd does not work any more, because all 5GHz channels
> are marked as No-IR. This regression was already discussed on this ML
> here: https://www.mail-archive.com/ath10k@lists.infradead.org/msg12018.html
> and there is also an entry in Debian's bug tracker for the same issue:
> https://bugs.debian.org/959821

TWIMC: To be sure this issue doesn't fall through the cracks unnoticed
again, I'm adding it to regzbot, my Linux kernel regression tracking bot:

#regzbot ^introduced 2dc016599cfa9672a147528ca26d70c3654a5423
#regzbot title net: wireless: ath10k: 5GHz channels are marked as No-IR
#regzbot monitor
https://lore.kernel.org/ath10k/5971a327-d11a-35e6-8295-8dfb8ae3a434@yandex.ru/
#regzbot monitor
https://lore.kernel.org/linux-wireless/20200730124923.271429-1-alsi@bang-olufsen.dk/
#regzbot monitor
https://lore.kernel.org/ath10k/19e636c1-fdbe-7222-a055-d668e4617070@gmx.de/
#regzbot monitor
https://lore.kernel.org/ath10k/20201022172113.GA1367233@capeo.gueux.org/
#regzbot link: https://bugs.debian.org/959821
#regzbot link: https://bbs.archlinux.org/viewtopic.php?id=254535
#regzbot link:
https://lore.kernel.org/ath10k/CA+ASDXNNfG3-ra8C2ou457J=Vj5eE83VCXgGsFPQQOixTcu7YA@mail.gmail.com/
#regzbot ignore-activity

Reminder for developers: when fixing this, please include a 'Link:' tag
pointing to the report (the parent of this mail), as explained here:
Documentation/process/submitting-patches.rst

> I have a slightly different card (branded Compex WLE200NX):
> 04:00.0 Network controller: Qualcomm Atheros AR928X Wireless Network
> Adapter (PCI-Express) (rev 01)
>         Subsystem: Qualcomm Atheros AR928X Wireless Network Adapter
> (PCI-Express)
>         Kernel driver in use: ath9k
>         Kernel modules: ath9k
> 
> But as you can see, also the EEPROM gets sanitized:
> [   15.461755] ath9k 0000:04:00.0: enabling device (0000 -> 0002)
> [   15.911600] ath: EEPROM regdomain sanitized
> [   15.911612] ath: EEPROM regdomain: 0x64
> [   15.911615] ath: EEPROM indicates we should expect a direct regpair map
> [   15.911625] ath: Country alpha2 being used: 00
> [   15.911628] ath: Regpair used: 0x64
> 
> I read in the other thread, that this is a regression, but the actual
> commit causing it was never reverted.

:-/

> I tried to search for newer messages explaining the issue, however as
> far as I can tell, the thread ends in June 2020 with no solution available.
> 
> Therefore, I kindly want to ask if there is any workaround available to
> re-enable 5GHz channels in AP mode for my card? (expect sticking to a
> pre-5.6 kernel or manually patching and recompiling ath)

Ciao, Thorsten, your Linux kernel regression tracker.

P.S.: As a Linux kernel regression tracker I'm getting a lot of reports
on my table. I can only look briefly into most of them. Unfortunately
therefore I sometimes will get things wrong or miss something important.
I hope that's not the case here; if you think it is, don't hesitate to
tell me about it in a public reply. That's in everyone's interest, as
what I wrote above might be misleading to everyone reading this; any
suggestion I gave they thus might sent someone reading this down the
wrong rabbit hole, which none of us wants.

BTW, I have no personal interest in this issue, which is tracked using
regzbot, my Linux kernel regression tracking bot
(https://linux-regtracking.leemhuis.info/regzbot/). I'm only posting
this mail to get things rolling again and hence don't need to be CC on
all further activities wrt to this regression.

P.P.S.: If you want to know more about regzbot, check out its
web-interface, the getting start guide, and/or the references documentation:

https://linux-regtracking.leemhuis.info/regzbot/
https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md
https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md

The last two documents will explain how you can interact with regzbot
yourself if your want to.

Hint for the reporter: when reporting a regression it's in your interest
to tell #regzbot about it in the report, as that will ensure the
regression gets on the radar of regzbot and the regression tracker.
That's in your interest, as they will make sure the report won't fall
through the cracks unnoticed.

Hint for developers: you normally don't need to care about regzbot, just
fix the issue as you normally would. Just remember to include a 'Link:'
tag to the report in the commit message, as explained in
Documentation/process/submitting-patches.rst
That aspect was recently was made more explicit in commit 1f57bd42b77c:
https://git.kernel.org/linus/1f57bd42b77c

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k