Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 1 Jan 2011 10:47:21 -0800
From:      Steve Kargl <sgk@troutmask.apl.washington.edu>
To:        Bernhard Schmidt <bschmidt@freebsd.org>
Cc:        freebsd-current@freebsd.org, Etienne Robillard <erob@gthcfoundation.org>
Subject:   Re: wlan/wpi are more broken than 3 weeks.
Message-ID:  <20110101184721.GA9383@troutmask.apl.washington.edu>
In-Reply-To: <201012270205.25867.bschmidt@freebsd.org>
References:  <20101226195556.GA45505@troutmask.apl.washington.edu> <201012262325.05784.bschmidt@freebsd.org> <20101227003256.GA46611@troutmask.apl.washington.edu> <201012270205.25867.bschmidt@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 27, 2010 at 02:05:25AM +0100, Bernhard Schmidt wrote:
> On Monday 27 December 2010 01:32:56 Steve Kargl wrote:
> > On Sun, Dec 26, 2010 at 11:25:05PM +0100, Bernhard Schmidt wrote:
> > > How about providing the info I asked for last time? Now that you have
> > > build the necessary options into the kernel you should be able to run
> > > with wlandebug 0xffffffff enabled.
> > 
> > Perhaps, I got busy with real life work, and perhaps,
> > I forgot you asked for this info.  In the end, /var/log/messages
> > get stuff full of
> > 
> > Dec 26 16:30:04 laptop kernel: wlan0: received beacon from
> > 00:18:e7:d4:f2:1b rssi 37 Dec 26 16:30:04 laptop kernel: wlan0: received
> > beacon from 00:18:e7:d4:f2:1b rssi 38 Dec 26 16:30:04 laptop kernel:
> > wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 Dec 26 16:30:04
> > laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 34 Dec
> > 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b
> > rssi 38 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from
> > 00:18:e7:d4:f2:1b rssi 38 Dec 26 16:30:04 laptop kernel: wlan0: received
> > beacon from 00:18:e7:d4:f2:1b rssi 41 Dec 26 16:30:04 laptop kernel:
> > wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 Dec 26 16:30:04
> > laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 32 Dec
> > 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b
> > rssi 34 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from
> > 00:18:e7:d4:f2:1b rssi 41 Dec 26 16:30:05 laptop kernel: wlan0: received
> > beacon from 00:18:e7:d4:f2:1b rssi 41 Dec 26 16:30:05 laptop kernel:
> > wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 Dec 26 16:30:05
> > laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 37 Dec
> > 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b
> > rssi 40 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from
> > 00:18:e7:d4:f2:1b rssi 40 Dec 26 16:30:05 laptop kernel: wlan0: received
> > beacon from 00:18:e7:d4:f2:1b rssi 32 Dec 26 16:30:05 laptop kernel:
> > wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 35 Dec 26 16:30:05
> > laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40
> > 
> > because apparently this message isn't rate limited.  So, perhaps, this
> > is the problem?
> 
> I don't think so, those messages are usually an indicator for a successful 
> connection. AP sends those as a 'hello, i'm still here' kinda thing. You 
> should be able to supress those with 'wlandebug 0xffffffff -dumppkts'.
> 
> If you can get debug output while the UPs/DOWNs happen, that would help a lot.
> 

Sorry about the delay.  The laptop has been in Windows land for the last week.
I finally have a log where the interface is going UP/DOWN and have wlandebug
in effect.  It's 220KB.  You can find it at 

http://troutmask.apl.washington.edu/~kargl/wlan0.msg

-- 
Steve



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