From owner-freebsd-current@FreeBSD.ORG Mon Dec 27 01:07:03 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C309B106566B for ; Mon, 27 Dec 2010 01:07:03 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 542A68FC18 for ; Mon, 27 Dec 2010 01:07:02 +0000 (UTC) Received: by bwz12 with SMTP id 12so2073444bwz.13 for ; Sun, 26 Dec 2010 17:07:02 -0800 (PST) Received: by 10.204.71.20 with SMTP id f20mr9956844bkj.139.1293412021789; Sun, 26 Dec 2010 17:07:01 -0800 (PST) Received: from julie.lab.techwires.net (dslb-094-217-135-235.pools.arcor-ip.net [94.217.135.235]) by mx.google.com with ESMTPS id v25sm7421979bkt.18.2010.12.26.17.06.59 (version=SSLv3 cipher=RC4-MD5); Sun, 26 Dec 2010 17:07:00 -0800 (PST) Sender: Bernhard Schmidt From: Bernhard Schmidt To: Steve Kargl Date: Mon, 27 Dec 2010 02:05:25 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.1-RELEASE; KDE/4.5.4; amd64; ; ) References: <20101226195556.GA45505@troutmask.apl.washington.edu> <201012262325.05784.bschmidt@freebsd.org> <20101227003256.GA46611@troutmask.apl.washington.edu> In-Reply-To: <20101227003256.GA46611@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201012270205.25867.bschmidt@freebsd.org> Cc: freebsd-current@freebsd.org, Etienne Robillard Subject: Re: wlan/wpi are more broken than 3 weeks. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2010 01:07:03 -0000 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. -- Bernhard