Re: BETA2 panic

On 07-09-2011 10:59, Bernhard Schmidt wrote:
> On Tue, Sep 6, 2011 at 22:42, Joel Dahl <joel_at_vnode.se> wrote:
> > On 05-09-2011  9:02, Bernhard Schmidt wrote:
> >> On Mon, Sep 5, 2011 at 08:24, Joel Dahl <joel_at_vnode.se> wrote:
> >> > On 05-09-2011  5:09, Adrian Chadd wrote:
> >> >> On 5 September 2011 01:04, Joel Dahl <joel_at_vnode.se> wrote:
> >> >> > Hi,
> >> >> >
> >> >> > I upgraded my laptop from BETA1 to rev. 225367 today, and now my laptop 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/panic_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?  I've posted a pic
> > at http://www.vnode.se/sc/panic_20110906.jpg showing what it looks like right
> > before the panic.  This 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.

Hm, this is with bwn(4), not iwn(4). :)

-- 
Joel