From owner-freebsd-current@FreeBSD.ORG  Sat Feb  7 03:15:16 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 9D41B106564A
	for <freebsd-current@freebsd.org>; Sat,  7 Feb 2009 03:15:16 +0000 (UTC)
	(envelope-from llc2w@virginia.edu)
Received: from fork2.mail.virginia.edu (fork2.mail.Virginia.EDU
	[128.143.2.192])
	by mx1.freebsd.org (Postfix) with ESMTP id 5F5368FC0A
	for <freebsd-current@freebsd.org>; Sat,  7 Feb 2009 03:15:16 +0000 (UTC)
	(envelope-from llc2w@virginia.edu)
Received: from localhost (localhost [127.0.0.1])
	by fork2.mail.virginia.edu (Postfix) with ESMTP id AA1BF1BF9F;
	Fri,  6 Feb 2009 22:15:15 -0500 (EST)
Received: from fork2.mail.virginia.edu ([127.0.0.1])
	by localhost (fork2.mail.virginia.edu [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 11941-02; Fri,  6 Feb 2009 22:15:15 -0500 (EST)
Received: from mail-gx0-f16.google.com (mail-gx0-f16.google.com
	[209.85.217.16])
	by fork2.mail.virginia.edu (Postfix) with ESMTP id 815601BF90;
	Fri,  6 Feb 2009 22:15:15 -0500 (EST)
Received: by mail-gx0-f16.google.com with SMTP id 9so1166760gxk.0
	for <multiple recipients>; Fri, 06 Feb 2009 19:15:15 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.193.1 with SMTP id q1mr1727139qbf.16.1233976514964; Fri, 06 
	Feb 2009 19:15:14 -0800 (PST)
In-Reply-To: <498CF81F.2090105@freebsd.org>
References: <792298050902061142k33f35be7sb19d566835e796ad@mail.gmail.com>
	<498CF81F.2090105@freebsd.org>
Date: Fri, 6 Feb 2009 22:15:14 -0500
Message-ID: <792298050902061915h2c345483pe0a30f7d524e7953@mail.gmail.com>
From: L Campbell <llc2w@virginia.edu>
To: Sam Leffler <sam@freebsd.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-UVA-Virus-Scanned: by amavisd-new at fork2.mail.virginia.edu
Cc: freebsd-current@freebsd.org
Subject: Re: iwi broken? reproducible crash :(
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Feb 2009 03:15:16 -0000

On Fri, Feb 6, 2009 at 9:55 PM, Sam Leffler <sam@freebsd.org> wrote:
> Looks like a race in referencing the bss node and a state change.  I haven't
> looked at iwi forever so can't recall how it's supposed to work.  You might
> enable net80211 state machine debug msgs to see if it provides more info:
> wlandebug state.

Awesome, I'll give that a shot on Monday and report back with the
results -- I can't seem to reproduce the panic on my home network.

In the meanwhile, I found an old Atheros-based WPC54G lying around
which will get me through the weekend.

Thanks for the help :3