crash in wpa_supplicant_dbus_notify_state_change

Bug #88325 reported by jroubuntu
80
Affects Status Importance Assigned to Milestone
wpasupplicant (Ubuntu)
Fix Released
Undecided
Reinhard Tartler

Bug Description

Binary package hint: wpasupplicant

After last ubuntu feist fawn update (27 february) with kernel update wireless missing giving the microcode error for bcm4xxx in the boot screen.

~$ sudo wpa_supplicant -Dwext -ieth1 -c/etc/wpa_supplicant.conf
SIOCSIFFLAGS: Operation not supported
Could not set interface 'eth1' UP
l2_packet_receive - recvfrom: Network is down
ioctl[SIOCSIWSCAN]: No such device
Failed to initiate AP scan.

If I try to:
~$ sudo ifconfig eth1 up
SIOCSIFFLAGS: Operation not supported

I I try to:

sudo wpa_supplicant -Dwext -ieth1 -c/etc/wpa_supplicant.conf
SIOCSIFFLAGS: Operation not supported
Could not set interface 'eth1' UP
l2_packet_receive - recvfrom: Network is down
ioctl[SIOCSIWSCAN]: No such device
Failed to initiate AP scan.
ioctl[SIOCSIWSCAN]: No such device
Failed to initiate AP scan.
ioctl[SIOCSIWSCAN]: No such device
Failed to initiate AP scan.
CTRL-EVENT-TERMINATING - signal 2 received

If I try to:

:~$ sudo dhclient eth1
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFFLAGS: Operation not supported
SIOCSIFFLAGS: Operation not supported
Listening on LPF/eth1/00:90:4b:55:af:f0
Sending on LPF/eth1/00:90:4b:55:af:f0
Sending on Socket/fallback
receive_packet failed on eth1: Network is down
DHCPREQUEST on eth1 to 255.255.255.255 port 67
send_packet: Network is down
DHCPREQUEST on eth1 to 255.255.255.255 port 67
send_packet: Network is down
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
send_packet: Network is down
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
send_packet: Network is down
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
send_packet: Network is down
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
send_packet: Network is down
No DHCPOFFERS received.
Trying recorded lease 192.168.0.174
SIOCSIFFLAGS: Operation not supported
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.

--- 192.168.0.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.908/0.908/0.908/0.000 ms
SIOCADDRT: Network is unreachable
bound: renewal in 35397 seconds.

##########
My file in /etc/network/interfaces is
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface

iface eth1 inet dhcp
wpa-driver wext
wpa-ssid "xxxx"
wpa-psk "xxxx"

auto eth0

auto lo:1
iface lo:1 inet static
address 192.168.xx.xxx
netmask 255.255.255.0

auto lo:2
iface lo:2 inet static
address 192.168.xx.xxx
netmask 255.255.255.0

auto lo:3
iface lo:3 inet static
address 192.168.xx.xxx
netmask 255.255.255.0

iface eth0 inet dhcp

auto eth1

####################3
my wpa_supliccant is:

ctrl_interface=/var/run/wpa_supplicant

network={
 ssid="xxxxx"
 key_mgmt=WPA-PSK IEEE8021X NONE
 proto=WPA
 group=TKIP
 psk="xxxx"
}

network={
 ssid="xxxx"
 key_mgmt=WPA-PSK IEEE8021X NONE
 proto=WPA
 group=TKIP
 psk="xxxx"
}

##############
I have installed ndiswrapper with the corresponding driver
sudo ndiswrapper -l
installed drivers:
bcmwl5 driver installed, hardware (14E4:4324) present (alternate driver: bcm43xx)

I also run with sucess:
sudo bcm43xx-fwcutter -w /lib/firmware bcmwl5.sys

by the way nm-applet is stopped showing wireless nets.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Feb 27 10:50:47 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /sbin/wpa_supplicant
Package: wpasupplicant 0.5.5-4
ProcCmdline: wpa_supplicant -Dwext -ieth1 -c/etc/wpa_supplicant.conf
ProcCwd: /home/jorge
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=en_AU.UTF-8
 LANGUAGE=en_AU:en
Signal: 11
SourcePackage: wpasupplicant
StacktraceTop:
 ?? ()
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? () from /lib/tls/i686/cmov/libc.so.6
Uname: Linux jrolap 2.6.20-9-386 #2 Mon Feb 26 02:58:41 UTC 2007 i686 GNU/Linux
UserGroups:

Revision history for this message
jroubuntu (jorgearosa) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:wpa_supplicant_dbus_notify_state_change (wpa_s=0x8096340, new_state=WPA_DISCONNECTED, old_state=WPA_DISCONNECTED) at ctrl_iface_dbus.c:652
wpa_supplicant_set_state (wpa_s=0x8096340, state=WPA_DISCONNECTED) at wpa_supplicant.c:853
wpa_supplicant_deauthenticate (wpa_s=0x8096340, reason_code=3) at wpa_supplicant.c:1573
wpa_supplicant_deinit_iface (wpa_s=0x8096340) at wpa_supplicant.c:2303
wpa_supplicant_add_iface (global=0x80962f8, iface=0x8096008) at wpa_supplicant.c:2361

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Reinhard Tartler (siretart) wrote : Re: wpa_supliccant crashes constantly for bcmxxx in HP Pav. zx5000

I think this has been fixed in version 0.5.7-0ubuntu2. can you please recheck with that version?

Changed in wpasupplicant:
status: Unconfirmed → Needs Info
Revision history for this message
Reinhard Tartler (siretart) wrote :

Should be fixed by this upload. Please reopen if necessary

Changes:
 wpasupplicant (0.6.0~cvs20070224-2) unstable; urgency=low
 .
   [Kel Modderman]
   * Update XS-Vcs fields of debian/control to reflect pkg-wpa archive change.
   * Update debian/copyright with new upstream URL's and Jouni's new email
     address.
   * Rename madwifi related dpatches to match that of hostapd source package.
   * Update debian/watch with new upstream release URL.
 .
   [Reinhard Tartler]
   * Remove the prerm script as discussed on pkg-wpa-devel@
   * upload to unstable

Changed in wpasupplicant:
assignee: nobody → siretart
status: Needs Info → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.