wpa_supplicant sig11-crashes with old, but still supported radio-adapter, Cisco 350 (802.11b). Problem persisted from 7.0-RELEASE. ===Cut=== %wpa_supplicant -d -ian0 -c/etc/wpa_supplicant.conf Initializing interface 'an0' conf '/etc/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A' Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf' Reading configuration file '/etc/wpa_supplicant.conf' Priority group 0 id=0 ssid='salma' Initializing interface (2) 'an0' EAPOL: SUPP_PAE entering state DISCONNECTED EAPOL: KEY_RX entering state NO_KEY_RECEIVE EAPOL: SUPP_BE entering state INITIALIZE EAP: EAP entering state DISABLED EAPOL: External notification - portEnabled=0 EAPOL: External notification - portValid=0 Own MAC address: 00:40:96:35:b2:8d wpa_driver_bsd_set_wpa: enabled=1 wpa_driver_bsd_set_wpa_internal: wpa=3 privacy=1 wpa_driver_bsd_del_key: keyidx=0 wpa_driver_bsd_del_key: keyidx=1 wpa_driver_bsd_del_key: keyidx=2 wpa_driver_bsd_del_key: keyidx=3 wpa_driver_bsd_set_countermeasures: enabled=0 wpa_driver_bsd_set_drop_unencrypted: enabled=1 Setting scan request: 0 sec 100000 usec Added interface an0 State: DISCONNECTED -> SCANNING Starting AP scan (broadcast SSID) Trying to get current scan results first without requesting a new scan to speed up initial association Segmentation fault (core dumped) ===Cut== Backtrace (wpa_supplicant is assembled with -g): ===Cut=== (gdb) bt #0 0x08065390 in ?? () [...] #5229 0x28356a4b in f_prealloc () from /lib/libc.so.7 Previous frame inner to this frame (corrupt stack?) (gdb) ===Cut=== How-To-Repeat: Get a Cisco 350 card, try to use wpa_supplicant.
Responsible Changed From-To: freebsd-bugs->freebsd-net Over to maintainer(s).
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped
I am sorry that nobody was able to investigate this issue at the time you reported it. As you note an(4) was already old in 2008, and more than 10 years later the driver is being removed from FreeBSD. Thus, closing this issue.