From owner-freebsd-wireless@FreeBSD.ORG  Thu Apr  4 01:00:22 2013
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
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 6C1EA44B;
 Thu,  4 Apr 2013 01:00:22 +0000 (UTC)
 (envelope-from jrisom@gmail.com)
Received: from mail-oa0-f53.google.com (mail-oa0-f53.google.com
 [209.85.219.53]) by mx1.freebsd.org (Postfix) with ESMTP id 24A29D50;
 Thu,  4 Apr 2013 01:00:21 +0000 (UTC)
Received: by mail-oa0-f53.google.com with SMTP id m17so2206998oag.26
 for <multiple recipients>; Wed, 03 Apr 2013 18:00:21 -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=MJSR4X4ei5lDKRhfXCi+5htPKXjwr3/jUsESpdbVEwE=;
 b=rFf1a6c85/NO59R8pE1ZT3ELwxyp00ZSX8QDBEqSSBqn0NdIhOllhrMirmWnZI8gsa
 cYjlPKpLWj8cWckfA8ZOIkAmBtnUgv5r4v7XR6ZNAdv4XtKjMm3e+XhnY4gK72h9arXr
 QCSchX3GetUQmjAkLY7NqY4ORNleXlO/3cUxWsB7LN63Zc4F5Lfku1ZwOLFdtFEIs2LA
 TMQIHvlmk6cr4thV6ebW42BKDn+58Y6kU1caWPMSHOdnP3rfByuLcz5YNRAqNV9YMwDw
 kivHgN2U2bw0wWjKs3ZIJi5hLvAd5HKXzWo0VnjD6gBY0wd5s24YzXSew1bkf9msPe9q
 HmjA==
X-Received: by 10.182.45.231 with SMTP id q7mr2650787obm.58.1365037221267;
 Wed, 03 Apr 2013 18:00:21 -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 be1sm4210611obb.11.2013.04.03.18.00.20
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Wed, 03 Apr 2013 18:00:20 -0700 (PDT)
Message-ID: <515CD0A3.2020204@gmail.com>
Date: Wed, 03 Apr 2013 20:00:19 -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>
 <CAJ-Vmok+C+et_b-8ZWQyDTebFBVwidQrn6U0J1eyB++wyxDAWA@mail.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>
In-Reply-To: <CAJ-VmonpLDWT6BK8sk5xdd+ugpNknrCQumghbSJZ63WYN5rnUg@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:00:22 -0000

It wasn't ran with -ampdu, but I guess that doesn't matter now.

hw.busdma.total_bpages: 8250
hw.busdma.zone0.total_bpages: 8250
hw.busdma.zone0.free_bpages: 8213
hw.busdma.zone0.reserved_bpages: 0
hw.busdma.zone0.active_bpages: 37
hw.busdma.zone0.total_bounced: 3275
hw.busdma.zone0.total_deferred: 0
hw.busdma.zone0.lowaddr: 0xffffffff
hw.busdma.zone0.alignment: 4096
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
         ether 64:70:02:18:6d:95
         inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255
         inet 192.168.1.6 netmask 0xffffff00 broadcast 192.168.1.255
         nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
         media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
         status: associated
         ssid foobar channel 1 (2412 MHz 11g ht/20) bssid c0:c1:c0:35:19:88
         regdomain 33 indoor ecm authmode WPA2/802.11i privacy ON
         deftxkey UNDEF AES-CCM 3:128-bit txpower 20 bmiss 7 scanvalid 60
         protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst
         roaming MANUAL
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: 3281
hw.busdma.zone0.total_deferred: 0
hw.busdma.zone0.lowaddr: 0xffffffff
hw.busdma.zone0.alignment: 4096

The alloc errors were with the patch, when I was trying to get the 
network up and running manually after multiuser.  I can't recall that 
I've ever gotten ath networking working after a boot without it in 
rc.conf.  I've brought it down, unloaded it, and brought it back but 
it's worked.  It might just be some random thing where if it doesn't 
have networking at boot I can't get it later.

Whatever's going on, it's odd.  And if you're going wtf, does that mean 
maybe a hardware issue?  What's linux do?  Whatever it's doing, the 
speed it fails is dependent on the amount of ram.