Been seeing panics as in the Subject for a few weeks.
Now running (and seeing the panics) with r251078M.
Please let me know if additional info is needed.
thanks
-kim
___
freebsd-wireless@freebsd.org mailing list
hi,
Can you please provide the backtrace?
thanks,
adrian
On 2 June 2013 04:49, Kim Culhan w8hd...@gmail.com wrote:
Been seeing panics as in the Subject for a few weeks.
Now running (and seeing the panics) with r251078M.
Please let me know if additional info is needed.
thanks
-kim
Hi,
So this is yet another instance of the MAC being tickled slightly
wrong/racy, which could lead to hardware lockups or general craziness.
It's happening during a stuck beacon whilst in AP mode.
I'll go and review the transmit/receive/reset path again and ensure
it's all shut down right
Oh, and please file a PR. With that core.txt file. It's fine.
adrian
On 2 June 2013 10:18, Adrian Chadd adr...@freebsd.org wrote:
Hi,
So this is yet another instance of the MAC being tickled slightly
wrong/racy, which could lead to hardware lockups or general craziness.
It's happening
On 2 June 2013 04:49, Kim Culhan w8hd...@gmail.com wrote:
Been seeing panics as in the Subject for a few weeks.
Now running (and seeing the panics) with r251078M.
Please let me know if additional info is needed.
So, just to brain dump what the story is here.
I changed the TX DMA code to
.. and stupidly, my reset code does this:
* wait for tx/rx to finish
* bump reset counter
rather than what it should be doing, which is:
* bump reset counter
* wait for tx/rx to finish
because TX will continue if the reset flag isn't set. And I bet that's
what is going on.
Thanks for pointing
