Debian Bug report logs - #970679
wireless-regdb: updating wireless-regdb to 2020.04.29-2~bpo10+1 makes AP mode impossible on ath10k wifi card

Reply or subscribe to this bug.

Display info messages

Message #5 received at [email protected] (full text, mbox, reply):

From: Félix Sipma <[email protected]>

To: Debian Bug Tracking System <[email protected]>

Subject: wireless-regdb: updating wireless-regdb to 2020.04.29-2~bpo10+1 makes AP mode impossible on ath10k wifi card

Date: Mon, 21 Sep 2020 13:28:53 +0200

Package: wireless-regdb
Version: 2016.06.10-1
Severity: normal

Hello,

I have an ath10k wireless card, using QCA988X driver in firmware-atheros, which 
worked with wireless-regdb 2016.06.10-1. I tried to update linux-image-amd64 
from 4.19+105+deb10u5 to 5.7.10-1~bpo10+1, which resulted in an updated 
wireless-regdb (2020.04.29-2~bpo10+1). From then, The wifi card got impossible 
to use in 5Ghz AP mode (no frequency available). I tried to boot with 
4.19.0-10-amd64, and the same symptoms remained. Finally, downgrading 
wireless-regdb to 2016.06.10-1 made the wifi functionnal again.

Using firmware-atheros from buster-backports or not made no difference.

Regards,


-- System Information:
Debian Release: 10.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-10-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

wireless-regdb depends on no packages.

wireless-regdb recommends no packages.

Versions of packages wireless-regdb suggests:
ii  crda  3.18-1

-- no debconf information

Message #10 received at [email protected] (full text, mbox, reply):

From: Romain Perier <[email protected]>

To: Félix Sipma <[email protected]>, [email protected]

Subject: Re: Bug#970679: wireless-regdb: updating wireless-regdb to 2020.04.29-2~bpo10+1 makes AP mode impossible on ath10k wifi card

Date: Tue, 6 Oct 2020 18:36:45 +0200

[Message part 1 (text/plain, inline)]

On Mon, Sep 21, 2020 at 01:28:53PM +0200, Félix Sipma wrote:
> Package: wireless-regdb
> Version: 2016.06.10-1
> Severity: normal
> 
> Hello,
> 
> I have an ath10k wireless card, using QCA988X driver in firmware-atheros, which 
> worked with wireless-regdb 2016.06.10-1. I tried to update linux-image-amd64 
> from 4.19+105+deb10u5 to 5.7.10-1~bpo10+1, which resulted in an updated 
> wireless-regdb (2020.04.29-2~bpo10+1). From then, The wifi card got impossible 
> to use in 5Ghz AP mode (no frequency available). I tried to boot with 
> 4.19.0-10-amd64, and the same symptoms remained. Finally, downgrading 
> wireless-regdb to 2016.06.10-1 made the wifi functionnal again.
> 
> Using firmware-atheros from buster-backports or not made no difference.
> 
> Regards,
> 
> 
> -- System Information:
> Debian Release: 10.5
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.19.0-10-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> wireless-regdb depends on no packages.
> 
> wireless-regdb recommends no packages.
> 
> Versions of packages wireless-regdb suggests:
> ii  crda  3.18-1
> 
> -- no debconf information

Hi,

Could you, please, provide the output of 'dmesg' with the faulty kernel and the
faulty wiresless-regdb, it might give us more context and I am wondering if it
is not signing issue (perhaps not, just wondering, as we are now two
maintainers). Typically one dmesg with kernel 5.7.x and wireless-regdb 2020.04.29,
one dmesg with kernel 4.19.x and wireless-regdb 2020.04.29 and one dmesg when it
works, would be perfect.


Thanks,
Romain

[signature.asc (application/pgp-signature, inline)]

Message #15 received at [email protected] (full text, mbox, reply):

From: Félix Sipma <[email protected]>

To: Romain Perier <[email protected]>

Cc: [email protected]

Subject: Re: Bug#970679: wireless-regdb: updating wireless-regdb to 2020.04.29-2~bpo10+1 makes AP mode impossible on ath10k wifi card

Date: Wed, 7 Oct 2020 11:24:38 +0200

[Message part 1 (text/plain, inline)]

Hi Romain,

Thanks for your reply. Here are the logs you asked for. I hope it will 
help diagnosing the issue!

Regards,

-- 
Félix

[log_kernel4.19_wrdb2016.06.10-1.log (text/plain, attachment)]

[log_kernel4.19_wrdb2020.04.29-2.log (text/plain, attachment)]

[log_kernel5.7_wrdb2020.04.29-1.log (text/plain, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #20 received at [email protected] (full text, mbox, reply):

From: Massimo Maggi <[email protected]>

To: [email protected]

Subject: ath10k and kernel >= 5.6

Date: Wed, 14 Oct 2020 23:12:08 +0200

[Message part 1 (text/plain, inline)]

Hi,
I saw the bug that you reported in Debian wireless-regdb:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970679 .
I am aware of a regression in kernel 5.6 (not yet fixed as of 5.9) which
produces the exact symptom you described - impossibility to use AP mode on
any 5GHz channel, due to country/regulatory issues.
However the wireless-regdb package is not directly involved in the issue
I'm talking about (as I understand it), so rebooting into a 4.x series
kernel should immediately fix it (at least, on my Turris Omnia, it does).
Therefore it might or might not be your same issue.
A non-exhaustive list of references:
https://patchwork.kernel.org/project/ath10k/patch/[email protected]/
https://www.mail-archive.com/[email protected]/msg12598.html
https://bbs.archlinux.org/viewtopic.php?id=254535
Culprit commit:
https://github.com/torvalds/linux/commit/2dc016599cfa9672a147528ca26d70c3654a5423

I'm just trying to spare you the many many hours of debugging that I spent
before finding that out :)

Best regards,
Massimo Maggi

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.