Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 03 Apr 2013 20:00:19 -0500
From:      Joshua Isom <jrisom@gmail.com>
To:        Adrian Chadd <adrian@freebsd.org>
Cc:        "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>
Subject:   Re: ath not working after a motherboard and ram upgrade
Message-ID:  <515CD0A3.2020204@gmail.com>
In-Reply-To: <CAJ-VmonpLDWT6BK8sk5xdd%2BugpNknrCQumghbSJZ63WYN5rnUg@mail.gmail.com>
References:  <515892C4.1060002@gmail.com> <CAJ-Vmok%2BC%2Bet_b-8ZWQyDTebFBVwidQrn6U0J1eyB%2B%2BwyxDAWA@mail.gmail.com> <515B4E16.3050901@gmail.com> <CAJ-VmonrJNAm55zMY2DifygAW8x4iGfPV_WntMXyQVbmRVbOmg@mail.gmail.com> <CAJ-VmokwtNiZtN7t96wc9E-fv-0j%2Byhd0jcJO4ZWjC0HCM%2BwPg@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%2BcW4ZfoP0-YCDGqZMBpwvZ_tRb=NE4GeNWPg@mail.gmail.com> <CAJ-VmomDUGyuNS2kjHWS_NJZdUXb5ki1-ueAh_%2Biv67q1bccXQ@mail.gmail.com> <515CAA36.70002@gmail.com> <CAJ-Vmok8%2BOiYtciugqFFzdzSm%2BayT9a1SXkuM-2iAj2AEbhLFg@mail.gmail.com> <515CC7C3.3070608@gmail.com> <CAJ-VmonpLDWT6BK8sk5xdd%2BugpNknrCQumghbSJZ63WYN5rnUg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?515CD0A3.2020204>