Re: wpa_supplicant causes panic in ieee80211_newstate

From: Brian Candler <B.Candler_at_pobox.com>
Date: Tue, 10 May 2005 11:31:02 +0100
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.
Received on Tue May 10 2005 - 08:31:21 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:34 UTC