From owner-freebsd-current@FreeBSD.ORG Mon Dec 27 00:32:57 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 267781065673; Mon, 27 Dec 2010 00:32:57 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 01ABF8FC12; Mon, 27 Dec 2010 00:32:56 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.4/8.14.4) with ESMTP id oBR0WuhG046629; Sun, 26 Dec 2010 16:32:56 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.4/8.14.4/Submit) id oBR0WuRI046628; Sun, 26 Dec 2010 16:32:56 -0800 (PST) (envelope-from sgk) Date: Sun, 26 Dec 2010 16:32:56 -0800 From: Steve Kargl To: Bernhard Schmidt Message-ID: <20101227003256.GA46611@troutmask.apl.washington.edu> References: <20101226195556.GA45505@troutmask.apl.washington.edu> <4D17B714.6040106@gthcfoundation.org> <20101226213958.GA46129@troutmask.apl.washington.edu> <201012262325.05784.bschmidt@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201012262325.05784.bschmidt@freebsd.org> User-Agent: Mutt/1.4.2.3i 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 00:32:57 -0000 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? -- Steve