I spoke too soon, it can still degrade, it's just takes longer to happen. This is with `ping -i .25 192.168.1.1`

64 bytes from 192.168.1.1: icmp_seq=743 ttl=64 time=1.595 ms
64 bytes from 192.168.1.1: icmp_seq=765 ttl=64 time=1.696 ms
64 bytes from 192.168.1.1: icmp_seq=771 ttl=64 time=3.118 ms
64 bytes from 192.168.1.1: icmp_seq=772 ttl=64 time=1.573 ms
64 bytes from 192.168.1.1: icmp_seq=778 ttl=64 time=1.796 ms
64 bytes from 192.168.1.1: icmp_seq=779 ttl=64 time=9222.495 ms
64 bytes from 192.168.1.1: icmp_seq=780 ttl=64 time=8967.619 ms
64 bytes from 192.168.1.1: icmp_seq=781 ttl=64 time=8701.003 ms
64 bytes from 192.168.1.1: icmp_seq=782 ttl=64 time=8434.659 ms


64 bytes from 192.168.1.1: icmp_seq=865 ttl=64 time=2.744 ms
64 bytes from 192.168.1.1: icmp_seq=871 ttl=64 time=1.548 ms
64 bytes from 192.168.1.1: icmp_seq=872 ttl=64 time=4.107 ms
64 bytes from 192.168.1.1: icmp_seq=873 ttl=64 time=1.570 ms
64 bytes from 192.168.1.1: icmp_seq=876 ttl=64 time=1.534 ms
64 bytes from 192.168.1.1: icmp_seq=900 ttl=64 time=1.530 ms
64 bytes from 192.168.1.1: icmp_seq=903 ttl=64 time=1.520 ms
64 bytes from 192.168.1.1: icmp_seq=904 ttl=64 time=6964.209 ms
64 bytes from 192.168.1.1: icmp_seq=905 ttl=64 time=6697.696 ms
64 bytes from 192.168.1.1: icmp_seq=906 ttl=64 time=7045.536 ms
64 bytes from 192.168.1.1: icmp_seq=907 ttl=64 time=6790.528 ms
64 bytes from 192.168.1.1: icmp_seq=908 ttl=64 time=6524.030 ms

It'll be very stable, ping times of less than 2ms, then dropped packets and jumping up to high ping times. My messages file doesn't report anything noticeable other than losing network and regaining.

On 3/31/2013 7:06 AM, Joshua Isom wrote:
If I drop down to one 8Gb stick, and I don't have other wifi devices
near causing interference, I can get a reliable connection and low loss.
  If I have 16Gb, I can get about a minute or two of decent ping times
before it degrades to multi-second pings of the router.  Even at 8Gb,
it's not guaranteed on boot, but rebooting does seem to fix it.  At
16Gb, I tried two different sticks just to see if maybe it was one bad
chip but it didn't change it.  That means it's probably an address
conflict, or cache size issue, right?

On 3/31/2013 1:25 AM, Adrian Chadd wrote:
does downgrading the motherboard/ram fix it?

You were already running 64 bit, right? What if you just boot with 2gb
of ram?




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"

Reply via email to