GNOME Bugzilla – Bug 454697
Disconnection with assertion failed in syslog
Last modified: 2007-11-29 23:45:22 UTC
Often now my wifi connexion stops with the following messages in my system log : Jul 8 00:26:52 kylae NetworkManager: <debug> [1183847212.044356] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'panda' Jul 8 00:26:52 kylae NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/ath0 / panda Jul 8 00:26:52 kylae NetworkManager: <info> Deactivating device ath0. Jul 8 00:26:52 kylae NetworkManager: <info> Device ath0 activation scheduled... Jul 8 00:26:52 kylae NetworkManager: <info> Activation (ath0) started... Jul 8 00:26:52 kylae NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled... Jul 8 00:26:52 kylae NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) started... Jul 8 00:26:52 kylae NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled... Jul 8 00:26:52 kylae NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete. Jul 8 00:26:52 kylae NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) starting... Jul 8 00:26:52 kylae NetworkManager: <info> Activation (ath0/wireless): access point 'panda' is encrypted, but NO valid key exists. New key needed. Jul 8 00:26:52 kylae NetworkManager: <info> Activation (ath0) New wireless user key requested for network 'panda'. Jul 8 00:26:52 kylae NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) complete. Jul 8 00:26:52 kylae NetworkManager: <info> Activation (ath0) New wireless user key for network 'panda' received. Jul 8 00:26:52 kylae NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled... Jul 8 00:26:52 kylae NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) started... Jul 8 00:26:52 kylae NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled... Jul 8 00:26:52 kylae NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete. Jul 8 00:26:52 kylae NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) starting... Jul 8 00:26:52 kylae NetworkManager: <info> Activation (ath0/wireless): access point 'panda' is encrypted, and a key exists. No new key needed. Jul 8 00:26:52 kylae NetworkManager: <info> SUP: sending command 'INTERFACE_ADD ath0 wext /var/run/wpa_supplicant ' Jul 8 00:26:52 kylae NetworkManager: <info> SUP: response was 'OK' Jul 8 00:26:52 kylae NetworkManager: <info> SUP: sending command 'AP_SCAN 1' Jul 8 00:26:52 kylae NetworkManager: <info> SUP: response was 'OK' Jul 8 00:26:52 kylae NetworkManager: <info> SUP: sending command 'ADD_NETWORK' Jul 8 00:26:52 kylae NetworkManager: <info> SUP: response was '0' Jul 8 00:26:52 kylae NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 70616e6461' Jul 8 00:26:52 kylae NetworkManager: <info> SUP: response was 'OK' Jul 8 00:26:52 kylae NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE' Jul 8 00:26:52 kylae NetworkManager: <info> SUP: response was 'OK' Jul 8 00:26:52 kylae NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_key0 <key>' Jul 8 00:26:52 kylae NetworkManager: <info> SUP: response was 'OK' Jul 8 00:26:52 kylae NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_tx_keyidx 0' Jul 8 00:26:52 kylae NetworkManager: <info> SUP: response was 'OK' Jul 8 00:26:52 kylae NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0' Jul 8 00:26:52 kylae NetworkManager: <info> SUP: response was 'OK' Jul 8 00:26:52 kylae NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) complete. Jul 8 00:27:00 kylae ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready Jul 8 00:27:00 kylae NetworkManager: <info> Activation (ath0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'panda'. Jul 8 00:27:00 kylae NetworkManager: <info> Activation (ath0) Stage 3 of 5 (IP Configure Start) scheduled. Jul 8 00:27:00 kylae NetworkManager: <info> Activation (ath0) Stage 3 of 5 (IP Configure Start) started... Jul 8 00:27:01 kylae NetworkManager: <info> Activation (ath0) Beginning DHCP transaction. Jul 8 00:27:01 kylae NetworkManager: <info> Activation (ath0) Stage 3 of 5 (IP Configure Start) complete. Jul 8 00:27:01 kylae NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface ath0 Jul 8 00:27:01 kylae dhclient: wifi0: unknown hardware address type 801 Jul 8 00:27:01 kylae dhclient: wifi0: unknown hardware address type 801 Jul 8 00:27:01 kylae NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface ath0 Jul 8 00:27:02 kylae dhclient: Trying medium "-link0 -link1 -link2" 1 Jul 8 00:27:02 kylae dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4 Jul 8 00:27:02 kylae dhcdbd: dhco_parse_option_settings: no new option definition for medium Jul 8 00:27:02 kylae dhclient: DHCPOFFER from 192.168.0.254 Jul 8 00:27:02 kylae NetworkManager: <info> DHCP daemon state is now 7 (unknown) for interface ath0 Jul 8 00:27:02 kylae usb 1-1: reset low speed USB device using uhci_hcd and address 3 Jul 8 00:27:05 kylae NetworkManager: <info> Old device 'ath0' activating, won't change. Jul 8 00:27:07 kylae dhclient: DHCPREQUEST on ath0 to 255.255.255.255 port 67 Jul 8 00:27:07 kylae dhclient: DHCPACK from 192.168.0.254 Jul 8 00:27:07 kylae dhclient: bound to 192.168.0.2 -- renewal in 1779 seconds. Jul 8 00:27:07 kylae dhcdbd: dhco_parse_option_settings: no new option definition for medium Jul 8 00:27:07 kylae NetworkManager: <info> DHCP daemon state is now 2 (bound) for interface ath0 Jul 8 00:27:07 kylae NetworkManager: <info> Activation (ath0) Stage 4 of 5 (IP Configure Get) scheduled... Jul 8 00:27:07 kylae NetworkManager: <info> Activation (ath0) Stage 4 of 5 (IP Configure Get) started... Jul 8 00:27:07 kylae dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.host_name Jul 8 00:27:07 kylae dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.nis_domain Jul 8 00:27:07 kylae dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.nis_servers Jul 8 00:27:07 kylae NetworkManager: <info> Retrieved the following IP4 configuration from the DHCP daemon: Jul 8 00:27:07 kylae NetworkManager: <info> address 192.168.0.2 Jul 8 00:27:07 kylae NetworkManager: <info> netmask 255.255.255.0 Jul 8 00:27:07 kylae NetworkManager: <info> broadcast 192.168.0.255 Jul 8 00:27:07 kylae NetworkManager: <info> gateway 192.168.0.254 Jul 8 00:27:07 kylae NetworkManager: <info> nameserver 127.0.0.1 Jul 8 00:27:07 kylae NetworkManager: <info> nameserver 212.27.54.252 Jul 8 00:27:07 kylae NetworkManager: <info> nameserver 212.27.53.252 Jul 8 00:27:07 kylae NetworkManager: <info> domain name 'local' Jul 8 00:27:07 kylae NetworkManager: <info> Activation (ath0) Stage 5 of 5 (IP Configure Commit) scheduled... Jul 8 00:27:07 kylae NetworkManager: <info> Activation (ath0) Stage 4 of 5 (IP Configure Get) complete. Jul 8 00:27:07 kylae NetworkManager: <info> Activation (ath0) Stage 5 of 5 (IP Configure Commit) started... Jul 8 00:27:08 kylae NetworkManager: <info> Activation (ath0) successful, device activated. Jul 8 00:27:08 kylae NetworkManager: <info> Activation (ath0) Finish handler scheduled. Jul 8 00:27:08 kylae NetworkManager: <info> Activation (ath0) Stage 5 of 5 (IP Configure Commit) complete. Jul 8 00:27:08 kylae NetworkManager: <debug> [1183847228.354723] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'panda' Jul 8 00:27:08 kylae NetworkManager: <info> SWITCH: terminating current connection 'ath0' because it's no longer valid. Jul 8 00:27:08 kylae NetworkManager: <info> Deactivating device ath0. Jul 8 00:27:08 kylae dhclient: There is already a pid file /var/run/dhclient-ath0.pid with pid 17491 Jul 8 00:27:08 kylae dhclient: killed old client process, removed PID file Jul 8 00:27:08 kylae dhclient: wifi0: unknown hardware address type 801 Jul 8 00:27:08 kylae dhclient: wifi0: unknown hardware address type 801 Jul 8 00:27:08 kylae dhclient: DHCPRELEASE on ath0 to 192.168.0.254 port 67 Jul 8 00:27:09 kylae NetworkManager: nm_device_is_802_3_ethernet: assertion `dev != NULL' failed Jul 8 00:27:09 kylae NetworkManager: nm_device_is_802_11_wireless: assertion `dev != NULL' failed Jul 8 00:27:10 kylae dhclient: receive_packet failed on ath0: Network is down Jul 8 00:27:25 kylae ADDRCONF(NETDEV_UP): ath0: link is not ready Notice the lines : nm_device_is_802_3_ethernet: assertion `dev != NULL' failed nm_device_is_802_11_wireless: assertion `dev != NULL' failed My hardware : Athreos chipset AR5008 using madwifi driver And when I connect manually using iwconfig + dhclient everything works fine
I can confirm this bug with ipw3945 using NetworkManager version 0.6.5-0ubuntu6. This bug has been seen on several times on mailing lists (found via google:) http://www.redhat.com/archives/fedora-test-list/2006-February/msg00460.html http://www.redhat.com/archives/fedora-de-list/2007-March/msg00055.html http://mail.gnome.org/archives/networkmanager-list/2006-July/msg00015.html http://www.mail-archive.com/networkmanager-list@gnome.org/msg06196.html
Hi there, is this still an issue? i have a similar setup and doens't experience this
I don't experience this anymore too. Well, I no longer use ArchLinux and I decided to switch from madwifi (wich has a annoying bug that stop the connexion after some time, and I think it could be related) to ndiswrapper. Unfortunately. And waiting for the new kernel driver that will replace madwifi to support the chipset AR5008. So I think for now i could close the bug.