I should have looked a bit longer. I was still running the patch
that acquired rcu-lock before the spinlock in the tx-push-pending.
I tried with that set to the normal way, and now it did not
hang. I'll do some more testing in case I just got lucky.
Thanks,
Ben
On 11/09/2016 04:07 PM, Ben
I have been seeing this for a while, but finally took some time to get some
debug info. This is with modified 4.7 kernel and ath10k firmware for 9984 NIC.
But, I suspect this could be a more general problem.
An easy way I can reproduce this is to associate a station and then try
to change its
ed to the wrong git tree, please drop us a note to
> help improve the system]
>
> url:
> https://github.com/0day-ci/linux/commits/c_traja-qti-qualcomm-com/ath10k-Add-support-for-BTCOEX-feature/20161109-043718
> base: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git pending
head: 0b28fa7b6a77e1815cb5d34fe5b889ab53c5ca04
commit: d557637809b66bd63a4d4693a11d5c287a6a68c0 [25/27] wcn36xx: Transition
driver to SMD client
config: sparc64-allmodconfig (attached as .config)
compiler:
-qti-qualcomm-com/ath10k-Add-support-for-BTCOEX-feature/20161109-043718
base: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git
ath-next
config: xtensa-allmodconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
wget
https://git.kernel.org/cgit/linux
/commits/c_traja-qti-qualcomm-com/ath10k-Add-support-for-BTCOEX-feature/20161109-043718
base: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git
ath-next
config: xtensa-allmodconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
wget
https://git.kernel.org
