From owner-freebsd-wireless@FreeBSD.ORG  Thu Apr  4 01:27:26 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 D0C556D8;
 Thu,  4 Apr 2013 01:27:26 +0000 (UTC)
 (envelope-from jrisom@gmail.com)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com
 [IPv6:2607:f8b0:4003:c01::22e])
 by mx1.freebsd.org (Postfix) with ESMTP id 5BF16E1C;
 Thu,  4 Apr 2013 01:27:26 +0000 (UTC)
Received: by mail-ob0-f174.google.com with SMTP id 16so2064356obc.33
 for <multiple recipients>; Wed, 03 Apr 2013 18:27:25 -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=S4ypOuu8lCTEj89XPU19B3Pi2ZF0KAz7eA+OoH2c/3M=;
 b=K1/Wf6mXpd4ODU0BfR8KleaPHZ+2K4XtUDu58G8v+uuQ9xjO2eW0PEm9MeGex8bCpp
 8hkTN2V7zKbyx0SGra8THbo0wnZ6hSUBV2H/8VbXKoMdfh0BB+V7p/KZf5Uk2K1FTUX+
 E+Mh/EBQ3Q1/CQku5fF4YOQQyKO6TKToGVmPJWwyFFwF6vjVieZS0xRlCfz9TAAD+CG4
 AdwuJ28IRFXu5I3etwPfSljquxWaDaYJdHvQmm9cGNjANFMU4F38wcsWEB66vKWsmO5i
 5ADT1kfZrEMvozAm+F/z2m2jjV8ti0WOOZ45MZVWvvXQeSq70sctAdiseSjmDd8yyu1b
 wp/Q==
X-Received: by 10.182.66.11 with SMTP id b11mr2630995obt.62.1365038845282;
 Wed, 03 Apr 2013 18:27:25 -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 t9sm4303414obk.13.2013.04.03.18.27.23
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Wed, 03 Apr 2013 18:27:24 -0700 (PDT)
Message-ID: <515CD6FB.3080502@gmail.com>
Date: Wed, 03 Apr 2013 20:27:23 -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: <515892C4.1060002@gmail.com> <515B4E16.3050901@gmail.com>
 <CAJ-VmonrJNAm55zMY2DifygAW8x4iGfPV_WntMXyQVbmRVbOmg@mail.gmail.com>
 <CAJ-VmokwtNiZtN7t96wc9E-fv-0j+yhd0jcJO4ZWjC0HCM+wPg@mail.gmail.com>
 <515B76A6.7080804@gmail.com>
 <CAJ-Vmon0S2Xm4tnkYPNAHRvODe_Mp=M5CvRrQH0Nt-W_PbEVew@mail.gmail.com>
 <515B78C2.20609@gmail.com>
 <CAJ-VmonSzyxfY0J8V4-LWaQneOeh7SD=EvHxxKE-yTXbhoBN_g@mail.gmail.com>
 <515B8233.9000603@gmail.com>
 <CAJ-Vmok_xdR4RrWv6RR1c2D4TYPHeoxsJi60m5kAjLUhLNVBzg@mail.gmail.com>
 <515B8914.8030303@gmail.com>
 <CAJ-VmokpdvgDj2+cW4ZfoP0-YCDGqZMBpwvZ_tRb=NE4GeNWPg@mail.gmail.com>
 <CAJ-VmomDUGyuNS2kjHWS_NJZdUXb5ki1-ueAh_+iv67q1bccXQ@mail.gmail.com>
 <515CAA36.70002@gmail.com>
 <CAJ-Vmok8+OiYtciugqFFzdzSm+ayT9a1SXkuM-2iAj2AEbhLFg@mail.gmail.com>
 <515CC7C3.3070608@gmail.com>
 <CAJ-VmonpLDWT6BK8sk5xdd+ugpNknrCQumghbSJZ63WYN5rnUg@mail.gmail.com>
 <515CD0A3.2020204@gmail.com>
 <CAJ-VmomVRi72GUnG0cGanehY+Gp-pyPze8qO7qXEj+UQhHy15Q@mail.gmail.com>
In-Reply-To: <CAJ-VmomVRi72GUnG0cGanehY+Gp-pyPze8qO7qXEj+UQhHy15Q@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: Thu, 04 Apr 2013 01:27:26 -0000

I'm trying again at 11.5GB, and it's working fine so far.  At 12GB it 
fails, but has an early period of tcp usability for ssh's needs.  It 
used to failed at 6GB after I first started messing with hw.physmem.

On 4/3/2013 8:04 PM, Adrian Chadd wrote:
> .. well, I can reproduce this particular nightmare on my i386 box. I'm
> running a kernel where I've reduced the bus size down quite
> signifcantly for ath(4).
>
>
>
> Adrian
>