Re: ath not working after a motherboard and ram upgrade
Right; when you've booted with 4 GB there's no need to create a separate zone for 32 bit only memory, so it doesn't bother. thanks, adrian On 2 April 2013 14:31, Joshua Isom jri...@gmail.com wrote: sysctl.1.txt is right after boot, sysctl.2.txt is while failing. One thing different when using 4GB is that hw.busdma.zone0.lowaddr is 0xfff, 60 bits and not 64, but when 32GB it's 0x, 32 bits. I don't know if that has anything to do with it, but it seems strange. On 4/2/2013 1:35 AM, Adrian Chadd wrote: .. and there's been some more work in -HEAD, so please svn update first! Thanks, 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
Re: ath not working after a motherboard and ram upgrade
Ok, can you: * bring the interface down cleanly (ifconfig wlan0 down); * unload the ath driver (kldunload if_ath and kldunload if_ath_pci) * sysctl hw.busdma, and just add it to the list here? I'd like to make sure that it's freeing all the bounce buffer pages. Thanks, 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
Re: ath not working after a motherboard and ram upgrade
hw.busdma.total_bpages: 8250 hw.busdma.zone0.total_bpages: 8250 hw.busdma.zone0.free_bpages: 8250 hw.busdma.zone0.reserved_bpages: 0 hw.busdma.zone0.active_bpages: 0 hw.busdma.zone0.total_bounced: 3836 hw.busdma.zone0.total_deferred: 0 hw.busdma.zone0.lowaddr: 0x hw.busdma.zone0.alignment: 4096 They'd not freed. On 4/2/2013 5:33 PM, Adrian Chadd wrote: Ok, can you: * bring the interface down cleanly (ifconfig wlan0 down); * unload the ath driver (kldunload if_ath and kldunload if_ath_pci) * sysctl hw.busdma, and just add it to the list here? I'd like to make sure that it's freeing all the bounce buffer pages. Thanks, 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
Re: ath not working after a motherboard and ram upgrade
And it did cause problems with 8GB before IIRC. On 4/2/2013 7:28 PM, Adrian Chadd wrote: Nono, they're free. There's no active pages after an unload. Thus, they're fine. Ok, so now I need to go and audit things in more depth. Thanks! Adrian On 2 April 2013 17:24, Joshua Isom jri...@gmail.com wrote: hw.busdma.total_bpages: 8250 hw.busdma.zone0.total_bpages: 8250 hw.busdma.zone0.free_bpages: 8250 hw.busdma.zone0.reserved_bpages: 0 hw.busdma.zone0.active_bpages: 0 hw.busdma.zone0.total_bounced: 3836 hw.busdma.zone0.total_deferred: 0 hw.busdma.zone0.lowaddr: 0x hw.busdma.zone0.alignment: 4096 They'd not freed. On 4/2/2013 5:33 PM, Adrian Chadd wrote: Ok, can you: * bring the interface down cleanly (ifconfig wlan0 down); * unload the ath driver (kldunload if_ath and kldunload if_ath_pci) * sysctl hw.busdma, and just add it to the list here? I'd like to make sure that it's freeing all the bounce buffer pages. Thanks, 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
Re: ath not working after a motherboard and ram upgrade
I did get a couple bounced after pinging for a while via ssh, but only one ping packet dropped, so it should be good for anything tcp. For my system, network is more important than ram quantity, but it was nice doing a buildworld onto a ram backed file system. I just need to work out a framework to bring up a filesystem, and regularly synchronize it to disk for preservation. On 4/2/2013 7:36 PM, Adrian Chadd wrote: On 2 April 2013 17:34, Joshua Isom jri...@gmail.com wrote: And it did cause problems with 8GB before IIRC. Yeah. I need to acquire a machine with that much RAM. Maybe tomorrow. I've been meaning to buy a new PC for other wifi/radio hacking purposes. 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
Re: ath not working after a motherboard and ram upgrade
On 2 April 2013 17:44, Joshua Isom jri...@gmail.com wrote: I did get a couple bounced after pinging for a while via ssh, but only one ping packet dropped, so it should be good for anything tcp. So what, 8GB almost-but-not-quite worked? How much RAM do I need to ensure that things will break quickly? :) 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
Re: ath not working after a motherboard and ram upgrade
Right now I'm at 62 bpages bounced, with it running in a loop every second listing hw.busdma. Right now it's half an hour of uptime, and when I did 4500 pings, I lost one packet. Quickly's relative. I mainly use ssh to access my FreeBSD machine, I don't recall the last time I ran X, which kind of pissed me off that I had to buy a video card for a console when the monitor's always off. Twelve gigs lost pretty fast, I'll try 9 to see if 8's a magic number. On 4/2/2013 7:46 PM, Adrian Chadd wrote: On 2 April 2013 17:44, Joshua Isom jri...@gmail.com wrote: I did get a couple bounced after pinging for a while via ssh, but only one ping packet dropped, so it should be good for anything tcp. So what, 8GB almost-but-not-quite worked? How much RAM do I need to ensure that things will break quickly? :) 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
Re: ath not working after a motherboard and ram upgrade
But this really will be interesting. It seems to be fine at 8GB of ram, not just at 4GB. I'm not getting any dma issues or dropped packets so far. But booting with 12GB will cause problems. On 4/2/2013 7:28 PM, Adrian Chadd wrote: Nono, they're free. There's no active pages after an unload. Thus, they're fine. Ok, so now I need to go and audit things in more depth. Thanks! Adrian On 2 April 2013 17:24, Joshua Isom jri...@gmail.com wrote: hw.busdma.total_bpages: 8250 hw.busdma.zone0.total_bpages: 8250 hw.busdma.zone0.free_bpages: 8250 hw.busdma.zone0.reserved_bpages: 0 hw.busdma.zone0.active_bpages: 0 hw.busdma.zone0.total_bounced: 3836 hw.busdma.zone0.total_deferred: 0 hw.busdma.zone0.lowaddr: 0x hw.busdma.zone0.alignment: 4096 They'd not freed. On 4/2/2013 5:33 PM, Adrian Chadd wrote: Ok, can you: * bring the interface down cleanly (ifconfig wlan0 down); * unload the ath driver (kldunload if_ath and kldunload if_ath_pci) * sysctl hw.busdma, and just add it to the list here? I'd like to make sure that it's freeing all the bounce buffer pages. Thanks, 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
Re: ath not working after a motherboard and ram upgrade
On 2 April 2013 17:33, Joshua Isom jri...@gmail.com wrote: But this really will be interesting. It seems to be fine at 8GB of ram, not just at 4GB. I'm not getting any dma issues or dropped packets so far. But booting with 12GB will cause problems. Chances are at 8GB of RAM it's just not bouncing a _lot_. 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
Re: ath not working after a motherboard and ram upgrade
On 2 April 2013 18:13, Joshua Isom jri...@gmail.com wrote: I went half an hour being ok, and 12GB was dropping TCP connections in five minutes. I'm estimating a little, but it was unusable in just a little time. Using 10GB seems fine, but get's a lot bounced. The connections stable and responsive with just occasional packet loss, but bounced is 6307 right now. Bouncing is fine. Why bouncing is broken in the ath driver, I don't yet know. Sounds like I need to acquire a machine with 32GB RAM. Sigh. 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
Re: ath not working after a motherboard and ram upgrade
So, can you test end-to-end pings? With full memory booted up? What I'd like to try and do is narrow down whether it's a TX or RX (or both.) Do you have control over something on the other end? Can you tcpdump the wifi interface and see if it's pings, pongs, or both being disabled? Also, can you disable 11n and see if you end up with the same behaviour? ifconfig wlan0 -ampdu, before you run wpa_supplicant. Thanks, 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
Re: [rft] ar9300 HAL updated
On 1 April 2013 08:44, Raphael Kubo da Costa rak...@freebsd.org wrote: On a side note: this card is also supposed to provide Bluetooth support, right? Is any of your work going to help with that as well? I forget what the deal is there. I think it'll work out of the box on AR9485, but the coexistence won't work. So you'll get packet loss form both sides. I have no ETA on including all the bluetooth coexistence, sorry. 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
