* Qualcomm Atheros QCA6174 monitoring mode receiving no data
@ 2019-05-31 9:57 Patrick Daume
2019-06-03 9:25 ` Kalle Valo
0 siblings, 1 reply; 8+ messages in thread
From: Patrick Daume @ 2019-05-31 9:57 UTC (permalink / raw)
To: ath10k
I've an SparkLan WPEQ-261ACN(BT) Qualcomm Atheros QCA6174 chipset on an 4.4.1 Kernel.
If I bring the chip in moinitor mode some Data-, QoS-, Acknowledgment-packets are notably missing.
For comparison I used tcpdump in parallel wich an Intel Wireless 3160 chip.
Only Beacons, Probe Requests and Response were recorded.
I tried to update the kernel to '4.9.140' and the firmware to 'WLAN.RM.4.4.1-00079-QCARMSWPZ-1' resulting in the monitoring mode Interface receiving no data at all.
I also tried different version of the firmware in combination with backports on the 4.4.1 Kernel.
All relevant backports starting from 'v4.14-rc2' show the same behaviour in monitor mode
(including tests with the 'WLAN.RM.4.4.1-00079-QCARMSWPZ-1', '4.4.1.c3', '4.4.1.c2' firmware in combination with 'v4.14-rc2', 'v4.20.17', 'v5.0.5' 'v5.1-rc2' backports)
Can anyone point out which patches may be relavant?
Is the monitoring mode no longer supported with a newer firmware/driver version?
Is the lower amount of packages a firmware limitation or possible to work around in the driver?
lshw >>
*-pci
description: PCI bridge
product: NVIDIA Corporation
vendor: NVIDIA Corporation
physical id: 1
bus info: pci@0000:00:01.0
version: a1
width: 32 bits
clock: 33MHz
capabilities: pci normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:388 memory:50200000-503fffff
*-network
description: interface
product: QCA6174 802.11ac Wireless Network Adapter
vendor: Qualcomm Atheros
physical id: 0
bus info: pci@0000:01:00.0
logical name: wlan0
version: 32
serial: [REMOVED]
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list logical
configuration: broadcast=yes driver=ath10k_pci driverversion=4.4.38-6-dedrone firmware=WLAN.RM.2.0-00180-QCARMSWPZ-1 latency=0 link=yes multicast=yes
resources: irq:452 memory:50200000-503fffff
lshw >>
*-pci:0
description: PCI bridge
product: NVIDIA Corporation
vendor: NVIDIA Corporation
physical id: 100
bus info: pci@0000:00:00.0
version: a1
width: 32 bits
clock: 33MHz
capabilities: pci normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:130 memory:32200000-322fffff
*-network
description: interface
product: Wireless 3160
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:01:00.0
logical name: wlan0
version: 83
serial: [REMOVED]
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list logical
configuration: broadcast=yes driver=iwlwifi driverversion=3.10.40 firmware=25.30.13.0 latency=0 link=yes multicast=yes
resources: irq:643 memory:32200000-32201fff
lshw after kernel and firmware update >>
*-pci
description: PCI bridge
product: NVIDIA Corporation
vendor: NVIDIA Corporation
physical id: 1
bus info: pci@0000:00:01.0
version: a1
width: 32 bits
clock: 33MHz
capabilities: pci normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:381 memory:40200000-403fffff
*-network
description: Wireless interface
product: QCA6174 802.11ac Wireless Network Adapter
vendor: Qualcomm Atheros
physical id: 0
bus info: pci@0000:01:00.0
logical name: wlan0
version: 32
serial: [REMOVED]
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list logical wireless
configuration: broadcast=yes driver=ath10k_pci driverversion=4.9.140-tegra firmware=WLAN.RM.4.4.1-00079-QCARMSWPZ-1 latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:446 memory:40200000-403fffff
dmesg >>
[ 8.125163] ath10k_pci 0000:01:00.0: enabling device (0000 -> 0002)
[ 8.128283] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 8.407814] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2
[ 8.407817] ath10k_pci 0000:01:00.0: Falling back to user helper
[ 8.410447] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/cal-pci-0000:01:00.0.bin failed with error -2
[ 8.410450] ath10k_pci 0000:01:00.0: Falling back to user helper
[ 8.425668] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1dac:0261
[ 8.425672] ath10k_pci 0000:01:00.0: kconfig debug 1 debugfs 1 tracing 0 dfs 0 testmode 0
[ 8.426406] ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[ 8.493987] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id N/A crc32 4ed3569e
sudo ifconfig wlan0 down
iw dev wlan0 set type monitor
ifconfig wlan0 up
iw dev wlan0 set freq 2412
tcpdump -i wlan0
>>>
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on wlan0, link-type IEEE802_11_RADIO (802.11 plus radiotap header), capture size 262144 bytes
0 packets captured
0 packets received by filter
0 packets dropped by kernel
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Qualcomm Atheros QCA6174 monitoring mode receiving no data
2019-05-31 9:57 Qualcomm Atheros QCA6174 monitoring mode receiving no data Patrick Daume
@ 2019-06-03 9:25 ` Kalle Valo
2019-06-03 12:50 ` Patrick Daume
0 siblings, 1 reply; 8+ messages in thread
From: Kalle Valo @ 2019-06-03 9:25 UTC (permalink / raw)
To: Patrick Daume; +Cc: ath10k
Patrick Daume <patrick.daume@dedrone.com> writes:
> I've an SparkLan WPEQ-261ACN(BT) Qualcomm Atheros QCA6174 chipset on an 4.4.1 Kernel.
> If I bring the chip in moinitor mode some Data-, QoS-,
> Acknowledgment-packets are notably missing.
> For comparison I used tcpdump in parallel wich an Intel Wireless 3160 chip.
> Only Beacons, Probe Requests and Response were recorded.
>
> I tried to update the kernel to '4.9.140' and the firmware to
> 'WLAN.RM.4.4.1-00079-QCARMSWPZ-1' resulting in the monitoring mode
> Interface receiving no data at all.
> I also tried different version of the firmware in combination with
> backports on the 4.4.1 Kernel.
> All relevant backports starting from 'v4.14-rc2' show the same
> behaviour in monitor mode
> (including tests with the 'WLAN.RM.4.4.1-00079-QCARMSWPZ-1',
> '4.4.1.c3', '4.4.1.c2' firmware in combination with 'v4.14-rc2',
> 'v4.20.17', 'v5.0.5' 'v5.1-rc2' backports)
>
> Can anyone point out which patches may be relavant?
> Is the monitoring mode no longer supported with a newer firmware/driver version?
IIRC someone reported monitor mode working on QCA6174 hw3.0 but I don't
remember the specifics. v4.14 and v4.9 are quite old kernels and
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 is also 1.5 years old firmware. I
recommend trying latest ath10k (for example v5.1) and latest firmware
for QCA6174:
https://github.com/kvalo/ath10k-firmware/blob/master/QCA6174/hw3.0/4.4.1/firmware-6.bin_WLAN.RM.4.4.1-00132-QCARMSWP-1
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Qualcomm Atheros QCA6174 monitoring mode receiving no data
2019-06-03 9:25 ` Kalle Valo
@ 2019-06-03 12:50 ` Patrick Daume
2019-06-05 5:09 ` Kalle Valo
0 siblings, 1 reply; 8+ messages in thread
From: Patrick Daume @ 2019-06-03 12:50 UTC (permalink / raw)
To: kvalo; +Cc: ath10k
I build the kernel: 5.1.0-rc7-wt-ath+ from the repository (git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git)
and replace WLAN.RM.4.4.1-00132-QCARMSWP-1 with "/lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin".
Same behavioiur as observed before. The interface receives no data in monitoring mode. While managed mode seems to work.
:~$ uname -a
Linux 5.1.0-rc7-wt-ath+ #3 SMP Fri May 17 14:58:27 CEST 2019 x86_64 x86_64 x86_64 GNU/Linux
:~$ sudo service network-manager stop
:~$ sudo lshw -sanitize
*-pci:1
description: PCI bridge
product: Sunrise Point-LP PCI Express Root Port #9
vendor: Intel Corporation
physical id: 1d
bus info: pci@0000:00:1d.0
version: f1
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:123 memory:df000000-df1fffff
*-network
description: Wireless interface
product: QCA6174 802.11ac Wireless Network Adapter
vendor: Qualcomm Atheros
physical id: 0
bus info: pci@0000:02:00.0
logical name: wlp2s0
version: 32
serial: [REMOVED]
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list logical wireless
configuration: broadcast=yes driver=ath10k_pci driverversion=5.1.0-rc7-wt-ath+ firmware=WLAN.RM.4.4.1-00132-QCARMSWP-1 latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:134 memory:df000000-df1fffff
:~$ sudo ifconfig wlp2s0 down
:~$ sudo iw dev wlp2s0 set type monitor
:~$ sudo iw dev
phy#0
Interface wlp2s0
ifindex 4
wdev 0x1
type monitor
txpower 0.00 dBm
:~$ sudo ifconfig wlp2s0 up
:~$ dmesg
[ 4.585876] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 4.587488] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 4.948771] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1dac:0261
[ 4.948773] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ 4.949182] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00132-QCARMSWP-1 api 6 features wowlan,ignore-otp,mfp crc32 79f4db86
[ 5.015300] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 4ed3569e
[ 5.077351] ath10k_pci 0000:02:00.0: UART prints enabled
[ 5.145608] ath10k_pci 0000:02:00.0: unsupported HTC service id: 1536
[ 5.399248] ath10k_pci 0000:02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ 5.506631] ath: EEPROM regdomain: 0x6c
[ 5.506632] ath: EEPROM indicates we should expect a direct regpair map
[ 5.506633] ath: Country alpha2 being used: 00
[ 5.506633] ath: Regpair used: 0x6c
[ 5.521558] ath10k_pci 0000:02:00.0 wlp2s0: renamed from wlan0
[ 9.349624] ath10k_pci 0000:02:00.0: UART prints enabled
[ 9.417824] ath10k_pci 0000:02:00.0: unsupported HTC service id: 1536
[ 172.602058] ath10k_pci 0000:02:00.0: UART prints enabled
[ 172.670794] ath10k_pci 0000:02:00.0: unsupported HTC service id: 1536
[ 173.065855] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[ 199.880218] device wlp2s0 entered promiscuous mode
[ 266.446078] device wlp2s0 left promiscuous mode
:~$ sudo tcpdump -i wlp2s0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on wlp2s0, link-type IEEE802_11_RADIO (802.11 plus radiotap header), capture size 262144 bytes
^C
0 packets captured
0 packets received by filter
0 packets dropped by kernel
# managed mode test
:~$ sudo ifconfig wlp2s0 down
:~$ sudo iw dev wlp2s0 set type managed
:~$ sudo ifconfig wlp2s0 up
:~$ iw dev
phy#0
Interface wlp2s0
ifindex 4
wdev 0x1
type managed
txpower 0.00 dBm
:~$ sudo iw wlp2s0 scan
BSS xxxxxxxxxxxxxx(on wlp2s0)
TSF: 4588156109184 usec (53d, 02:29:16)
freq: 2437
beacon interval: 100 TUs
capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
signal: -84.00 dBm
last seen: 4440 ms ago
Information elements from Probe Response frame:
SSID: xxxxxxxxxxxxx
Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0* 9.0 12.0* 18.0
DS Parameter set: channel 6
TIM: DTIM Count 0 DTIM Period 1 Bitmap Control 0x0 Bitmap[0] 0x0
ERP: <no flags>
Extended supported rates: 24.0* 36.0 48.0 54.0
BSS Load:
* station count: 4
* channel utilisation: 75/255
* available admission capacity: 0 [*32us]
HT capabilities:
Capabilities: 0x1ac
HT20
SM Power Save disabled
RX HT20 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-23
HT operation:
* primary channel: 6
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 0
* HT protection: nonmember
* non-GF present: 1
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Extended capabilities:
* Operating Mode Notification
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
RSN: * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
......
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Qualcomm Atheros QCA6174 monitoring mode receiving no data
2019-06-03 12:50 ` Patrick Daume
@ 2019-06-05 5:09 ` Kalle Valo
2019-06-05 7:18 ` Patrick Daume
2019-06-05 15:38 ` Patrick Daume
0 siblings, 2 replies; 8+ messages in thread
From: Kalle Valo @ 2019-06-05 5:09 UTC (permalink / raw)
To: Patrick Daume; +Cc: ath10k
Patrick Daume <patrick.daume@dedrone.com> writes:
> I build the kernel: 5.1.0-rc7-wt-ath+ from the repository (git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git)
> and replace WLAN.RM.4.4.1-00132-QCARMSWP-1 with "/lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin".
>
> Same behavioiur as observed before. The interface receives no data in monitoring mode. While managed mode seems to work.
>
[...]
> [ 4.948771] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1dac:0261
> [ 4.948773] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
> [ 4.949182] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00132-QCARMSWP-1 api 6 features wowlan,ignore-otp,mfp crc32 79f4db86
> [ 5.015300] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 4ed3569e
> [ 5.077351] ath10k_pci 0000:02:00.0: UART prints enabled
> [ 5.145608] ath10k_pci 0000:02:00.0: unsupported HTC service id: 1536
> [ 5.399248] ath10k_pci 0000:02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
Indeed, that firmware version does not have raw mode enabled ("raw 0").
Can you try this one:
https://github.com/kvalo/ath10k-firmware/blob/master/QCA6174/hw3.0/4.4.1.c3/firmware-6.bin_WLAN.RM.4.4.1.c3-00030
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Qualcomm Atheros QCA6174 monitoring mode receiving no data
2019-06-05 5:09 ` Kalle Valo
@ 2019-06-05 7:18 ` Patrick Daume
2019-06-05 15:38 ` Patrick Daume
1 sibling, 0 replies; 8+ messages in thread
From: Patrick Daume @ 2019-06-05 7:18 UTC (permalink / raw)
To: kvalo; +Cc: ath10k
> Indeed, that firmware version does not have raw mode enabled ("raw 0").
> Can you try this one:
>
> https://github.com/kvalo/ath10k-firmware/blob/master/QCA6174/hw3.0/4.4.1.c3/firmware-6.bin_WLAN.RM.4.4.1.c3-00030
>
I've tried the firmware WLAN.RM.4.4.1.c3-00030.
No changes on ("raw 0").
The interface receives no data in monitoring mode furthermore.
[ 4.718032] ath10k_pci 0000:02:00.0: enabling device (0000 -> 0002)
[ 4.718729] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 5.005309] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1dac:0261
[ 5.005312] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ 5.005768] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1.c3-00030 api 6 features wowlan,ignore-otp,no-4addr-pad,raw-mode,mfp crc32 9a201530
[ 5.075333] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 4ed3569e
[ 5.139360] ath10k_pci 0000:02:00.0: UART prints enabled
[ 5.203039] ath10k_pci 0000:02:00.0: unsupported HTC service id: 1536
[ 5.461084] ath10k_pci 0000:02:00.0: htt-ver 3.62 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ 5.569983] ath: EEPROM regdomain: 0x6c
[ 5.569985] ath: EEPROM indicates we should expect a direct regpair map
[ 5.569986] ath: Country alpha2 being used: 00
[ 5.569986] ath: Regpair used: 0x6c
[ 5.578025] ath10k_pci 0000:02:00.0 wlp2s0: renamed from wlan0
[ 5.801629] ath10k_pci 0000:02:00.0: UART prints enabled
[ 5.865226] ath10k_pci 0000:02:00.0: unsupported HTC service id:
1536
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Qualcomm Atheros QCA6174 monitoring mode receiving no data
2019-06-05 5:09 ` Kalle Valo
2019-06-05 7:18 ` Patrick Daume
@ 2019-06-05 15:38 ` Patrick Daume
2019-06-13 8:54 ` Patrick Daume
1 sibling, 1 reply; 8+ messages in thread
From: Patrick Daume @ 2019-06-05 15:38 UTC (permalink / raw)
To: kvalo; +Cc: ath10k
I test it with modprobe option rawmode=1 and it seems to work.
solution:
linux kernel 5.1.0-rc7-wt-ath+
firmware: WLAN.RM.4.4.1.c3-00030
sudo modprobe ath10k_core rawmode=1
sudo modprobe ath10k_pci
But if i call tcpdump for a while i got some error traces in dmesg.
How
can i fix this?
[ 281.101682] pinctrl_intel [last unloaded: cfg80211]
[ 281.101694] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G W 5.1.0-rc7-wt-ath+ #3
[ 281.101697] Hardware name: /, BIOS 5.11 03/24/2016
[ 281.101703] RIP: 0010:skb_trim+0x2d/0x30
[ 281.101708] Code: 00 00 39 77 70 77 02 f3 c3 8b 47 74 85 c0 75 1a 48 8b 87 c8 00 00 00 48 2b 87 c0 00 00 00 89 77 70 01 c6 89 b7 b8 00 00 00 c3 <0f> 0b c3 0f 1f 44 00 00 8b 87 e8 00 00 00 8b 96 d0 00 00 00 01 d0
[ 281.101712] RSP: 0018:ffff9d47dda83ce0 EFLAGS: 00010206
[ 281.101717] RAX: 00000000000004cc RBX: 0000000000008000 RCX: ffff9d47dda83e60
[ 281.101720] RDX: 0000000000000000 RSI: 0000000000000ae0 RDI: ffff9d47d3eebf00
[ 281.101723] RBP: 0000000000000004 R08: 0000000000000000 R09: 0000000000000000
[ 281.101726] R10: fffff2c05158d840 R11: ffff9d43b447e4b8 R12: 0000000000000000
[ 281.101729] R13: 0000000000004000 R14: ffff9d47d0421620 R15: ffff9d47d3eebf00
[ 281.101734] FS: 0000000000000000(0000) GS:ffff9d47dda80000(0000) knlGS:0000000000000000
[ 281.101737] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 281.101741] CR2: 000056110f0580a4 CR3: 00000003a120e003 CR4: 00000000003606e0
[ 281.101744] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 281.101747] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 281.101749] Call Trace:
[ 281.101755] <IRQ>
[ 281.101798] ath10k_htt_rx_h_mpdu+0x6a5/0xab0 [ath10k_core]
[ 281.101813] ? swiotlb_map+0x6b/0x1c0
[ 281.101846] ath10k_htt_txrx_compl_task+0xc4f/0x1490 [ath10k_core]
[ 281.101864] ath10k_pci_napi_poll+0x51/0x130 [ath10k_pci]
[ 281.101876] net_rx_action+0x27e/0x3d0
[ 281.101888] __do_softirq+0xfd/0x2d8
[ 281.101899] irq_exit+0xae/0xb0
[ 281.101906] do_IRQ+0x52/0xe0
[ 281.101913] common_interrupt+0xf/0xf
[ 281.101917] </IRQ>
[ 281.101928] RIP: 0010:cpuidle_enter_state+0xc4/0x460
[ 281.101932] Code: e8 71 f7 90 ff 80 7c 24 0f 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 b3 f6 96 ff fb 66 0f 1f 44 00 00 <45> 85 e4 0f 88 35 03 00 00 4c 2b 7c 24 10 48 ba cf f7 53 e3 a5 9b
[ 281.101936] RSP: 0018:ffffacef41943e88 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffdd
[ 281.101941] RAX: ffff9d47ddaa2c80 RBX: ffffffffad2d7860 RCX: 000000000000001f
[ 281.101944] RDX: 0000000000000000 RSI: 000000002d958403 RDI: 0000000000000000
[ 281.101947] RBP: ffff9d47ddaac100 R08: fffffffca8f126a7 R09: ffff9d47ddaa1ca4
[ 281.101950] R10: 0000000000000018 R11: 0000000000002615 R12: 0000000000000008
[ 281.101953] R13: 0000000000000008 R14: ffffffffad2d7860 R15: 0000004172f2f453
[ 281.101965] ? cpuidle_enter_state+0x9f/0x460
[ 281.101972] do_idle+0x202/0x280
[ 281.101980] cpu_startup_entry+0x19/0x20
[ 281.101990] start_secondary+0x17a/0x1d0
[ 281.101999] secondary_startup_64+0xa4/0xb0
[ 281.102006] ---[ end trace 23dc6ddb093396c5 ]---
[ 306.126454] device wlp2s0 entered promiscuous mode
[ 317.700835] device wlp2s0 left promiscuous mode
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Qualcomm Atheros QCA6174 monitoring mode receiving no data
2019-06-05 15:38 ` Patrick Daume
@ 2019-06-13 8:54 ` Patrick Daume
2019-06-13 9:03 ` Patrick Daume
0 siblings, 1 reply; 8+ messages in thread
From: Patrick Daume @ 2019-06-13 8:54 UTC (permalink / raw)
To: kvalo; +Cc: ath10k
On Mi, 2019-06-05 at 17:38 +0200, Patrick Daume wrote:
> I test it with modprobe option rawmode=1 and it seems to work.
>
> solution:
>
> linux kernel 5.1.0-rc7-wt-ath+
> firmware: WLAN.RM.4.4.1.c3-00030
>
> sudo modprobe ath10k_core rawmode=1
> sudo modprobe ath10k_pci
>
>
> But if i call tcpdump for a while i got some error traces in dmesg.
> How
> can i fix this?
>
> [ 281.101682] pinctrl_intel [last unloaded: cfg80211]
> [ 281.101694] CPU: 1 PID: 0 Comm: swapper/1 Tainted:
> G W 5.1.0-rc7-wt-ath+ #3
> [ 281.101697] Hardware name: /, BIOS 5.11 03/24/2016
> [ 281.101703] RIP: 0010:skb_trim+0x2d/0x30
> [ 281.101708] Code: 00 00 39 77 70 77 02 f3 c3 8b 47 74 85 c0 75 1a
> 48 8b 87 c8 00 00 00 48 2b 87 c0 00 00 00 89 77 70 01 c6 89 b7 b8 00
> 00 00 c3 <0f> 0b c3 0f 1f 44 00 00 8b 87 e8 00 00 00 8b 96 d0 00 00
> 00 01 d0
> [ 281.101712] RSP: 0018:ffff9d47dda83ce0 EFLAGS: 00010206
> [ 281.101717] RAX: 00000000000004cc RBX: 0000000000008000 RCX:
> ffff9d47dda83e60
> [ 281.101720] RDX: 0000000000000000 RSI: 0000000000000ae0 RDI:
> ffff9d47d3eebf00
> [ 281.101723] RBP: 0000000000000004 R08: 0000000000000000 R09:
> 0000000000000000
> [ 281.101726] R10: fffff2c05158d840 R11: ffff9d43b447e4b8 R12:
> 0000000000000000
> [ 281.101729] R13: 0000000000004000 R14: ffff9d47d0421620 R15:
> ffff9d47d3eebf00
> [ 281.101734] FS: 0000000000000000(0000) GS:ffff9d47dda80000(0000)
> knlGS:0000000000000000
> [ 281.101737] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 281.101741] CR2: 000056110f0580a4 CR3: 00000003a120e003 CR4:
> 00000000003606e0
> [ 281.101744] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
> 0000000000000000
> [ 281.101747] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
> 0000000000000400
> [ 281.101749] Call Trace:
> [ 281.101755] <IRQ>
> [ 281.101798] ath10k_htt_rx_h_mpdu+0x6a5/0xab0 [ath10k_core]
> [ 281.101813] ? swiotlb_map+0x6b/0x1c0
> [ 281.101846] ath10k_htt_txrx_compl_task+0xc4f/0x1490 [ath10k_core]
> [ 281.101864] ath10k_pci_napi_poll+0x51/0x130 [ath10k_pci]
> [ 281.101876] net_rx_action+0x27e/0x3d0
> [ 281.101888] __do_softirq+0xfd/0x2d8
> [ 281.101899] irq_exit+0xae/0xb0
> [ 281.101906] do_IRQ+0x52/0xe0
> [ 281.101913] common_interrupt+0xf/0xf
> [ 281.101917] </IRQ>
> [ 281.101928] RIP: 0010:cpuidle_enter_state+0xc4/0x460
> [ 281.101932] Code: e8 71 f7 90 ff 80 7c 24 0f 00 74 17 9c 58 0f 1f
> 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 b3 f6 96 ff fb 66 0f 1f
> 44 00 00 <45> 85 e4 0f 88 35 03 00 00 4c 2b 7c 24 10 48 ba cf f7 53
> e3 a5 9b
> [ 281.101936] RSP: 0018:ffffacef41943e88 EFLAGS: 00000246 ORIG_RAX:
> ffffffffffffffdd
> [ 281.101941] RAX: ffff9d47ddaa2c80 RBX: ffffffffad2d7860 RCX:
> 000000000000001f
> [ 281.101944] RDX: 0000000000000000 RSI: 000000002d958403 RDI:
> 0000000000000000
> [ 281.101947] RBP: ffff9d47ddaac100 R08: fffffffca8f126a7 R09:
> ffff9d47ddaa1ca4
> [ 281.101950] R10: 0000000000000018 R11: 0000000000002615 R12:
> 0000000000000008
> [ 281.101953] R13: 0000000000000008 R14: ffffffffad2d7860 R15:
> 0000004172f2f453
> [ 281.101965] ? cpuidle_enter_state+0x9f/0x460
> [ 281.101972] do_idle+0x202/0x280
> [ 281.101980] cpu_startup_entry+0x19/0x20
> [ 281.101990] start_secondary+0x17a/0x1d0
> [ 281.101999] secondary_startup_64+0xa4/0xb0
> [ 281.102006] ---[ end trace 23dc6ddb093396c5 ]---
> [ 306.126454] device wlp2s0 entered promiscuous mode
> [ 317.700835] device wlp2s0 left promiscuous mode
htt.h:2226
/*
* Should be: sizeof(struct htt_host_rx_desc) + max rx MSDU size,
>> * sizeof(struct htt_host_rx_desc) 360 bytes + max MPDU/~MDSU size
802.11AC 16.384 bytes (2^14) + (2^9)
* rounded up to a cache line size.
*/
>> #define HTT_RX_BUF_SIZE 16896
#define HTT_RX_MSDU_SIZE (HTT_RX_BUF_SIZE - (int)sizeof(struct
htt_rx_desc))
htt_rx.c:1390, ath10k_htt_rx_h_undecap_raw
if (WARN_ON_ONCE(!(is_first && is_last) && !msdu_limit_err))
return;
/* We see zero length msdus and greater max lenght msdus,
* not sure why. At least don't try to trim it further.
*/
>> if (unlikely(msdu->len < FCS_LEN || msdu->len > HTT_RX_MSDU_SIZE))
>> return;
skb_trim(msdu, msdu->len - FCS_LEN);
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Qualcomm Atheros QCA6174 monitoring mode receiving no data
2019-06-13 8:54 ` Patrick Daume
@ 2019-06-13 9:03 ` Patrick Daume
0 siblings, 0 replies; 8+ messages in thread
From: Patrick Daume @ 2019-06-13 9:03 UTC (permalink / raw)
To: kvalo; +Cc: ath10k
I have a solution for this issue,
please find out if its the right way
htt.h:2226
/*
* Should be: sizeof(struct htt_host_rx_desc) + max rx MSDU size,
>> * sizeof(struct htt_host_rx_desc) 360 bytes + max MPDU/~MDSU size
802.11AC 16.384 bytes (2^14) + (2^9)
* rounded up to a cache line size.
*/
>> #define HTT_RX_BUF_SIZE 16896
#define HTT_RX_MSDU_SIZE (HTT_RX_BUF_SIZE - (int)sizeof(struct
htt_rx_desc))
htt_rx.c:1390, ath10k_htt_rx_h_undecap_raw
if (WARN_ON_ONCE(!(is_first && is_last) && !msdu_limit_err))
return;
/* We see zero length msdus and greater max lenght msdus,
* not sure why. At least don't try to trim it further.
*/
>> if (unlikely(msdu->len < FCS_LEN || msdu->len > HTT_RX_MSDU_SIZE))
>> return;
skb_trim(msdu, msdu->len - FCS_LEN);
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2019-06-13 9:03 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-05-31 9:57 Qualcomm Atheros QCA6174 monitoring mode receiving no data Patrick Daume
2019-06-03 9:25 ` Kalle Valo
2019-06-03 12:50 ` Patrick Daume
2019-06-05 5:09 ` Kalle Valo
2019-06-05 7:18 ` Patrick Daume
2019-06-05 15:38 ` Patrick Daume
2019-06-13 8:54 ` Patrick Daume
2019-06-13 9:03 ` Patrick Daume
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.