On 3 April 2013 17:22, Joshua Isom <jri...@gmail.com> wrote: > I added -ampdu to rc.conf and it connected to the network, but still dropped > packets. I'm not getting the network to work when I try it manually after
Ok. So it's not kooky stuff with aggregation handling. That said, you're already running a far-away network, so a lack of aggregation means that you're not doing software retried packets. :-) > boot. It could be me though, or something else wrong or not working > properly. It's the same kernel as before except the patch, and that was the CAn you please dump out the contents of hw.busdma after it's run and failed for a while? Then ifconfig wlan0 ; kldunload if_ath_pci ; kldload if_ath ; sysctl hw.busdma again. I'd like to see if it's leaking bounce buffers now. > only time I was getting those messages. I checked hw.ath before, and after, > there's no difference. So you're still seeing the FIFO allocation failures with this patch? The reason why RX FIFO allocations would fail here is because the bounce buffer allocation is failing. I doubt the mbuf allocation is failing. > hw.ath.longcal: 30 > hw.ath.shortcal: 100 > hw.ath.resetcal: 1200 > hw.ath.anical: 100 > hw.ath.rxbuf: 512 > hw.ath.txbuf: 512 > hw.ath.txbuf_mgmt: 32 > hw.ath.bstuck: 4 > hw.ath.debug: 0 > hw.ath.hal.debug: 0 Yup, that's correct. Adrian _______________________________________________ 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"
