panic: ath_legacy_tx_dma_restart: Q3: called with PUTRUNNING=1

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

ath0_node_lock ath0_com_lock lor

Have not seen an lor in some time, this noted today fyi lock order reversal: 1st 0xff80009267f0 ath0_node_lock (ath0_node_lock) @ /usr/src/sys/net80211/ieee80211_ioctl.c:1341 2nd 0xff8000925018 ath0_com_lock (ath0_com_lock) @ /usr/src/sys/net80211/ieee80211_node.c:2619 KDB: stack backtra

Re: ath related panic

On Tue, Sep 25, 2012 at 4:42 PM, Adrian Chadd wrote: > On 25 September 2012 13:33, Kim Culhan wrote: >> On Tue, Sep 25, 2012 at 4:32 PM, Adrian Chadd wrote: >>> That's on -head ? >> >> Yes on 240921 > > Grr. I think I found out wh

Re: ath related panic

On Tue, Sep 25, 2012 at 4:32 PM, Adrian Chadd wrote: > That's on -head ? Yes on 240921 ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr..

ath related panic

Now seeing: panic: mutex ath0_txq1 not owned at /usr/src/sys/dev/ath/if_ath_tx.c:1320 cpuid = 1 KDB: enter: panic [ thread pid 0 tid 100045 ] Stopped at kdb_enter+0x3e: movq$0,kdb_why db> db> bt Tracing pid 0 tid 100045 td 0xfe000500d480 kdb_enter() at kdb_enter+0x3e panic() at panic+