Date: Wed, 03 Apr 2013 20:27:23 -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: <515CD6FB.3080502@gmail.com> In-Reply-To: <CAJ-VmomVRi72GUnG0cGanehY%2BGp-pyPze8qO7qXEj%2BUQhHy15Q@mail.gmail.com> References: <515892C4.1060002@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> <515CD0A3.2020204@gmail.com> <CAJ-VmomVRi72GUnG0cGanehY%2BGp-pyPze8qO7qXEj%2BUQhHy15Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?515CD6FB.3080502>