From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 12:35:15 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AE28DEE3; Sun, 31 Mar 2013 12:35:15 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-gh0-f175.google.com (mail-gh0-f175.google.com [209.85.160.175]) by mx1.freebsd.org (Postfix) with ESMTP id 65CE1AB5; Sun, 31 Mar 2013 12:35:15 +0000 (UTC) Received: by mail-gh0-f175.google.com with SMTP id f1so245190ghb.20 for ; Sun, 31 Mar 2013 05:35:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=s90HMHXUMX8vvsw/3tH0iP403eDjHVvL0MxaMIBDtYY=; b=dV16HUCTOpSvRi8Sog1fycBz3pJaj/vEqZRkS85u7N73sHO77AxARXuu4gIOE3ABbV WqzQd35V95zyS2PNz1Yp4kMYjwXarXnvlfMXLd76UCwfNYyNEbNoSXewYiC9/7FZhjlV WA9SaJmN9YtziYaC2CR7s7529/5HhNA7y/Mc4qUa1h4O7c3GxAQGdwRh+FfA9pj3vi5N OEXjdRMPpsfqFNigNkccey+fkkCPa7prJhFfHh35lOPA5mXFW4JwAGVenBbkECKwBXJI 1jHNVaPVBW9vJuHaLFZsOhEuoGM06iH9U0GHYIgOFax4cc1Cceg+7gK3owhMNlXH2cj7 QfvQ== X-Received: by 10.236.26.203 with SMTP id c51mr6254477yha.89.1364733309768; Sun, 31 Mar 2013 05:35:09 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id w69sm18130883yhe.4.2013.03.31.05.35.08 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 31 Mar 2013 05:35:09 -0700 (PDT) Message-ID: <51582D78.1070100@gmail.com> Date: Sun, 31 Mar 2013 07:35:04 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <51578BAC.4090608@gmail.com> <515826B9.6070509@gmail.com> In-Reply-To: <515826B9.6070509@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Mar 2013 12:35:15 -0000 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 >>