On Wednesday, February 27, 2013 06:45:04 PM you wrote:
> These are only during probe requests, right?
> 
> 
> 
> 
> adrian
> 
> 
> On 27 February 2013 16:30, Derrick Dantavious Edwards
> 
> <dantavious...@gmail.com> wrote:
> >         Hi,
> > 
> > During recent upgrades to Current, I have been experiencing timeouts with
> > the ath0 device. These are the errors that I am receiving. Any ideas?
> > 
> > V/r
> > 
> > Derrick
> > 
> > 
> > 
> > ath0: ath_tx_tid_drain_print: norm: node 0xffffff802adf3000:
> > bf=0xffffff8001d6e000: addbaw=0, dobaw=0, seqno=0, retry=0
> > ath0: ath_tx_tid_drain_print: node 0xffffff802adf3000:
> > bf=0xffffff8001d6e000: txq[3] axq_depth=0, axq_aggr_depth=0
> > ath0: ath_tx_tid_drain_print: node 0xffffff802adf3000:
> > bf=0xffffff8001d6e000: tid txq_depth=2 hwq_depth=0, bar_wait=0,
> > isfiltered=0
> > ath0: ath_tx_tid_drain_print: node 0xffffff802adf3000: tid 16: sched=1,
> > paused=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=5
> > NODS 00:22:5f:78:b1:0a->ff:ff:ff:ff:ff:ff(ff:ff:ff:ff:ff:ff) probe_req 0M
> > 
> >  4000 0000 ffff ffff ffff 0022 5f78 b10a ffff ffff ffff 3000 0000 0108
> >  8284
> > 
> > 8b96 0c12 1824 3014 0100 000f ac04 0100 000f ac04 0100 000f ac02 0000 3204
> > 3048 606c
> > ath0: device timeout
> > ath0: ath_tx_tid_drain_print: norm: node 0xffffff80270e6000:
> > bf=0xffffff8001d6ee10: addbaw=0, dobaw=0, seqno=0, retry=0
> > ath0: ath_tx_tid_drain_print: node 0xffffff80270e6000:
> > bf=0xffffff8001d6ee10: txq[3] axq_depth=0, axq_aggr_depth=0
> > ath0: ath_tx_tid_drain_print: node 0xffffff80270e6000:
> > bf=0xffffff8001d6ee10: tid txq_depth=2 hwq_depth=0, bar_wait=0,
> > isfiltered=0
> > ath0: ath_tx_tid_drain_print: node 0xffffff80270e6000: tid 16: sched=1,
> > paused=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=5
> > NODS 00:22:5f:78:b1:0a->ff:ff:ff:ff:ff:ff(ff:ff:ff:ff:ff:ff) probe_req 0M
> > 
> >  4000 0000 ffff ffff ffff 0022 5f78 b10a ffff ffff ffff 3000 0000 0108
> >  8284
> > 
> > 8b96 0c12 1824 3014 0100 000f ac04 0100 000f ac04 0100 000f ac02 0000 3204
> > 3048 606c
> > ath0: device timeout
> > 
> > FreeBSD 10.0-CURRENT #0 r247397: Wed Feb 27 08:53:24 EST 2013
> > 
> > ath0@pci0:2:0:0:        class=0x028000 card=0x3041103c chip=0x002a168c
> > rev=0x01 hdr=0x00
> > 
> >     vendor     = 'Atheros Communications Inc.'
> >     device     = 'AR928X Wireless Network Adapter (PCI-Express)'
> >     class      = network
> > 
> > _______________________________________________
> > freebsd-wireless@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> > To unsubscribe, send any mail to
> > "freebsd-wireless-unsubscr...@freebsd.org"

    Yes. When I start the system, I get those messages. Wireless Link fails to 
establish thus causing all services requring link to fail....ie NFS . Soon 
after I am at the command prompt or GUI, I can ping hosts however, I have to 
/etc/rc.d/mountlate to get remote filesystems connected. Thanks for your 
assistance.

V/r

Derrick

_______________________________________________
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Reply via email to