From owner-freebsd-current@FreeBSD.ORG Thu Apr 28 12:15:03 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 EFE9E16A4CE for ; Thu, 28 Apr 2005 12:15:03 +0000 (GMT) Received: from orb.pobox.com (orb.pobox.com [207.8.226.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A91F43D2D for ; Thu, 28 Apr 2005 12:15:03 +0000 (GMT) (envelope-from discussion-lists@linnet.org) Received: from orb (localhost [127.0.0.1]) by orb.pobox.com (Postfix) with ESMTP id 3145E7D7 for ; Thu, 28 Apr 2005 08:15:00 -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 017E391 for ; Thu, 28 Apr 2005 08:14:59 -0400 (EDT) Received: from lists by thinkdog.local.linnet.org with local (Exim 4.43 (FreeBSD)) id 1DR7up-000NXc-6g for freebsd-current@freebsd.org; Thu, 28 Apr 2005 13:14:47 +0100 Date: Thu, 28 Apr 2005 13:14:47 +0100 From: Brian Candler To: freebsd-current@freebsd.org Message-ID: <20050428121447.GA90430@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: 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: Thu, 28 Apr 2005 12:15:04 -0000 -CURRENT supped as of yesterday. Old-ish Dell PIII-600MHz system. I have put in a Buffalo PCI-PCCard adaptor with WLI-PCM-L11 wireless card, detected as if_wi. Now I'm trying to see if I can get it to join a WPA network. I installed security/wpa_supplicant from ports, and ran it as wpa_supplicant -iwi0 -c/usr/local/etc/wpa_supplicant.conf -d # based closely on wpa_suppicant.conf.sample It generated some screens of debug information, ending with Starting AP scan (broadcast SSID) Added BSSID 00:00:00:00:00:00 into blacklist EAPOL: External notification - portEnabled=0 EAPOL: External notification - portValid=0 Disconnect event - remove keys wpa_driver_bsd_dsl_key: keyidx=0 wpa_driver_bsd_dsl_key: keyidx=1 wpa_driver_bsd_dsl_key: keyidx=2 wpa_driver_bsd_dsl_key: keyidx=3 wpa_driver_bsd_dsl_key: keyidx=0 At this point, a panic occured on the first virtual console: panic: ieee80211_newstate: bogus xmit rate 0 setup cpuid = 0 KDB: enter: panic [thread pid 22 tid 100014 ] Stopped at kdb_enter+0x2b: nop db> trace Tracing pid 22 tid 100014 td 0xc1521d80 kdb_enter(c08a88ab) at kdb_enter+0x2b panic(c08b6a4a,c085bbdf,0,c16ae400,c1770000) at panic+0x127 ieee80211_netstate(c177025c,4,ffffffff,c16ae400,782af) at ieee80211_newstate+0x50e wi_newstate(c1777025c,4,ffffffff) at wi_newstate+0x1bf wi_info_intr(c17770000) at wi_info_intr+0x107 wi_intr(c17770000) at wi_intr+0x17e pccard_intr(c1544680,c1775080,cbffed0c,c064622c,c164f880) at pccard_intr+0x60 cbb_func_intr(c164f880) at cbb_func_intr+0x45 ithread_loop(c1544c00,cbffed38,c1544c00,c064610c,0) at ithread_loop+0x120 fork_exit(c064610c,c1544c00,cbffed38) at fork_exit+0xa0 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xcbffed6c, edp = 0 --- db> ps ... 22 c1524c00 0 0 0 0000204 [CPU 0] irq11: cbb0 ifpi0+* Unfortunately I didn't have a dumpdev enabled. I don't know if the above is much use by itself. Regards, Brian.