On 3/27/2013 6:53 PM, Adrian Chadd wrote:
.. this has me worried. This would've caused a panic before. The next
time it happens, but before you disconnect, please do this:
sysctl dev.ath.0.txagg=1
I'd like to see if any other TX queue has a frame hanging around in it
that hasn't been completed.
I had syslogd pipe the output to a perl script to set the sysctl, not
ideal but effective I hope. I've got two today.
Mar 28 07:03:01 jri kernel: ath0: ath_edma_tx_processq: Q1: empty?
Mar 28 07:03:02 jri kernel: no tx bufs (empty list): 0
Mar 28 07:03:02 jri kernel: no tx bufs (was busy): 0
Mar 28 07:03:02 jri kernel: aggr single packet: 481
Mar 28 07:03:02 jri kernel: aggr single packet w/ BAW closed: 0
Mar 28 07:03:02 jri kernel: aggr non-baw packet: 20
Mar 28 07:03:02 jri kernel: aggr aggregate packet: 1278
Mar 28 07:03:02 jri kernel: aggr single packet low hwq: 13087
Mar 28 07:03:02 jri kernel: aggr single packet RTS aggr limited: 0
Mar 28 07:03:02 jri kernel: aggr sched, no work: 849
Mar 28 07:03:02 jri kernel: 0: 0 1: 0 2: 318 3:
221
Mar 28 07:03:02 jri kernel: 4: 331 5: 50 6: 221 7:
57
Mar 28 07:03:02 jri kernel: 8: 35 9: 22 10: 13 11:
1
Mar 28 07:03:02 jri kernel: 12: 5 13: 0 14: 1 15:
0
Mar 28 07:03:02 jri kernel: 16: 2 17: 0 18: 0 19:
1
Mar 28 07:03:02 jri kernel: 20: 0 21: 0 22: 0 23:
0
Mar 28 07:03:02 jri kernel: 24: 0 25: 0 26: 0 27:
0
Mar 28 07:03:02 jri kernel: 28: 0 29: 0 30: 0 31:
0
Mar 28 07:03:02 jri kernel: 32: 0 33: 0 34: 0 35:
0
Mar 28 07:03:02 jri kernel: 36: 0 37: 0 38: 0 39:
0
Mar 28 07:03:02 jri kernel: 40: 0 41: 0 42: 0 43:
0
Mar 28 07:03:02 jri kernel: 44: 0 45: 0 46: 0 47:
0
Mar 28 07:03:02 jri kernel: 48: 0 49: 0 50: 0 51:
0
Mar 28 07:03:02 jri kernel: 52: 0 53: 0 54: 0 55:
0
Mar 28 07:03:02 jri kernel: 56: 0 57: 0 58: 0 59:
0
Mar 28 07:03:02 jri kernel: 60: 0 61: 0 62: 0 63:
0
Mar 28 07:03:02 jri kernel:
Mar 28 07:03:02 jri kernel: HW TXQ 0: axq_depth=0, axq_aggr_depth=0,
axq_fifo_depth=0, holdingbf=0
Mar 28 07:03:02 jri kernel: HW TXQ 1: axq_depth=0, axq_aggr_depth=0,
axq_fifo_depth=0, holdingbf=0
Mar 28 07:03:02 jri kernel: HW TXQ 2: axq_depth=0, axq_aggr_depth=0,
axq_fifo_depth=0, holdingbf=0
Mar 28 07:03:02 jri kernel: HW TXQ 3: axq_depth=0, axq_aggr_depth=0,
axq_fifo_depth=0, holdingbf=0
Mar 28 07:03:02 jri kernel: HW TXQ 8: axq_depth=0, axq_aggr_depth=0,
axq_fifo_depth=0, holdingbf=0
Mar 28 07:03:02 jri kernel: Total TX buffers: 512; Total TX buffers busy: 0
(512)
Mar 28 07:03:02 jri kernel: Total mgmt TX buffers: 32; Total mgmt TX buffers
busy: 0
Mar 28 07:03:02 jri kernel: 0: fifolen: 16/16; head=0; tail=0
Mar 28 07:03:02 jri kernel: 1: fifolen: 128/128; head=45; tail=45
Mar 28 07:03:02 jri kernel: Total RX buffers in free list: 368 buffers
Mar 28 07:03:05 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0
Mar 28 07:38:13 jri kernel: ath0: ath_edma_tx_processq: Q1: empty?
Mar 28 07:38:14 jri kernel: no tx bufs (empty list): 0
Mar 28 07:38:14 jri kernel: no tx bufs (was busy): 0
Mar 28 07:38:14 jri kernel: aggr single packet: 481
Mar 28 07:38:14 jri kernel: aggr single packet w/ BAW closed: 0
Mar 28 07:38:14 jri kernel: aggr non-baw packet: 20
Mar 28 07:38:14 jri kernel: aggr aggregate packet: 1278
Mar 28 07:38:14 jri kernel: aggr single packet low hwq: 13087
Mar 28 07:38:14 jri kernel: aggr single packet RTS aggr limited: 0
Mar 28 07:38:14 jri kernel: aggr sched, no work: 849
Mar 28 07:38:14 jri kernel: 0: 0 1: 0 2: 318 3:
221
Mar 28 07:38:14 jri kernel: 4: 331 5: 50 6: 221 7:
57
Mar 28 07:38:14 jri kernel: 8: 35 9: 22 10: 13 11:
1
Mar 28 07:38:14 jri kernel: 12: 5 13: 0 14: 1 15:
0
Mar 28 07:38:14 jri kernel: 16: 2 17: 0 18: 0 19:
1
Mar 28 07:38:14 jri kernel: 20: 0 21: 0 22: 0 23:
0
Mar 28 07:38:14 jri kernel: 24: 0 25: 0 26: 0 27:
0
Mar 28 07:38:14 jri kernel: 28: 0 29: 0 30: 0 31:
0
Mar 28 07:38:14 jri kernel: 32: 0 33: 0 34: 0 35:
0
Mar 28 07:38:14 jri kernel: 36: 0 37: 0 38: 0 39:
0
Mar 28 07:38:14 jri kernel: 40: 0 41: 0 42: 0 43:
0
Mar 28 07:38:14 jri kernel: 44: 0 45: 0 46: 0 47:
0
Mar 28 07:38:14 jri kernel: 48: 0 49: 0 50: 0 51:
0
Mar 28 07:38:14 jri kernel: 52: 0 53: 0 54: 0 55:
0
Mar 28 07:38:14 jri kernel: 56: 0 57: 0 58: 0 59:
0
Mar 28 07:38:14 jri kernel: 60: 0 61: 0 62: 0 63:
0
Mar 28 07:38:14 jri kernel:
Mar 28 07:38:14 jri kernel: HW TXQ 0: axq_depth=0, axq_aggr_depth=0,
axq_fifo_depth=0, holdingbf=0
Mar 28 07:38:14 jri kernel: HW TXQ 1: axq_depth=0, axq_aggr_depth=0,
axq_fifo_depth=0, holdingbf=0
Mar 28 07:38:14 jri kernel: HW TXQ 2: axq_depth=0, axq_aggr_depth=0,
axq_fifo_depth=0, holdingbf=0
Mar 28 07:38:14 jri kernel: HW TXQ 3: axq_depth=0, axq_aggr_depth=0,
axq_fifo_depth=0, holdingbf=0
Mar 28 07:38:14 jri kernel: HW TXQ 8: axq_depth=0, axq_aggr_depth=0,
axq_fifo_depth=0, holdingbf=0
Mar 28 07:38:14 jri kernel: Total TX buffers: 512; Total TX buffers busy: 0
(512)
Mar 28 07:38:14 jri kernel: Total mgmt TX buffers: 32; Total mgmt TX buffers
busy: 0
Mar 28 07:38:14 jri kernel: 0: fifolen: 16/16; head=0; tail=0
Mar 28 07:38:14 jri kernel: 1: fifolen: 128/128; head=27; tail=27
Mar 28 07:38:14 jri kernel: Total RX buffers in free list: 368 buffers
Mar 28 07:38:32 jri kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0
Also, whats the output if 'ifconfig wlan0 list sta'? I wonder what the
RSSI is and I do wonder why you see frequent disconnects.
My RSSI tends to be between 7.0 and 8.5, I don't think I've seen 9.0
yet. I'm still working on improving my signal but at least for right
now it's stable enough to be usable. Try making a little Faraday cage
around your router, or put openwrt on it and drop your signal down for
your connection. Don't forget to add a dozen random wifi APs and devices.
[jri:/var/log] jisom% ifconfig wlan0 list sta
ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG
c0:c1:c0:35:19:88 1 1 26M 8.5 0 1865 29712 EP AQEHTRS RSN HTCAP
WPS WME
Thanks,
Adrian
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "[email protected]"
