From owner-freebsd-current@FreeBSD.ORG Tue May 10 10:31:21 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CA6B16A4CE; Tue, 10 May 2005 10:31:21 +0000 (GMT) Received: from orb.pobox.com (orb.pobox.com [207.8.226.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 424BA43D79; Tue, 10 May 2005 10:31:21 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from orb (localhost [127.0.0.1]) by orb.pobox.com (Postfix) with ESMTP id 9F24B80A; Tue, 10 May 2005 06:31:16 -0400 (EDT) Received: from thinkdog.local.linnet.org (host217-40-157-153.in-addr.btopenworld.com [217.40.157.153]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by orb.sasl.smtp.pobox.com (Postfix) with ESMTP id 2B6D387; Tue, 10 May 2005 06:31:13 -0400 (EDT) Received: from brian by thinkdog.local.linnet.org with local (Exim 4.43 (FreeBSD)) id 1DVS10-00020a-Jw; Tue, 10 May 2005 11:31:02 +0100 Date: Tue, 10 May 2005 11:31:02 +0100 From: Brian Candler To: Bill Paul Message-ID: <20050510103102.GA7705@uk.tiscali.com> References: <20050509164944.GA7041@uk.tiscali.com> <20050510032532.B08BE16A4EE@hub.freebsd.org> <20050510091354.GB7269@uk.tiscali.com> <20050510095341.GA7507@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050510095341.GA7507@uk.tiscali.com> User-Agent: Mutt/1.4.2.1i cc: sam@errno.com cc: freebsd-current@freebsd.org Subject: Re: wpa_supplicant causes panic in ieee80211_newstate X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Tue, 10 May 2005 10:31:21 -0000 On Tue, May 10, 2005 at 10:53:41AM +0100, Brian Candler wrote: > I can join a vanilla unencrypted network, but using wpa_supplicant to try to > join a WPA-PSK network has not been successful. Also: trying to run dhclient on the ndis0 interface seems to make it lose the ssid I selected. Then, trying to watch what was happening with tcpdump, I managed to get another panic: ndis0: failed to get bssid ndis0: setting SSID to mytestnet ndis0: failed to get bssid ndis0: link up panic: mutex Giant not owned at .../src/sys/net/bpf.c:1321 cpuid = 0 .. db> trace Tracing pid 32 tid 100022 td 0xc1521180 kdb_enter.. panic.. _mtx_assert.. catchpacket.. bpf_tap(..) at bpf_tap+0x74 bpf_mtap(..) at bpf_mtap+0x34 ndis_start(..) at ndis_start+0x3e5 ndis_starttask(..) at ndis_starttask+0x1e _end(..) at 0xc15b7161 _end(..) at 0xc15b5b61 fork_exit(..) at fork_exit+0xa0 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xcca16d6c, ebp = 0 --- db> ps .. 32 .... 0000204 [CPU 0] Windows WorkItem Regards, Brian.