* QCA6174 firmware crash
@ 2022-02-19 13:30 Nerijus Baliūnas
2022-02-20 22:32 ` Nerijus Baliūnas
0 siblings, 1 reply; 7+ messages in thread
From: Nerijus Baliūnas @ 2022-02-19 13:30 UTC (permalink / raw)
To: ath10k
Hello,
07:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless
Network Adapter [168c:003e] (rev 20)
Firmware is newest:
# ethtool -i wlp7s0
driver: ath10k_pci
version: 5.16.9-200.fc35.x86_64
firmware-version: SW_RM.1.1.1-00157-QCARMSWPZ-1
expansion-rom-version:.
bus-info: 0000:07:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
# dmesg | grep ath10k
[ 6.698345] ath10k_pci 0000:07:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[ 6.927480] ath10k_pci 0000:07:00.0: qca6174 hw2.1 target 0x05010000
chip_id 0x003405ff sub 11ad:0804
[ 6.928453] ath10k_pci 0000:07:00.0: kconfig debug 0 debugfs 1 tracing 0
dfs 0 testmode 0
[ 6.929729] ath10k_pci 0000:07:00.0: firmware ver
SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5 features ignore-otp,no-4addr-pad crc32
10bf8e08
[ 6.995609] ath10k_pci 0000:07:00.0: board_file api 2 bmi_id N/A crc32
ae2e275a
[ 8.223964] ath10k_pci 0000:07:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp
max-sta 32 raw 0 hwcrypto 1
It crashes every time I try to connect to TP-Link Archer MR600 v2 Firmware
Version:1.5.0 0.9.1 v0001.0 Build 210914 wifi router:
ath10k_pci 0000:07:00.0: firmware crashed! (guid
c1610eff-6185-467f-aba7-26ec9d9b8605)
ath10k_pci 0000:07:00.0: qca6174 hw2.1 target 0x05010000 chip_id 0x003405ff
sub 11ad:0804
ath10k_pci 0000:07:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
ath10k_pci 0000:07:00.0: firmware ver SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5
features ignore-otp,no-4addr-pad crc32 10bf8e08
ath10k_pci 0000:07:00.0: board_file api 2 bmi_id N/A crc32 ae2e275a
ath10k_pci 0000:07:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32 raw
0 hwcrypto 1
ath10k_pci 0000:07:00.0: firmware register dump:
ath10k_pci 0000:07:00.0: [00]: 0x05010000 0x00000000 0x0092E4DC 0x0EB2E199
ath10k_pci 0000:07:00.0: [04]: 0x0092E4DC 0x00060130 0x00000018 0x0041A760
ath10k_pci 0000:07:00.0: [08]: 0x0EB2E185 0x00400000 0x00000000 0x000A5C88
ath10k_pci 0000:07:00.0: [12]: 0x00000009 0x00000000 0x0096C09C 0x0096C0A7
ath10k_pci 0000:07:00.0: [16]: 0x0096BDBC 0x009287BD 0x00000000 0x009287BD
ath10k_pci 0000:07:00.0: [20]: 0x4092E4DC 0x0041A710 0x00000000 0x0F000000
ath10k_pci 0000:07:00.0: [24]: 0x809432A7 0x0041A770 0x0040D45C 0xC092E4DC
ath10k_pci 0000:07:00.0: [28]: 0x80942BC4 0x0041A790 0x0EB2E185 0x00400000
ath10k_pci 0000:07:00.0: [32]: 0x80947BA7 0x0041A7B0 0x004050A8 0x0040E074
ath10k_pci 0000:07:00.0: [36]: 0x809BDECC 0x0041A7D0 0x004050A8 0x0040E074
ath10k_pci 0000:07:00.0: [40]: 0x8099638C 0x0041A7F0 0x004050A8 0x00000000
ath10k_pci 0000:07:00.0: [44]: 0x80992076 0x0041A810 0x00408420 0x0046FFE8
ath10k_pci 0000:07:00.0: [48]: 0x80996BD3 0x0041A830 0x00408420 0x00000000
ath10k_pci 0000:07:00.0: [52]: 0x800B4405 0x0041A850 0x00422318 0x00005002
ath10k_pci 0000:07:00.0: [56]: 0x809A6C34 0x0041A8E0 0x0042932C 0x0042CA44
ath10k_pci 0000:07:00.0: Copy Engine register dump:
ath10k_pci 0000:07:00.0: [00]: 0x00034400 1 1 3 3
ath10k_pci 0000:07:00.0: [01]: 0x00034800 13 13 272 273
ath10k_pci 0000:07:00.0: [02]: 0x00034c00 13 13 76 77
ath10k_pci 0000:07:00.0: [03]: 0x00035000 27 27 28 27
ath10k_pci 0000:07:00.0: [04]: 0x00035400 1629 1629 112 48
ath10k_pci 0000:07:00.0: [05]: 0x00035800 0 0 0 0
ath10k_pci 0000:07:00.0: [06]: 0x00035c00 27 27 27 27
ath10k_pci 0000:07:00.0: [07]: 0x00036000 1 1 1 1
ath10k_pci 0000:07:00.0: failed to create WMI vdev 1: -108
ath10k_pci 0000:07:00.0: firmware crashed! (guid
016cc818-beee-4422-b9dd-fee9fd612a03)
ath10k_pci 0000:07:00.0: qca6174 hw2.1 target 0x05010000 chip_id 0x003405ff
sub 11ad:0804
ath10k_pci 0000:07:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
ath10k_pci 0000:07:00.0: firmware ver SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5
features ignore-otp,no-4addr-pad crc32 10bf8e08
ath10k_pci 0000:07:00.0: board_file api 2 bmi_id N/A crc32 ae2e275a
ath10k_pci 0000:07:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32 raw
0 hwcrypto 1
ath10k_pci 0000:07:00.0: firmware register dump:
ath10k_pci 0000:07:00.0: [00]: 0x05010000 0x00000000 0x0092E4DC 0x1029E198
ath10k_pci 0000:07:00.0: [04]: 0x0092E4DC 0x00060130 0x00000018 0x0041A760
ath10k_pci 0000:07:00.0: [08]: 0x1029E184 0x00400000 0x00000000 0x000A5C88
ath10k_pci 0000:07:00.0: [12]: 0x0000000D 0x00000000 0x0096C09C 0x0096C0A7
ath10k_pci 0000:07:00.0: [16]: 0x00000004 0x0040A090 0x0000FFFF 0x00000002
ath10k_pci 0000:07:00.0: [20]: 0x80996343 0x0041A7D0 0x00408420 0x0040D45C
ath10k_pci 0000:07:00.0: [24]: 0x80942BC4 0x0041A790 0x1029E184 0x00400000
ath10k_pci 0000:07:00.0: [28]: 0x0041A7B0 0x0041A790 0x00000024 0x00000001
ath10k_pci 0000:07:00.0: [32]: 0x80947BA7 0x0041A7B0 0x004050A8 0x0040E074
ath10k_pci 0000:07:00.0: [36]: 0x1029E164 0x00000000 0x00000000 0x00000001
ath10k_pci 0000:07:00.0: [40]: 0x809BDECC 0x0041A7D0 0x004050A8 0x0040E074
ath10k_pci 0000:07:00.0: [44]: 0x004124C4 0x004050D4 0x00000000 0x00404D9C
ath10k_pci 0000:07:00.0: [48]: 0x8099638C 0x0041A7F0 0x004050A8 0x00000000
ath10k_pci 0000:07:00.0: [52]: 0x00000000 0x004124C4 0x004050CC 0x00000005
ath10k_pci 0000:07:00.0: [56]: 0x80992076 0x0041A810 0x00408420 0x0046FFE8
ath10k_pci 0000:07:00.0: Copy Engine register dump:
ath10k_pci 0000:07:00.0: [00]: 0x00034400 1 1 3 3
ath10k_pci 0000:07:00.0: [01]: 0x00034800 5 5 488 489
ath10k_pci 0000:07:00.0: [02]: 0x00034c00 8 8 71 72
ath10k_pci 0000:07:00.0: [03]: 0x00035000 25 25 25 25
ath10k_pci 0000:07:00.0: [04]: 0x00035400 665 665 142 78
ath10k_pci 0000:07:00.0: [05]: 0x00035800 0 0 0 0
ath10k_pci 0000:07:00.0: [06]: 0x00035c00 26 26 26 26
ath10k_pci 0000:07:00.0: [07]: 0x00036000 1 1 1 1
ath10k_pci 0000:07:00.0: failed to submit keepalive on vdev 1: -108
ath10k_pci 0000:07:00.0: failed to disable keepalive on vdev 1: -108
Regards,
Nerijus
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: QCA6174 firmware crash
2022-02-19 13:30 QCA6174 firmware crash Nerijus Baliūnas
@ 2022-02-20 22:32 ` Nerijus Baliūnas
0 siblings, 0 replies; 7+ messages in thread
From: Nerijus Baliūnas @ 2022-02-20 22:32 UTC (permalink / raw)
To: ath10k
That was on Fedora 35, 5.16.9 kernel. Today with 5.16.10-200.fc35.x86_64
kernel:
ath10k_pci 0000:07:00.0: failed to install key for vdev 0 peer
f0:72:ea:0d:xx:xx: -110
wlp7s0: failed to remove key (0, f0:72:ea:0d:xx:xx) from hardware (-110)
ath10k_pci 0000:07:00.0: wmi command 114693 timeout, restarting hardware
ath10k_pci 0000:07:00.0: failed to submit keepalive on vdev 0: -11
ath10k_pci 0000:07:00.0: failed to disable keepalive on vdev 0: -11
ath10k_pci 0000:07:00.0: failed to read hi_board_data address: -16
2022-02-19 15:30, Nerijus Baliūnas wrote:
> Hello,
>
> 07:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac
> Wireless Network Adapter
> [168c:003e] (rev 20)
>
> Firmware is newest:
>
> # ethtool -i wlp7s0
> driver: ath10k_pci
> version: 5.16.9-200.fc35.x86_64
> firmware-version: SW_RM.1.1.1-00157-QCARMSWPZ-1
> expansion-rom-version:.
> bus-info: 0000:07:00.0
> supports-statistics: yes
> supports-test: no
> supports-eeprom-access: no
> supports-register-dump: no
> supports-priv-flags: no
>
> # dmesg | grep ath10k
> [ 6.698345] ath10k_pci 0000:07:00.0: pci irq msi oper_irq_mode 2 irq_mode
> 0 reset_mode 0
> [ 6.927480] ath10k_pci 0000:07:00.0: qca6174 hw2.1 target 0x05010000
> chip_id 0x003405ff sub 11ad:0804
> [ 6.928453] ath10k_pci 0000:07:00.0: kconfig debug 0 debugfs 1 tracing 0
> dfs 0 testmode 0
> [ 6.929729] ath10k_pci 0000:07:00.0: firmware ver
> SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5 features
> ignore-otp,no-4addr-pad crc32 10bf8e08
> [ 6.995609] ath10k_pci 0000:07:00.0: board_file api 2 bmi_id N/A crc32
> ae2e275a
> [ 8.223964] ath10k_pci 0000:07:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal
> otp max-sta 32 raw 0 hwcrypto 1
>
> It crashes every time I try to connect to TP-Link Archer MR600 v2 Firmware
> Version:1.5.0 0.9.1
> v0001.0 Build 210914 wifi router:
>
> ath10k_pci 0000:07:00.0: firmware crashed! (guid
> c1610eff-6185-467f-aba7-26ec9d9b8605)
> ath10k_pci 0000:07:00.0: qca6174 hw2.1 target 0x05010000 chip_id 0x003405ff
> sub 11ad:0804
> ath10k_pci 0000:07:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode
> 0
> ath10k_pci 0000:07:00.0: firmware ver SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5
> features
> ignore-otp,no-4addr-pad crc32 10bf8e08
> ath10k_pci 0000:07:00.0: board_file api 2 bmi_id N/A crc32 ae2e275a
> ath10k_pci 0000:07:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32
> raw 0 hwcrypto 1
> ath10k_pci 0000:07:00.0: firmware register dump:
> ath10k_pci 0000:07:00.0: [00]: 0x05010000 0x00000000 0x0092E4DC 0x0EB2E199
> ath10k_pci 0000:07:00.0: [04]: 0x0092E4DC 0x00060130 0x00000018 0x0041A760
> ath10k_pci 0000:07:00.0: [08]: 0x0EB2E185 0x00400000 0x00000000 0x000A5C88
> ath10k_pci 0000:07:00.0: [12]: 0x00000009 0x00000000 0x0096C09C 0x0096C0A7
> ath10k_pci 0000:07:00.0: [16]: 0x0096BDBC 0x009287BD 0x00000000 0x009287BD
> ath10k_pci 0000:07:00.0: [20]: 0x4092E4DC 0x0041A710 0x00000000 0x0F000000
> ath10k_pci 0000:07:00.0: [24]: 0x809432A7 0x0041A770 0x0040D45C 0xC092E4DC
> ath10k_pci 0000:07:00.0: [28]: 0x80942BC4 0x0041A790 0x0EB2E185 0x00400000
> ath10k_pci 0000:07:00.0: [32]: 0x80947BA7 0x0041A7B0 0x004050A8 0x0040E074
> ath10k_pci 0000:07:00.0: [36]: 0x809BDECC 0x0041A7D0 0x004050A8 0x0040E074
> ath10k_pci 0000:07:00.0: [40]: 0x8099638C 0x0041A7F0 0x004050A8 0x00000000
> ath10k_pci 0000:07:00.0: [44]: 0x80992076 0x0041A810 0x00408420 0x0046FFE8
> ath10k_pci 0000:07:00.0: [48]: 0x80996BD3 0x0041A830 0x00408420 0x00000000
> ath10k_pci 0000:07:00.0: [52]: 0x800B4405 0x0041A850 0x00422318 0x00005002
> ath10k_pci 0000:07:00.0: [56]: 0x809A6C34 0x0041A8E0 0x0042932C 0x0042CA44
> ath10k_pci 0000:07:00.0: Copy Engine register dump:
> ath10k_pci 0000:07:00.0: [00]: 0x00034400 1 1 3 3
> ath10k_pci 0000:07:00.0: [01]: 0x00034800 13 13 272 273
> ath10k_pci 0000:07:00.0: [02]: 0x00034c00 13 13 76 77
> ath10k_pci 0000:07:00.0: [03]: 0x00035000 27 27 28 27
> ath10k_pci 0000:07:00.0: [04]: 0x00035400 1629 1629 112 48
> ath10k_pci 0000:07:00.0: [05]: 0x00035800 0 0 0 0
> ath10k_pci 0000:07:00.0: [06]: 0x00035c00 27 27 27 27
> ath10k_pci 0000:07:00.0: [07]: 0x00036000 1 1 1 1
> ath10k_pci 0000:07:00.0: failed to create WMI vdev 1: -108
>
>
> ath10k_pci 0000:07:00.0: firmware crashed! (guid
> 016cc818-beee-4422-b9dd-fee9fd612a03)
> ath10k_pci 0000:07:00.0: qca6174 hw2.1 target 0x05010000 chip_id 0x003405ff
> sub 11ad:0804
> ath10k_pci 0000:07:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode
> 0
> ath10k_pci 0000:07:00.0: firmware ver SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5
> features
> ignore-otp,no-4addr-pad crc32 10bf8e08
> ath10k_pci 0000:07:00.0: board_file api 2 bmi_id N/A crc32 ae2e275a
> ath10k_pci 0000:07:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32
> raw 0 hwcrypto 1
> ath10k_pci 0000:07:00.0: firmware register dump:
> ath10k_pci 0000:07:00.0: [00]: 0x05010000 0x00000000 0x0092E4DC 0x1029E198
> ath10k_pci 0000:07:00.0: [04]: 0x0092E4DC 0x00060130 0x00000018 0x0041A760
> ath10k_pci 0000:07:00.0: [08]: 0x1029E184 0x00400000 0x00000000 0x000A5C88
> ath10k_pci 0000:07:00.0: [12]: 0x0000000D 0x00000000 0x0096C09C 0x0096C0A7
> ath10k_pci 0000:07:00.0: [16]: 0x00000004 0x0040A090 0x0000FFFF 0x00000002
> ath10k_pci 0000:07:00.0: [20]: 0x80996343 0x0041A7D0 0x00408420 0x0040D45C
> ath10k_pci 0000:07:00.0: [24]: 0x80942BC4 0x0041A790 0x1029E184 0x00400000
> ath10k_pci 0000:07:00.0: [28]: 0x0041A7B0 0x0041A790 0x00000024 0x00000001
> ath10k_pci 0000:07:00.0: [32]: 0x80947BA7 0x0041A7B0 0x004050A8 0x0040E074
> ath10k_pci 0000:07:00.0: [36]: 0x1029E164 0x00000000 0x00000000 0x00000001
> ath10k_pci 0000:07:00.0: [40]: 0x809BDECC 0x0041A7D0 0x004050A8 0x0040E074
> ath10k_pci 0000:07:00.0: [44]: 0x004124C4 0x004050D4 0x00000000 0x00404D9C
> ath10k_pci 0000:07:00.0: [48]: 0x8099638C 0x0041A7F0 0x004050A8 0x00000000
> ath10k_pci 0000:07:00.0: [52]: 0x00000000 0x004124C4 0x004050CC 0x00000005
> ath10k_pci 0000:07:00.0: [56]: 0x80992076 0x0041A810 0x00408420 0x0046FFE8
> ath10k_pci 0000:07:00.0: Copy Engine register dump:
> ath10k_pci 0000:07:00.0: [00]: 0x00034400 1 1 3 3
> ath10k_pci 0000:07:00.0: [01]: 0x00034800 5 5 488 489
> ath10k_pci 0000:07:00.0: [02]: 0x00034c00 8 8 71 72
> ath10k_pci 0000:07:00.0: [03]: 0x00035000 25 25 25 25
> ath10k_pci 0000:07:00.0: [04]: 0x00035400 665 665 142 78
> ath10k_pci 0000:07:00.0: [05]: 0x00035800 0 0 0 0
> ath10k_pci 0000:07:00.0: [06]: 0x00035c00 26 26 26 26
> ath10k_pci 0000:07:00.0: [07]: 0x00036000 1 1 1 1
> ath10k_pci 0000:07:00.0: failed to submit keepalive on vdev 1: -108
> ath10k_pci 0000:07:00.0: failed to disable keepalive on vdev 1: -108
>
> Regards,
> Nerijus
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: QCA6174 firmware crash
2016-04-27 6:42 ` Michal Kazior
@ 2016-04-27 22:43 ` Michael Ney
0 siblings, 0 replies; 7+ messages in thread
From: Michael Ney @ 2016-04-27 22:43 UTC (permalink / raw)
To: Michal Kazior, ath10k
I did a few more tests, including trying Backports 4.4.2-1 with no difference. Everything's pointing to a firmware issue not related specifically to the monitor VDEV. It seems to me that the Contention Free logic in the firmware doesn't handle Contention Free null frames addressed to other MAC addresses in any mode. As soon as the firmware is set to hear data frames not addresses to the hardware's MAC the firmware will crash on the first Null Data CF frame received.
In order to see if this was related to the monitor VDEV or something else, I configured the hardware to run in promiscuous mode with the managed VDEV. To do this I configured the RX filter (register 0x1803c) manually, turning on the promiscuous bit (0x20).
Reproduction:
1. Stay in managed mode (don't enter monitor mode)
2. echo 0x1803c > /sys/kern/debug/ieee80211/phy0/reg_addr
3. cat /sys/kernel/debug/ieee80211/phy0/reg_val
4. Change bit 0x20 to on (enable promiscuous mode)
5. echo (result of step 4) > /sys/kernel/debug/ieee80211/phy0/reg_val
6. Configure another card (ath9k, etc) to a target frequency (I used 5300 since it was fairly quiet). Transmit type 0x2 subtype 0x5 (Null data + CF ACK) on a loop.
7. iw wlan0 scan freq 5300
Immediately crashes.
If I run the scan without setting the rx_filter register, there is no crash.
If I run the scan without sending the Null Data + CF ACK frames from the other card, there is no crash.
--
I also configured ath10k_core with debug mask 0x5F (PCI, WMI, HTC, HTT, MAC, and PCI dump). When the firmware crashed, there was nothing unhandled nor unusual that came across the PCI bus.
--
Finally, in the crash's firmware register dump in my original email, I typoed the 2nd entry on line 20. it should be 0x004018F0 not 0x004019F0.
> On Apr 27, 2016, at 2:42 AM, Michal Kazior <michal.kazior@tieto.com> wrote:
>
> On 26 April 2016 at 21:52, Michael Ney <neym@vorklift.com> wrote:
>
> Firmware can get confused sometimes, especially when it comes to monitor vdev.
>
> Perhaps you should try latest backports or generate one yourself from
> Kalle's ath.git? The problem may have been already fixed in upstream.
>
>
> Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: QCA6174 firmware crash
2016-04-26 19:52 ` Michael Ney
@ 2016-04-27 6:42 ` Michal Kazior
2016-04-27 22:43 ` Michael Ney
0 siblings, 1 reply; 7+ messages in thread
From: Michal Kazior @ 2016-04-27 6:42 UTC (permalink / raw)
To: Michael Ney; +Cc: ath10k
On 26 April 2016 at 21:52, Michael Ney <neym@vorklift.com> wrote:
> Michal,
>
> I'm using Backports 4.2. I added that patch and no change to the crash. That patch changed the TX NSS config, but didn't do anything with the RX. I can watch kernel log and see that the crash happens immediately when I send the Null Data / QOS Null Data with any of the CF attributes, so it's definitely on RX. All other frame types work fine.
Firmware can get confused sometimes, especially when it comes to monitor vdev.
Perhaps you should try latest backports or generate one yourself from
Kalle's ath.git? The problem may have been already fixed in upstream.
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: QCA6174 firmware crash
2016-04-26 6:08 ` Michal Kazior
@ 2016-04-26 19:52 ` Michael Ney
2016-04-27 6:42 ` Michal Kazior
0 siblings, 1 reply; 7+ messages in thread
From: Michael Ney @ 2016-04-26 19:52 UTC (permalink / raw)
To: Michal Kazior; +Cc: ath10k
Michal,
I'm using Backports 4.2. I added that patch and no change to the crash. That patch changed the TX NSS config, but didn't do anything with the RX. I can watch kernel log and see that the crash happens immediately when I send the Null Data / QOS Null Data with any of the CF attributes, so it's definitely on RX. All other frame types work fine.
Thanks,
Michael
> On Apr 26, 2016, at 2:08 AM, Michal Kazior <michal.kazior@tieto.com> wrote:
>
> On 25 April 2016 at 22:35, Michael Ney <neym@vorklift.com> wrote:
>> Hello,
>>
>> I ran into a crash with the QCA6174 firmware and I was hoping someone knew a solution to it or could pass it on to Qualcomm Atheros to be resolved.
>>
>> The hardware version is QCA6174 HW 2.1
>>
>> The firmware version I am using is SW_RM.1.1.1-00157-QCARMSWPZ-1 (the same version available for download from Kalle Valo's git for QCA6174 HW 2.1).
>>
>> The crash occurs when receiving certain frame types.
> [...]
>
> What kernel version are you using? Do you have this patch[1] applied?
> If not, can you try it, please?
>
> [1]: https://patchwork.kernel.org/patch/8481281/
>
>
>
> Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: QCA6174 firmware crash
2016-04-25 20:35 Michael Ney
@ 2016-04-26 6:08 ` Michal Kazior
2016-04-26 19:52 ` Michael Ney
0 siblings, 1 reply; 7+ messages in thread
From: Michal Kazior @ 2016-04-26 6:08 UTC (permalink / raw)
To: Michael Ney; +Cc: ath10k
On 25 April 2016 at 22:35, Michael Ney <neym@vorklift.com> wrote:
> Hello,
>
> I ran into a crash with the QCA6174 firmware and I was hoping someone knew a solution to it or could pass it on to Qualcomm Atheros to be resolved.
>
> The hardware version is QCA6174 HW 2.1
>
> The firmware version I am using is SW_RM.1.1.1-00157-QCARMSWPZ-1 (the same version available for download from Kalle Valo's git for QCA6174 HW 2.1).
>
> The crash occurs when receiving certain frame types.
[...]
What kernel version are you using? Do you have this patch[1] applied?
If not, can you try it, please?
[1]: https://patchwork.kernel.org/patch/8481281/
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread
* QCA6174 firmware crash
@ 2016-04-25 20:35 Michael Ney
2016-04-26 6:08 ` Michal Kazior
0 siblings, 1 reply; 7+ messages in thread
From: Michael Ney @ 2016-04-25 20:35 UTC (permalink / raw)
To: ath10k
Hello,
I ran into a crash with the QCA6174 firmware and I was hoping someone knew a solution to it or could pass it on to Qualcomm Atheros to be resolved.
The hardware version is QCA6174 HW 2.1
The firmware version I am using is SW_RM.1.1.1-00157-QCARMSWPZ-1 (the same version available for download from Kalle Valo's git for QCA6174 HW 2.1).
The crash occurs when receiving certain frame types.
Reproduction:
1. Place QCA6174 into monitor mode.
2. Use another card (such as an ath9k) to send an Null Data or QOS Null Data with CF-ACK or CF-Poll (frame type 2, frame subtypes 5, 6, 7, D, E, or F). The DA of the frame must not be the MAC of the QCA6174 (the crash does not happen if the DA is the MAC).
3. Firmware immediately crashes.
The crash's Firmware register dump is:
[00] 0x05010000 0x00000000 0x00000000 0x00000000
[04] 0x00000000 0x00000000 0x00000000 0x00000000
[..]
[16] 0x00000000 0x00000000 0x00000000 0x00000000
[20] 0x00000000 0x004019F0 0x00000000 0x00000000
[24] 0x00000000 0x00000000 0x00000000 0x00000000
[..]
[56] 0x00000000 0x00000000 0x00000000 0x00000000
Thanks for any help,
Michael
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2022-02-20 22:34 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-19 13:30 QCA6174 firmware crash Nerijus Baliūnas
2022-02-20 22:32 ` Nerijus Baliūnas
-- strict thread matches above, loose matches on Subject: below --
2016-04-25 20:35 Michael Ney
2016-04-26 6:08 ` Michal Kazior
2016-04-26 19:52 ` Michael Ney
2016-04-27 6:42 ` Michal Kazior
2016-04-27 22:43 ` Michael Ney
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).