From owner-freebsd-wireless@FreeBSD.ORG  Sun Mar 31 13:14:40 2013
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id BF528C1F;
 Sun, 31 Mar 2013 13:14:40 +0000 (UTC)
 (envelope-from jrisom@gmail.com)
Received: from mail-gg0-x236.google.com (mail-gg0-x236.google.com
 [IPv6:2607:f8b0:4002:c02::236])
 by mx1.freebsd.org (Postfix) with ESMTP id 77749CDC;
 Sun, 31 Mar 2013 13:14:40 +0000 (UTC)
Received: by mail-gg0-f182.google.com with SMTP id u2so248181ggn.27
 for <multiple recipients>; Sun, 31 Mar 2013 06:14:40 -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=gbLBWSsszMMjh1YO7dMby0ukTGBMCMSddUTh6nJJx84=;
 b=JdiVRcnOgTtG8EN3YSioRycL7obpHuOL441ECN+l8gHCtn2tyCS/dSH2lvq8EPjF2q
 OAz02dw0ZlXgvTC86g+koOwwCUx78WwqUUkGsgLvq7IC/dtm2jmkVLZHtwaEmnntA6tJ
 TFuaq0czM2NAu6gN+13jZkUAZQSZgcEYA1AIGDtv6PkgoscX2s4PA6iUW+BSMy8z6uXX
 9wWEQl6lCRF2+vtUeVoUdwkXh/vUS68JsV+I0/bum8euS7GA6bSSaX3SejuHgBsi/sak
 N5OJMZcyhVdZ7EjqQVrqxE2vHSsymu3vMCRhkSQPw6sqUinzABAeod4SAR87SRC1jqz0
 +3tA==
X-Received: by 10.236.190.200 with SMTP id e48mr6061972yhn.137.1364731583101; 
 Sun, 31 Mar 2013 05:06:23 -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 x71sm17970209yhg.17.2013.03.31.05.06.21
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Sun, 31 Mar 2013 05:06:22 -0700 (PDT)
Message-ID: <515826B9.6070509@gmail.com>
Date: Sun, 31 Mar 2013 07:06:17 -0500
From: Joshua Isom <jrisom@gmail.com>
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 <adrian@freebsd.org>
Subject: Re: ath not working after a motherboard and ram upgrade
References: <51578BAC.4090608@gmail.com>
 <CAJ-Vmo=ztG4+REqAC=x-pKkr7PpV=Wk8ZBKZ2u3HM1rwxLgOqQ@mail.gmail.com>
In-Reply-To: <CAJ-Vmo=ztG4+REqAC=x-pKkr7PpV=Wk8ZBKZ2u3HM1rwxLgOqQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "freebsd-wireless@freebsd.org" <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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Mar 2013 13:14:40 -0000

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
>