From owner-freebsd-mobile@FreeBSD.ORG  Tue Sep 23 21:11:09 2003
Return-Path: <owner-freebsd-mobile@FreeBSD.ORG>
Delivered-To: freebsd-mobile@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id BCCAC16A4B3; Tue, 23 Sep 2003 21:11:09 -0700 (PDT)
Received: from ebb.errno.com (ebb.errno.com [66.127.85.87])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id F04D443FE5; Tue, 23 Sep 2003 21:11:04 -0700 (PDT)
	(envelope-from sam@errno.com)
Received: from melange.errno.com (melange.errno.com [66.127.85.82])
	(authenticated bits=0)
	by ebb.errno.com (8.12.9/8.12.9) with ESMTP id h8O4B00x038919
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 23 Sep 2003 21:11:02 -0700 (PDT)
	(envelope-from sam@errno.com)
Date: Tue, 23 Sep 2003 21:11:00 -0700
From: Sam Leffler <sam@errno.com>
To: David Gilbert <dgilbert@dclg.ca>, freebsd-current@freebsd.org,
	freebsd-mobile@freebsd.org
Message-ID: <970409274.1064351460@melange.errno.com>
In-Reply-To: <16241.5876.725602.924641@canoe.dclg.ca>
References: <16241.5876.725602.924641@canoe.dclg.ca>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: wi hostap recently screwed.
X-BeenThere: freebsd-mobile@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Mobile computing with FreeBSD <freebsd-mobile.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-mobile>
List-Post: <mailto:freebsd-mobile@freebsd.org>
List-Help: <mailto:freebsd-mobile-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Sep 2003 04:11:09 -0000

> Obviously I don't understand enough about locks.  A recent (last week
> or two) checkin screwed the wi driver such that it panic's saying that
> ic_nodelock is used recursively first in line 525 and then in 547 of
> net80211/ieee80211_node.c.
> 
> On my own, I tried chaging line 87 to mtx_init() the lock with
> MTX_RECURSE, but this causes the kernel to panic on line 472 saying
> something about trying to spin.
> 
> I'm relatively certain that this is all only caused by hostap mode
> ... it doesn't appear to happen on my laptop (also running this week's
> current).
> 
> ... Now, that said, some of my disassociation problems on the laptop
> seem to have cured (associating with other access points) ...
> 
> So I need help with this really large bug in the wi code.

Please send me your config.  I'll deal with it.

	Sam