From owner-freebsd-current@FreeBSD.ORG Wed Sep 7 09:06:17 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B8821065670; Wed, 7 Sep 2011 09:06:17 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0E57C8FC21; Wed, 7 Sep 2011 09:06:16 +0000 (UTC) Received: by fxe4 with SMTP id 4so526613fxe.13 for ; Wed, 07 Sep 2011 02:06:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.24.21 with SMTP id t21mr3061981fab.24.1315385973459; Wed, 07 Sep 2011 01:59:33 -0700 (PDT) Sender: bschmidt@techwires.net Received: by 10.223.73.202 with HTTP; Wed, 7 Sep 2011 01:59:33 -0700 (PDT) X-Originating-IP: [91.46.214.235] In-Reply-To: <20110906204242.GP52426@goofy03.vnode.local> References: <09C13664-4FC0-41F3-8849-CE875B3A6CC0@vnode.se> <20110905062453.GM52426@goofy03.vnode.local> <20110906204242.GP52426@goofy03.vnode.local> Date: Wed, 7 Sep 2011 10:59:33 +0200 X-Google-Sender-Auth: 6-z4IP5JLTE2Ed_rfG3lMFaLbjY Message-ID: From: Bernhard Schmidt To: Joel Dahl Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org, current@freebsd.org Subject: Re: BETA2 panic 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: Wed, 07 Sep 2011 09:06:17 -0000 On Tue, Sep 6, 2011 at 22:42, Joel Dahl wrote: > On 05-09-2011 =A09:02, Bernhard Schmidt wrote: >> On Mon, Sep 5, 2011 at 08:24, Joel Dahl wrote: >> > On 05-09-2011 =A05:09, Adrian Chadd wrote: >> >> On 5 September 2011 01:04, Joel Dahl wrote: >> >> > Hi, >> >> > >> >> > I upgraded my laptop from BETA1 to rev. 225367 today, and now my la= ptop panics just a few minutes after booting. This is 100% reproducible, it= panics every time. >> >> > >> >> > I've got a pic with the backtrace here: http://www.vnode.se/sc/pani= c_20110904.jpg >> >> >> >> Hi, >> >> >> >> There weren't many commits between BETA1 and -HEAD in the wireless >> >> area; would you please do a binary search of the kernel revisions (no >> >> need to do full buildworlds) to find which commit broke it? >> > >> > Yes, I'll do that tonight. >> >> While doing so, can you enable at least some debugging? >> wlandebug +state >> or even better >> wlandebug 0xffffffff >> >> It smells like that something is poking the SW bmiss handler while not >> in RUN state and therefore you're hitting a KASSERT(). Question is if >> the bmiss timer isn't stopped/drained somewhere or if there is too >> excessive call. > > Exactly what in the wlandebug output are you looking for? =A0I've posted = a pic > at http://www.vnode.se/sc/panic_20110906.jpg showing what it looks like r= ight > before the panic. =A0This is with "wlandebug 0xffffffff". Thanks, so, looks like it is scanning while the panic happens. At that point it should actually never ever care about beacon misses.. this is strange, really. Can you try to comment out the call to ieee80211_beacon_miss() on line 2936 in if_iwn.c? If the panic no longer happens the issue is somewhere in the conditions before that call. > I've also installed kernels all the way back to revision 222980, but they= all > panic, which I think is somewhat odd. I think this is an issue related to iwn(4), which had its last commit prior to that. -- Bernhard