Skip to contentSkip to conversation

ath11k: QCA6390 support on Linux

DISCUSSION Kalle Valo 2 participants 7 messages Sep 14, 2020 – Nov 6, 2020 Qualcomm Atheros ATH11K wireless driver

lore
Share & tools
lore

Kalle Valo

author
#0 lore raw

Hi,

some of the Dell XPS 15 9500 models have QCA6390 Wi-Fi 6 device. ath11k will be the driver to support QCA6390 and the plan is that Linux v5.10 (most likely released end of December) will be the first release to support it.

But as everything is not ready yet I recommend people to test ath11k-qca6390-bringup branch, and specifically tag ath11k-qca6390-bringup-202008181507. Below are instructions how to install kernel and firmware.

Do note that this is still experimental, there will be bugs but at least it should be possible to connect to an AP and have connectivity.

Please send all questions, comments and bug reports to [email protected] list. I do not have time to reply to private email. I have Bcced people who have contacted me privately.

Kalle

# clone kernel
git clone -b ath11k-qca6390-bringup-202008181507 https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git

# Tag ath11k-qca6390-bringup-202008181507 uses v5.9-rc1 as the baseline

# which has a regression in nvme subsystem, so this nvme patch might be
# needed as well:
# http://git.infradead.org/nvme.git/commitdiff/286155561ecd13b6c85a78eaf2880d3baea03b9e
# clone firmware
git clone https://github.com/kvalo/ath11k-firmware.git

# Ensure below options are selected in the kernel
cd ath
make menuconfig
--> Select Device drivers
--> Network device support
--> Wireless LAN
--> Enable as below
<M> Qualcomm Technologies 11ax chipset support
<M> Atheros ath11k PCI support
[*] QCA ath11k debugging
[*] QCA ath11k debugfs support
[*] ath11k tracing support
[*] QCA ath11k spectral scan support

# Build and install the kernel and kernel modules

# Install firmware
cd ../ath11k-firmware
sudo mkdir -p /lib/firmware/ath11k/QCA6390/hw2.0/
sudo cp QCA6390/hw2.0/WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1/*.bin /lib/firmware/ath11k/QCA6390/hw2.0/ sudo cp QCA6390/hw2.0/WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1/bdwlan.e04 /lib/firmware/ath11k/QCA6390/hw2.0/board.bin

Signature · 6 lines
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath11k
author
#1 lore raw
Quoted 10 lines · Kalle Valo

some of the Dell XPS 15 9500 models have QCA6390 Wi-Fi 6 device. ath11k will be the driver to support QCA6390 and the plan is that Linux v5.10 (most likely released end of December) will be the first release to support it.

But as everything is not ready yet I recommend people to test ath11k-qca6390-bringup branch, and specifically tag ath11k-qca6390-bringup-202008181507. Below are instructions how to install kernel and firmware.

Quoted 6 lines

Do note that this is still experimental, there will be bugs but at least it should be possible to connect to an AP and have connectivity.

Please send all questions, comments and bug reports to [email protected] list. I do not have time to reply to private email. I have Bcced people who have contacted me privately.

Some updates:

* QCA6390 support is now in v5.10-rc2

* pull request to linux-firmware sent, not yet pulled

* board-2.bin should be now used instead of board.bin

* there was some reorganisation in ath11k-firmware

Here are updated instructions on how to test ath11k:

# clone kernel
git clone -b v5.10-rc2 git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
# clone firmware
git clone https://github.com/kvalo/ath11k-firmware.git

# Ensure below options are selected in the kernel
cd linux
make menuconfig
--> Select Device drivers
--> Network device support
--> Wireless LAN
--> Enable as below
<M> Qualcomm Technologies 11ax chipset support
<M> Atheros ath11k PCI support
[*] QCA ath11k debugging
[*] QCA ath11k debugfs support
[*] ath11k tracing support
[*] QCA ath11k spectral scan support

# Build and install the kernel and kernel modules

# Install firmware
cd ../ath11k-firmware
sudo mkdir -p /lib/firmware/ath11k/QCA6390/hw2.0/
sudo cp QCA6390/hw2.0/1.0.1/WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1/*.bin /lib/firmware/ath11k/QCA6390/hw2.0/ sudo cp QCA6390/hw2.0/board-2.bin /lib/firmware/ath11k/QCA6390/hw2.0/

Signature · 8 lines
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath11k
#2 lore raw

Hi

I've tried it out and this time it did not work for me. (Previous instructions with ath11k-qca6390-bringup-202008181507 did bring it up.)

My laptop is a Dell XPS 15" with Killer Wi-fi 6 AX500-DBS (2x2) (QCA6390)

Output from dmesg:

sudo dmesg | grep ath11k

[    7.450993] ath11k_pci 0000:6c:00.0: WARNING: ath11k PCI support is
experimental!
[    7.451067] ath11k_pci 0000:6c:00.0: BAR 0: assigned [mem
0xb4200000-0xb42fffff 64bit]
[    7.451082] ath11k_pci 0000:6c:00.0: enabling device (0000 -> 0002)
[    7.955819] ath11k_pci 0000:6c:00.0: Respond mem req failed,
result: 1, err: 0
[    7.955821] ath11k_pci 0000:6c:00.0: qmi failed to respond fw mem req:-22
[    8.004127] ath11k_pci 0000:6c:00.0: chip_id 0x0 chip_family 0xb
board_id 0xff soc_id 0xffffffff
[    8.004128] ath11k_pci 0000:6c:00.0: fw_version 0x101c06cc
fw_build_timestamp 2020-06-24 19:50 fw_build_id
[   10.081910] ath11k_pci 0000:6c:00.0 wlp108s0: renamed from wlan0
[   13.346532] ath11k_pci 0000:6c:00.0: wmi command 20488 timeout
[   13.346533] ath11k_pci 0000:6c:00.0: failed to send WMI_VDEV_SET_PARAM_CMDID
[   13.346534] ath11k_pci 0000:6c:00.0: failed to set vdev 0 tx encap mode: -11
[   16.418519] ath11k_pci 0000:6c:00.0: wmi command 20488 timeout
[   16.418520] ath11k_pci 0000:6c:00.0: failed to send WMI_VDEV_SET_PARAM_CMDID
[   16.418521] ath11k_pci 0000:6c:00.0: failed to set vdev 0 chainmask
0x3, nss 2 :-11
[   19.490526] ath11k_pci 0000:6c:00.0: wmi command 20482 timeout
[   19.490527] ath11k_pci 0000:6c:00.0: failed to submit WMI_VDEV_DELETE_CMDID
[   22.818765] ath11k_pci 0000:6c:00.0: wmi command 16387 timeout
[   22.818767] ath11k_pci 0000:6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[   22.818769] ath11k_pci 0000:6c:00.0: failed to enable PMF QOS: (-11
[   25.890491] ath11k_pci 0000:6c:00.0: wmi command 16387 timeout
[   25.890493] ath11k_pci 0000:6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[   25.890494] ath11k_pci 0000:6c:00.0: failed to enable PMF QOS: (-11
[   38.178527] ath11k_pci 0000:6c:00.0: wmi command 16387 timeout
[   38.178529] ath11k_pci 0000:6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[   38.178531] ath11k_pci 0000:6c:00.0: failed to enable PMF QOS: (-11
[   41.250526] ath11k_pci 0000:6c:00.0: wmi command 16387 timeout

Please let me know if I can provide anything more.

Quoted 69 lines · Kalle Valo
Quoted 10 lines · Kalle Valo

some of the Dell XPS 15 9500 models have QCA6390 Wi-Fi 6 device. ath11k will be the driver to support QCA6390 and the plan is that Linux v5.10 (most likely released end of December) will be the first release to support it.

But as everything is not ready yet I recommend people to test ath11k-qca6390-bringup branch, and specifically tag ath11k-qca6390-bringup-202008181507. Below are instructions how to install kernel and firmware.

Quoted 6 lines

Do note that this is still experimental, there will be bugs but at least it should be possible to connect to an AP and have connectivity.

Please send all questions, comments and bug reports to [email protected] list. I do not have time to reply to private email. I have Bcced people who have contacted me privately.

Some updates:

* QCA6390 support is now in v5.10-rc2

* pull request to linux-firmware sent, not yet pulled

* board-2.bin should be now used instead of board.bin

* there was some reorganisation in ath11k-firmware

Here are updated instructions on how to test ath11k:

# clone kernel
git clone -b v5.10-rc2 git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
# clone firmware
git clone https://github.com/kvalo/ath11k-firmware.git

# Ensure below options are selected in the kernel
cd linux
make menuconfig
--> Select Device drivers
--> Network device support
--> Wireless LAN
--> Enable as below
<M> Qualcomm Technologies 11ax chipset support
<M> Atheros ath11k PCI support
[*] QCA ath11k debugging
[*] QCA ath11k debugfs support
[*] ath11k tracing support
[*] QCA ath11k spectral scan support

# Build and install the kernel and kernel modules

# Install firmware
cd ../ath11k-firmware
sudo mkdir -p /lib/firmware/ath11k/QCA6390/hw2.0/
sudo cp QCA6390/hw2.0/1.0.1/WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1/*.bin /lib/firmware/ath11k/QCA6390/hw2.0/ sudo cp QCA6390/hw2.0/board-2.bin /lib/firmware/ath11k/QCA6390/hw2.0/

--
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

--
ath11k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath11k

Signature · 3 lines
ath11k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath11k
author
#3 lore raw
Quoted 42 lines · Kenny Johansson

I've tried it out and this time it did not work for me. (Previous instructions with ath11k-qca6390-bringup-202008181507 did bring it up.)

My laptop is a Dell XPS 15" with Killer Wi-fi 6 AX500-DBS (2x2) (QCA6390)

Output from dmesg:

sudo dmesg | grep ath11k

[    7.450993] ath11k_pci 0000:6c:00.0: WARNING: ath11k PCI support is
experimental!
[    7.451067] ath11k_pci 0000:6c:00.0: BAR 0: assigned [mem
0xb4200000-0xb42fffff 64bit]
[    7.451082] ath11k_pci 0000:6c:00.0: enabling device (0000 -> 0002)
[    7.955819] ath11k_pci 0000:6c:00.0: Respond mem req failed,
result: 1, err: 0
[    7.955821] ath11k_pci 0000:6c:00.0: qmi failed to respond fw mem req:-22
[    8.004127] ath11k_pci 0000:6c:00.0: chip_id 0x0 chip_family 0xb
board_id 0xff soc_id 0xffffffff
[    8.004128] ath11k_pci 0000:6c:00.0: fw_version 0x101c06cc
fw_build_timestamp 2020-06-24 19:50 fw_build_id
[   10.081910] ath11k_pci 0000:6c:00.0 wlp108s0: renamed from wlan0
[   13.346532] ath11k_pci 0000:6c:00.0: wmi command 20488 timeout
[   13.346533] ath11k_pci 0000:6c:00.0: failed to send WMI_VDEV_SET_PARAM_CMDID
[   13.346534] ath11k_pci 0000:6c:00.0: failed to set vdev 0 tx encap mode: -11
[   16.418519] ath11k_pci 0000:6c:00.0: wmi command 20488 timeout
[   16.418520] ath11k_pci 0000:6c:00.0: failed to send WMI_VDEV_SET_PARAM_CMDID
[   16.418521] ath11k_pci 0000:6c:00.0: failed to set vdev 0 chainmask
0x3, nss 2 :-11
[   19.490526] ath11k_pci 0000:6c:00.0: wmi command 20482 timeout
[   19.490527] ath11k_pci 0000:6c:00.0: failed to submit WMI_VDEV_DELETE_CMDID
[   22.818765] ath11k_pci 0000:6c:00.0: wmi command 16387 timeout
[   22.818767] ath11k_pci 0000:6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[   22.818769] ath11k_pci 0000:6c:00.0: failed to enable PMF QOS: (-11
[   25.890491] ath11k_pci 0000:6c:00.0: wmi command 16387 timeout
[   25.890493] ath11k_pci 0000:6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[   25.890494] ath11k_pci 0000:6c:00.0: failed to enable PMF QOS: (-11
[   38.178527] ath11k_pci 0000:6c:00.0: wmi command 16387 timeout
[   38.178529] ath11k_pci 0000:6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[   38.178531] ath11k_pci 0000:6c:00.0: failed to enable PMF QOS: (-11
[   41.250526] ath11k_pci 0000:6c:00.0: wmi command 16387 timeout
Quoted 1 line

Please let me know if I can provide anything more.

Hmm, this is a new problem, never seen it before. Can you provide output from 'md5sum /lib/firmware/ath11k/QCA6390/hw2.0/*'? I want to check there's no corruption in firmware files. They should be:

a101dc90f8e876f39383b60c9da64ec4  /lib/firmware/ath11k/QCA6390/hw2.0/amss.bin
4c0781f659d2b7d6bef10a2e3d457728  /lib/firmware/ath11k/QCA6390/hw2.0/board-2.bin
d4c912a3501a3694a3f460d13de06d28  /lib/firmware/ath11k/QCA6390/hw2.0/m3.bin

First you could try reverting commit 7fef431be9c9 ("mm/page_alloc: place pages to tail in __free_pages_core()"), as it helped with Pavel's problem. Though his symptoms were different so I'm not optimistic but it's still a good idea to test it.

If that doesn't help, the next best thing would be try to pinpoint where this got broken by testing these three commits:

fd5ad4d1e980 wcn36xx: Advertise beacon filtering support in bmps 3650b228f83a Linux 5.10-rc1
3cea11cd5e3b Linux 5.10-rc2

Commit fd5ad4d1e980 is based on v5.9-rc6 so try that first.

In these three commits ath11k is practically identical, the only change is a small bugfix in commit 8431350eee2e ("ath11k: Fix memory leak on error path"). For me QCA6390 works on all these commits, I don't know why it's failing for you.

Signature · 8 lines
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath11k
#4 lore raw

Short story:
* Firmware matches
* Reverting 7fef431be9c9 does not work
* fd5ad4d1e980 works
* 3650b228f83a does not work

Details:

Firmware matches:
~/qca$ md5sum /lib/firmware/ath11k/QCA6390/hw2.0/*

a101dc90f8e876f39383b60c9da64ec4  /lib/firmware/ath11k/QCA6390/hw2.0/amss.bin
4c0781f659d2b7d6bef10a2e3d457728  /lib/firmware/ath11k/QCA6390/hw2.0/board-2.bin
d4c912a3501a3694a3f460d13de06d28  /lib/firmware/ath11k/QCA6390/hw2.0/m3.bin

------

I tried reverting 7fef431be9c9, it did not work, but showed a slightly different error

[    7.618202] ath11k_pci 0000:6c:00.0: WARNING: ath11k PCI support is
experimental!
[    7.618411] ath11k_pci 0000:6c:00.0: BAR 0: assigned [mem
0xb4200000-0xb42fffff 64bit]
[    7.618424] ath11k_pci 0000:6c:00.0: enabling device (0000 -> 0002)
[    8.094576] ath11k_pci 0000:6c:00.0: Respond mem req failed,
result: 1, err: 0
[    8.094578] ath11k_pci 0000:6c:00.0: qmi failed to respond fw mem req:-22
[    8.105426] ath11k_pci 0000:6c:00.0: chip_id 0x0 chip_family 0xb
board_id 0xff soc_id 0xffffffff
[    8.105428] ath11k_pci 0000:6c:00.0: fw_version 0x101c06cc
fw_build_timestamp 2020-06-24 19:50 fw_build_id
[   13.342271] ath11k_pci 0000:6c:00.0: failed to receive wmi unified
ready event: -110
[   13.343250] ath11k_pci 0000:6c:00.0: qmi failed to send mode
request, mode: 4, err = -5
[   13.343252] ath11k_pci 0000:6c:00.0: qmi failed to send wlan mode off
[   13.343253] ath11k_pci 0000:6c:00.0: failed to start core: -110

------

The commit 3650b228f83a worked

[    7.452884] ath11k_pci 0000:6c:00.0: WARNING: ath11k PCI support is
experimental!
[    7.452926] ath11k_pci 0000:6c:00.0: BAR 0: assigned [mem
0xb4200000-0xb42fffff 64bit]
[    7.452939] ath11k_pci 0000:6c:00.0: enabling device (0000 -> 0002)
[    7.941932] ath11k_pci 0000:6c:00.0: Respond mem req failed,
result: 1, err: 0
[    7.941933] ath11k_pci 0000:6c:00.0: qmi failed to respond fw mem req:-22
[    7.952897] ath11k_pci 0000:6c:00.0: chip_id 0x0 chip_family 0xb
board_id 0xff soc_id 0xffffffff
[    7.952897] ath11k_pci 0000:6c:00.0: fw_version 0x101c06cc
fw_build_timestamp 2020-06-24 19:50 fw_build_id
[    8.156172] ath11k_pci 0000:6c:00.0 wlp108s0: renamed from wlan0

------

The commit 3650b228f83a does not work

[    7.390729] ath11k_pci 0000:6c:00.0: WARNING: ath11k PCI support is
experimental!
[    7.390773] ath11k_pci 0000:6c:00.0: BAR 0: assigned [mem
0xb4200000-0xb42fffff 64bit]
[    7.390804] ath11k_pci 0000:6c:00.0: enabling device (0000 -> 0002)
[    7.861912] ath11k_pci 0000:6c:00.0: Respond mem req failed,
result: 1, err: 0
[    7.861914] ath11k_pci 0000:6c:00.0: qmi failed to respond fw mem req:-22
[    7.872416] ath11k_pci 0000:6c:00.0: chip_id 0x0 chip_family 0xb
board_id 0xff soc_id 0xffffffff
[    7.872418] ath11k_pci 0000:6c:00.0: fw_version 0x101c06cc
fw_build_timestamp 2020-06-24 19:50 fw_build_id
[    8.072605] ath11k_pci 0000:6c:00.0 wlp108s0: renamed from wlan0
[   11.298562] ath11k_pci 0000:6c:00.0: wmi command 20488 timeout
[   11.298563] ath11k_pci 0000:6c:00.0: failed to send WMI_VDEV_SET_PARAM_CMDID
[   11.298565] ath11k_pci 0000:6c:00.0: failed to set vdev 0 tx encap mode: -11
[   14.370799] ath11k_pci 0000:6c:00.0: wmi command 20488 timeout
[   14.370801] ath11k_pci 0000:6c:00.0: failed to send WMI_VDEV_SET_PARAM_CMDID
[   14.370803] ath11k_pci 0000:6c:00.0: failed to set vdev 0 chainmask
0x3, nss 2 :-11
[   17.442773] ath11k_pci 0000:6c:00.0: wmi command 20482 timeout
[   17.442774] ath11k_pci 0000:6c:00.0: failed to submit WMI_VDEV_DELETE_CMDID
[   20.514613] ath11k_pci 0000:6c:00.0: wmi command 16387 timeout
[   20.514615] ath11k_pci 0000:6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[   20.514618] ath11k_pci 0000:6c:00.0: failed to enable PMF QOS: (-11
[   23.586522] ath11k_pci 0000:6c:00.0: wmi command 16387 timeout

I will try to use fd5ad4d1e980 a bit more to make sure it is not something intermittent, though I suspect not as the bringup-branch seemed to work consistently, while the latest seems consistently broken for me.

Quoted 78 lines · Kalle Valo
Quoted 42 lines · Kenny Johansson

I've tried it out and this time it did not work for me. (Previous instructions with ath11k-qca6390-bringup-202008181507 did bring it up.)

My laptop is a Dell XPS 15" with Killer Wi-fi 6 AX500-DBS (2x2) (QCA6390)

Output from dmesg:

sudo dmesg | grep ath11k

[    7.450993] ath11k_pci 0000:6c:00.0: WARNING: ath11k PCI support is
experimental!
[    7.451067] ath11k_pci 0000:6c:00.0: BAR 0: assigned [mem
0xb4200000-0xb42fffff 64bit]
[    7.451082] ath11k_pci 0000:6c:00.0: enabling device (0000 -> 0002)
[    7.955819] ath11k_pci 0000:6c:00.0: Respond mem req failed,
result: 1, err: 0
[    7.955821] ath11k_pci 0000:6c:00.0: qmi failed to respond fw mem req:-22
[    8.004127] ath11k_pci 0000:6c:00.0: chip_id 0x0 chip_family 0xb
board_id 0xff soc_id 0xffffffff
[    8.004128] ath11k_pci 0000:6c:00.0: fw_version 0x101c06cc
fw_build_timestamp 2020-06-24 19:50 fw_build_id
[   10.081910] ath11k_pci 0000:6c:00.0 wlp108s0: renamed from wlan0
[   13.346532] ath11k_pci 0000:6c:00.0: wmi command 20488 timeout
[   13.346533] ath11k_pci 0000:6c:00.0: failed to send WMI_VDEV_SET_PARAM_CMDID
[   13.346534] ath11k_pci 0000:6c:00.0: failed to set vdev 0 tx encap mode: -11
[   16.418519] ath11k_pci 0000:6c:00.0: wmi command 20488 timeout
[   16.418520] ath11k_pci 0000:6c:00.0: failed to send WMI_VDEV_SET_PARAM_CMDID
[   16.418521] ath11k_pci 0000:6c:00.0: failed to set vdev 0 chainmask
0x3, nss 2 :-11
[   19.490526] ath11k_pci 0000:6c:00.0: wmi command 20482 timeout
[   19.490527] ath11k_pci 0000:6c:00.0: failed to submit WMI_VDEV_DELETE_CMDID
[   22.818765] ath11k_pci 0000:6c:00.0: wmi command 16387 timeout
[   22.818767] ath11k_pci 0000:6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[   22.818769] ath11k_pci 0000:6c:00.0: failed to enable PMF QOS: (-11
[   25.890491] ath11k_pci 0000:6c:00.0: wmi command 16387 timeout
[   25.890493] ath11k_pci 0000:6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[   25.890494] ath11k_pci 0000:6c:00.0: failed to enable PMF QOS: (-11
[   38.178527] ath11k_pci 0000:6c:00.0: wmi command 16387 timeout
[   38.178529] ath11k_pci 0000:6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[   38.178531] ath11k_pci 0000:6c:00.0: failed to enable PMF QOS: (-11
[   41.250526] ath11k_pci 0000:6c:00.0: wmi command 16387 timeout
Quoted 1 line

Please let me know if I can provide anything more.

Hmm, this is a new problem, never seen it before. Can you provide output from 'md5sum /lib/firmware/ath11k/QCA6390/hw2.0/*'? I want to check there's no corruption in firmware files. They should be:

a101dc90f8e876f39383b60c9da64ec4  /lib/firmware/ath11k/QCA6390/hw2.0/amss.bin
4c0781f659d2b7d6bef10a2e3d457728  /lib/firmware/ath11k/QCA6390/hw2.0/board-2.bin
d4c912a3501a3694a3f460d13de06d28  /lib/firmware/ath11k/QCA6390/hw2.0/m3.bin

First you could try reverting commit 7fef431be9c9 ("mm/page_alloc: place pages to tail in __free_pages_core()"), as it helped with Pavel's problem. Though his symptoms were different so I'm not optimistic but it's still a good idea to test it.

If that doesn't help, the next best thing would be try to pinpoint where this got broken by testing these three commits:

fd5ad4d1e980 wcn36xx: Advertise beacon filtering support in bmps 3650b228f83a Linux 5.10-rc1
3cea11cd5e3b Linux 5.10-rc2

Commit fd5ad4d1e980 is based on v5.9-rc6 so try that first.

In these three commits ath11k is practically identical, the only change is a small bugfix in commit 8431350eee2e ("ath11k: Fix memory leak on error path"). For me QCA6390 works on all these commits, I don't know why it's failing for you.

--
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Signature · 3 lines
ath11k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath11k
author
#5 lore raw
Quoted 5 lines · Kenny Johansson

Short story:
* Firmware matches
* Reverting 7fef431be9c9 does not work
* fd5ad4d1e980 works
* 3650b228f83a does not work

An excellent summary, makes it a lot easier to understand what's happening :)

Quoted 7 lines

Details:

Firmware matches:
~/qca$ md5sum /lib/firmware/ath11k/QCA6390/hw2.0/*

a101dc90f8e876f39383b60c9da64ec4  /lib/firmware/ath11k/QCA6390/hw2.0/amss.bin
4c0781f659d2b7d6bef10a2e3d457728  /lib/firmware/ath11k/QCA6390/hw2.0/board-2.bin
d4c912a3501a3694a3f460d13de06d28  /lib/firmware/ath11k/QCA6390/hw2.0/m3.bin

Good, we can rule out firmware corruption then.

Quoted 15 lines

The commit 3650b228f83a worked

[    7.452884] ath11k_pci 0000:6c:00.0: WARNING: ath11k PCI support is
experimental!
[    7.452926] ath11k_pci 0000:6c:00.0: BAR 0: assigned [mem
0xb4200000-0xb42fffff 64bit]
[    7.452939] ath11k_pci 0000:6c:00.0: enabling device (0000 -> 0002)
[    7.941932] ath11k_pci 0000:6c:00.0: Respond mem req failed,
result: 1, err: 0
[    7.941933] ath11k_pci 0000:6c:00.0: qmi failed to respond fw mem req:-22
[    7.952897] ath11k_pci 0000:6c:00.0: chip_id 0x0 chip_family 0xb
board_id 0xff soc_id 0xffffffff
[    7.952897] ath11k_pci 0000:6c:00.0: fw_version 0x101c06cc
fw_build_timestamp 2020-06-24 19:50 fw_build_id
[    8.156172] ath11k_pci 0000:6c:00.0 wlp108s0: renamed from wlan0

I think you have a typo here and you mean that commit fd5ad4d1e980 worked, right? The one which is based on v5.9-rc6:

fd5ad4d1e980 wcn36xx: Advertise beacon filtering support in bmps

Quoted 4 lines

I will try to use fd5ad4d1e980 a bit more to make sure it is not something intermittent, though I suspect not as the bringup-branch seemed to work consistently, while the latest seems consistently broken for me.

Yes, it's a good idea to rule out all intermittent issues. This is a weird problem and any randomness might confuse the testing results.

Even if your symptoms are different I suspect this is related to Pavel's problem, where the number one suspect is high physical addresses are causing problems:

http://lists.infradead.org/pipermail/ath11k/2020-November/000556.html

Signature · 8 lines
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath11k
#6 lore raw

An update here,
* 3650b228f83a 5.10-rc1 works intermittently, I would say less than 50%, but more than 25% of times.
* fd5ad4d1e980 worked consistently for at least 10 boots.

I will follow that discussion, it sounds like a good lead.

(You correctly spotted the commit typo in my previous email.)

Quoted 61 lines · Kalle Valo
Quoted 5 lines · Kenny Johansson

Short story:
* Firmware matches
* Reverting 7fef431be9c9 does not work
* fd5ad4d1e980 works
* 3650b228f83a does not work

An excellent summary, makes it a lot easier to understand what's happening :)

Quoted 7 lines

Details:

Firmware matches:
~/qca$ md5sum /lib/firmware/ath11k/QCA6390/hw2.0/*

a101dc90f8e876f39383b60c9da64ec4  /lib/firmware/ath11k/QCA6390/hw2.0/amss.bin
4c0781f659d2b7d6bef10a2e3d457728  /lib/firmware/ath11k/QCA6390/hw2.0/board-2.bin
d4c912a3501a3694a3f460d13de06d28  /lib/firmware/ath11k/QCA6390/hw2.0/m3.bin

Good, we can rule out firmware corruption then.

Quoted 15 lines

The commit 3650b228f83a worked

[    7.452884] ath11k_pci 0000:6c:00.0: WARNING: ath11k PCI support is
experimental!
[    7.452926] ath11k_pci 0000:6c:00.0: BAR 0: assigned [mem
0xb4200000-0xb42fffff 64bit]
[    7.452939] ath11k_pci 0000:6c:00.0: enabling device (0000 -> 0002)
[    7.941932] ath11k_pci 0000:6c:00.0: Respond mem req failed,
result: 1, err: 0
[    7.941933] ath11k_pci 0000:6c:00.0: qmi failed to respond fw mem req:-22
[    7.952897] ath11k_pci 0000:6c:00.0: chip_id 0x0 chip_family 0xb
board_id 0xff soc_id 0xffffffff
[    7.952897] ath11k_pci 0000:6c:00.0: fw_version 0x101c06cc
fw_build_timestamp 2020-06-24 19:50 fw_build_id
[    8.156172] ath11k_pci 0000:6c:00.0 wlp108s0: renamed from wlan0

I think you have a typo here and you mean that commit fd5ad4d1e980 worked, right? The one which is based on v5.9-rc6:

fd5ad4d1e980 wcn36xx: Advertise beacon filtering support in bmps

Quoted 4 lines

I will try to use fd5ad4d1e980 a bit more to make sure it is not something intermittent, though I suspect not as the bringup-branch seemed to work consistently, while the latest seems consistently broken for me.

Yes, it's a good idea to rule out all intermittent issues. This is a weird problem and any randomness might confuse the testing results.

Even if your symptoms are different I suspect this is related to Pavel's problem, where the number one suspect is high physical addresses are causing problems:

http://lists.infradead.org/pipermail/ath11k/2020-November/000556.html

--
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Signature · 3 lines
ath11k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath11k