Anyone seeing tx-credits 'hang'?

[Ben Greear <greearb@candelatech.com>]

I am still working on tracking down tx-credits hang, where it appears
to the driver that firmware does not return tx credits, and the driver
then gets lots of -11 errors from htc/wmi and will not recover (well,
once it recovered after hanging for about 45 minutes, for reasons that are totally
beyond me.  I do not normally wait so long).

I am using a hacked ath10k driver and CT firmware, but I am suspicious that the problem
is not unique to me, though I probably hit the problem much more often
due to the types of stress tests I am running.

I have implemented a keep-alive between my driver and CT firmware,
and firmware will assert if it does not get a message within
about 10 seconds.  This is a wmi-message, so if we hang due to credits,
the firmware will assert and dump a nice crash log (and host can recover).

One crash I looked at closely appears to show the firmware thinking it
has returned all credits, but driver never received them.  What is more,
it seems that the driver thought it sent one additional wmi command
that the firmware did not receive in the wmi message handling code.

I am curious if anyone else has seen these problems (even if very rarely),
and if anyone has done any additional debugging on what might be the issue.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k