New hardware, old problem: stuck beacon when here is WiFi traffic

[Adrian Chadd]

On 26 April 2013 01:45, Adrian Chadd <adrian at freebsd.org> wrote:
> Hi,
>
> Wait. sysctl dev.ath.0.forcebstuck=1 didn't fix it?

So the descriptors are mostly completed. I really need to hack the
reset path to continue printing everything in the queue, not just the
frames that were completed.

But the TXQ[1] head pointer is pointing to the wrong descriptor. It's
pointing to a descriptor that's finished, whose next descriptor is
also finished. That makes no sense.

I'll have to add some more debugging to -HEAD so to dump out the full
set of TX descriptors in the queue. That hopefully will shed some
light here.



Adrian