panic: ath_legacy_tx_dma_restart: Q3: called with PUTRUNNING=1

2013-06-02 Thread Kim Culhan
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 http://lists.freebsd.org/mailman/listinf

Re: panic: ath_legacy_tx_dma_restart: Q3: called with PUTRUNNING=1

2013-06-02 Thread Adrian Chadd
hi, Can you please provide the backtrace? thanks, adrian On 2 June 2013 04:49, Kim Culhan 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 >

Re: Atheros AR5B22 WLAN+Bluetooth support on FreeBSD

2013-06-02 Thread Adrian Chadd
Hi, It's supported in -HEAD. Bluetooth may or may not work. I've not sat down and focused on that, sorry. adrian On 2 June 2013 08:00, Miguel Clara wrote: > Hi, > > Sorry for the direct mail, but I not sure about the correct steps to > take when a driver is missing... if there a mailling list

Re: panic: ath_legacy_tx_dma_restart: Q3: called with PUTRUNNING=1

2013-06-02 Thread Adrian Chadd
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 during

Re: panic: ath_legacy_tx_dma_restart: Q3: called with PUTRUNNING=1

2013-06-02 Thread Adrian Chadd
Oh, and please file a PR. With that core.txt file. It's fine. adrian On 2 June 2013 10:18, Adrian Chadd 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 during a stuck

Re: panic: ath_legacy_tx_dma_restart: Q3: called with PUTRUNNING=1

2013-06-02 Thread Adrian Chadd
On 2 June 2013 04:49, Kim Culhan 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 implement exactl

Re: panic: ath_legacy_tx_dma_restart: Q3: called with PUTRUNNING=1

2013-06-02 Thread Adrian Chadd
.. 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

playing with 802.11p / DMCA-86P2

2013-06-02 Thread Adrian Chadd
So Unex gave me a couple of their 802.11p NICs to play with. http://www.unex.com.tw/product/dcma-86p2 It's a NIC specifically designed for the 5.9GHz band for 802.11p deployments. Now, the NIC probes and detects fine under FreeBSD. The main issue is the lack of regulatory information for said NI