Date: Fri, 26 Aug 2011 05:11:44 -0700 From: Edgar Martinez <emartinez@kbcnetworks.com> To: Adrian Chadd <adrian@freebsd.org> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: RE: XR9 w 8.2 Stable Message-ID: <957EB052144AA64AB39F7AB26878320101215E9CC6@VA3DIAXVS881.RED001.local> In-Reply-To: <CAJ-Vmongi9ojDfjLBCKJtB_A56BRc5ZKUbgV5kv3-vSCMqpKJA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
If interface is up and running, and bgscan was disabled, then renabled, no scanning takes place. If interface is up and configured, and ifconfig wlan0 scan is sent, no scanning is taking place. Pretty much you have to have the interface not configured for anything, then you can do a scan up and get results. 8.2 Stable -----Original Message----- From: adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] On Behalf Of Adrian Chadd Sent: Friday, August 26, 2011 4:20 AM To: Edgar Martinez Cc: freebsd-wireless@freebsd.org Subject: Re: XR9 w 8.2 Stable (re-cc'ing freebsd-wireless as it's interesting.) On 26 August 2011 19:14, Edgar Martinez <emartinez@kbcnetworks.com> wrote: > what's causing the stuck beacons you think? No idea. :) Lot's of reasons. DMA taking too long, TX engine is stuck, RX CLEAR is stuck low, the medium is too busy, calibration is taking too long, etc. > also when the ucast rate is set to 6, I notice that all nodes have a minimum latency of 17ms. > > when set to 12, they appear to work just fine. ideas? No idea? :) "6" should be an OFDM rate, same as 12. Maybe there's something going on with power calibration in the AR5212 series NICs that needs the higher rates to be used? (Since the earlier nics use PAPRD test frames to calibrate the output TX.) Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?957EB052144AA64AB39F7AB26878320101215E9CC6>