Bug 206923 - ath10k qca6174 failed to receive scan abortion completion: timed out, restarts hardware, then freezes up the system
Summary: ath10k qca6174 failed to receive scan abortion completion: timed out, restart...
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-22 20:21 UTC by Mike Lothian
Modified: 2020-03-22 20:21 UTC (History)
0 users

See Also:
Kernel Version: 5.6.0-rc5
Subsystem:
Regression: No
Bisected commit-id:

Attachments
dmesg (82.66 KB, text/plain)
2020-03-22 20:21 UTC, Mike Lothian 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Mike Lothian 2020-03-22 20:21:44 UTC 
Created attachment 288011 [details]
dmesg

Key messages:

[    0.798721] ath10k_pci 0000:3c:00.0: Using iommu dma mapping
[    0.798724] ath10k_pci 0000:3c:00.0: DMAR: 32bit DMA uses non-identity mapping
[    0.798891] ath10k_pci 0000:3c:00.0: enabling device (0000 -> 0002)
[    0.802044] ath10k_pci 0000:3c:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[    1.020644] ath10k_pci 0000:3c:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
[    1.025096] ath10k_pci 0000:3c:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0
[    1.032111] ath10k_pci 0000:3c:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1
[    1.102145] ath10k_pci 0000:3c:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b
[    1.199203] ath10k_pci 0000:3c:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1


[86441.174256] ath10k_pci 0000:3c:00.0: failed to receive scan abortion completion: timed out
[86441.174265] ath10k_pci 0000:3c:00.0: failed to stop scan: -110
[86441.174268] ath10k_pci 0000:3c:00.0: failed to start hw scan: -110
[87233.376227] ath10k_pci 0000:3c:00.0: wmi command 12289 timeout, restarting hardware
[87233.376232] ath10k_pci 0000:3c:00.0: failed to start hw scan: -11
[87236.416323] ath10k_pci 0000:3c:00.0: failed to receive initialized event from target: 00000000
[87239.448376] ath10k_pci 0000:3c:00.0: failed to receive initialized event from target: 00000000
[87239.448379] ath10k_pci 0000:3c:00.0: failed to wait for target init: -110
[87239.449823] ath10k_pci 0000:3c:00.0: failed to set inactivity time for vdev 0: -108
[87239.449825] ath10k_pci 0000:3c:00.0: failed to setup powersave: -108
[87239.449841] ath10k_pci 0000:3c:00.0: failed to set PS Mode 0 for vdev 0: -108
[87239.449842] ath10k_pci 0000:3c:00.0: failed to setup powersave: -108
[87239.449843] ath10k_pci 0000:3c:00.0: failed to setup ps on vdev 0: -108
[87239.449860] ath10k_pci 0000:3c:00.0: failed to flush transmit queue (skip 1 ar-state 2): 5000
[87239.449915] ath10k_pci 0000:3c:00.0: failed to delete peer a0:63:91:a7:3c:9f for vdev 0: -108
[87239.450437] ath10k_pci 0000:3c:00.0: failed to recalculate rts/cts prot for vdev 0: -108
[87239.450438] ath10k_pci 0000:3c:00.0: failed to set cts protection for vdev 0: -108

Full dmesg attached
Note You need to log in before you can comment on or make changes to this bug.