NetworkManager loses wireless connection frequently; wicd doesn't -- Marvell 88E8040

[manishmahabir]

Binary package hint: network-manager

network-manager looses wireless connection frequently and tries to reconnect.
at times after disconnection, as soon as i plug my wired connection, both wired and wireless get connected simultaneously.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
IfupdownConfig:
 auto lo
 iface lo inet loopback
Package: network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2
ProcEnviron:
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: network-manager
Uname: Linux 2.6.28-11-generic i686

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release the Karmic Koala. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

[Jeremy Nickurak (nickurak)]

I've been having similar issues under jaunty and karmic. It's hard to tell if this is the same issue or an independant one.

I'm on a bcm4322 wireless chip with broadcom's wl driver. I frequently lose wireless connectivity, and nm-applet doesn't indicate it. As far as I can tell, this is always on a network with many access points, one or two of which are clearly the closest ones.

The system itself seems to be aware that it's lost its connection, as the logs indicate. It seems like the network roams from one AP to another, and gets disconnected, reconnects and authenticates, but doesn't run dhcp. Then, if I manually try to reconnect (by re-selecting the network in nm-applet, which already indicates it's connected) it fails to connect. The only reliable way I've found to correct is whenever the issue comes up, running:

sudo killall wpa_supplicant dhclient; sudo /etc/init.d/NetworkManager stop; sudo rmmod wl; sudo modprobe wl; sudo /etc/init.d/NetworkManager start.

I'm attaching a daemon.log with NetworkManager and wpa_supplicant messages.

[Jeremy Nickurak (nickurak)]

One indication that it's a network-manager problem is that (like many users) I'm trying wicd instead of network-manager. I've been up and running for almost 24 hours with no such disconnection problems.

[max (mikhmv)]

Confirm this bug on Karmic.
And I have this problem only on notebook with broadcom WiFi.

[max (mikhmv)]

Thanks Jeremy. I start use wicd and it is work very well without disconnections.

[Jeremy Nickurak (nickurak)]

Still present in Lucid. Wicd still solves the problem.

[jedioetzi (jedioetzi)]

On maverick the same issue.
with only wlan0 it disconnects frequently when there is network traffic .
If no or low traffic the connection seems to be stable.

with wicd the problem not occurs (in same conditions, same place, same net).

Dec 13 10:04:40 luca-laptop NetworkManagerDispatcher: lo is down
Dec 13 10:04:40 luca-laptop kernel: [ 45.704994] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Dec 13 10:04:41 luca-laptop kernel: [ 46.500174] hda-intel: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj.
Dec 13 10:04:59 luca-laptop nautilus: [N-A] Nautilus-Actions Tracker 2.30.2 initializing...
Dec 13 10:04:59 luca-laptop nautilus: [N-A] Nautilus-Actions Menu Extender 2.30.2 initializing...
Dec 13 10:04:59 luca-laptop kernel: [ 65.114067] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Dec 13 10:05:00 luca-laptop kernel: [ 65.397739] Intel AES-NI instructions are not detected.
Dec 13 10:05:00 luca-laptop kernel: [ 65.554359] padlock: VIA PadLock not detected.
Dec 13 10:05:10 luca-laptop NetworkManagerDispatcher: wlan0 is up (wlan0 up)
Dec 13 10:05:10 luca-laptop NetworkManagerDispatcher: Found IP 192.168.1.177 ESSID EMC
Dec 13 10:05:10 luca-laptop NetworkManagerDispatcher: Profile has not changed: home
Dec 13 10:05:10 luca-laptop NetworkManagerDispatcher: Calling system network settings
Dec 13 10:05:11 luca-laptop NetworkManagerDispatcher: Calling user network settings for all logged users
Dec 13 10:05:11 luca-laptop NetworkManagerDispatcher: Completed network profiles settings
Dec 13 10:05:23 luca-laptop kernel: [ 87.472647] cfg80211: Calling CRDA to update world regulatory domain
Dec 13 10:05:23 luca-laptop kernel: [ 87.475537] cfg80211: World regulatory domain updated:
Dec 13 10:05:23 luca-laptop kernel: [ 87.475539] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Dec 13 10:05:23 luca-laptop kernel: [ 87.475541] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec 13 10:05:23 luca-laptop kernel: [ 87.475544] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Dec 13 10:05:23 luca-laptop kernel: [ 87.475546] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Dec 13 10:05:23 luca-laptop kernel: [ 87.475548] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec 13 10:05:23 luca-laptop kernel: [ 87.475550] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec 13 10:05:24 luca-laptop NetworkManagerDispatcher: wlan0 is down
Dec 13 10:05:34 luca-laptop NetworkManagerDispatcher: wlan0 is up (wlan0 up)
Dec 13 10:05:34 luca-laptop NetworkManagerDispatcher: Found IP 192.168.1.177 ESSID Alice-36687582
Dec 13 10:05:34 luca-laptop NetworkManagerDispatcher: Profile has not changed: home
Dec 13 10:05:34 luca-laptop NetworkManagerDispatcher: Calling system network settings
Dec 13 10:05:34 luca-laptop NetworkManagerDispatcher: Calling user network settings for all logged users
Dec 13 10:05:34 luca-laptop NetworkManagerDispatcher: Completed network profiles settings
Dec 13 10:05:44 luca-laptop sudo: pam_sm_authenticate: Called
Dec 13 10:05:44 luca-laptop sudo: pam_sm_authenticate: username = [luca]
Dec 13...

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Thomas Hood (jdthood)]

Does this problem persist in Ubuntu 12.04?

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]