From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 5 07:02:14 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13AF010656D2; Mon, 5 Sep 2011 07:02:14 +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 409138FC08; Mon, 5 Sep 2011 07:02:13 +0000 (UTC) Received: by fxe4 with SMTP id 4so4261068fxe.13 for ; Mon, 05 Sep 2011 00:02:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.24.21 with SMTP id t21mr1526334fab.24.1315206132214; Mon, 05 Sep 2011 00:02:12 -0700 (PDT) Sender: bschmidt@techwires.net Received: by 10.223.73.202 with HTTP; Mon, 5 Sep 2011 00:02:12 -0700 (PDT) X-Originating-IP: [91.46.219.248] In-Reply-To: <20110905062453.GM52426@goofy03.vnode.local> References: <09C13664-4FC0-41F3-8849-CE875B3A6CC0@vnode.se> <20110905062453.GM52426@goofy03.vnode.local> Date: Mon, 5 Sep 2011 09:02:12 +0200 X-Google-Sender-Auth: asJN7gtj-uzMizLiP9fhKZpNKM4 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-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Sep 2011 07:02:14 -0000 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 lapto= p panics just a few minutes after booting. This is 100% reproducible, it pa= nics every time. >> > >> > I've got a pic with the backtrace here: http://www.vnode.se/sc/panic_2= 0110904.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. -- Bernhard