network-manager fails to stop properly when connected to wireless

[David Benjamin]

Binary package hint: network-manager

NetworkManager hangs the shutdown process for me if connected to a network.

I rebooted several times, doing nothing but set up the network and then restarting and each time this was reproducible.

Steps to Reproduce:
1. Set the kernel to boot without the quiet option, so it's possible to see what's happening (or whichever option it was)
2. Connect computer to wireless
3. Logout -> Restart
The restart hangs at killing NetworkManager.

Pressing the power button at this point makes the process start over, this time shutting down instead of restarting, and it succeeds in killing NM.
There is a warning between system-tools-backends and NetworkManager (before NM) about not being able to kill a certain PID because it doesn't exist anymore. This PID is not that of NM. (Probably some service was already killed and it was trying to kill it again.) After this, the computer needs to be manually turned on since it is shutting down instead of restarting.
(Note: on the one time I tried this when I had hibernated in between, pressing the button didn't work and I had to hold it down and power down without shutting down cleanly.)

I am running an up-to-date Gutsy install that was updated from Feisty.

Wireless card: ipw3945

[David Benjamin (davidben)]

More information.

This also occurs (and seems to occur more often) after a suspend (for significantly long, like one hour) and seems to be caused by NetworkManager hanging and so it will not respond to a stop command. Also, when this happens, nm-applet is stuck on displaying old information, i.e. I'm still connected to the network I was on before I suspended.

When the latter case happens, running top shows that it is at 100% CPU. I tried to attach a debugger to get a stack trace, but gdb crashed and I did not have pstack installed. The next time this happens, I will try pstack.

However, there aren't any symbols in the binary, so I don't know how much use it'll be.

My guess is that there are some critical points of NetworkManager's execution that cause it to behave very badly to a stop command and this gets triggered when it's told to shut down at the wrong time.

[Nick Steeves (nick-0)]

It'd just like to confirm that this bug also affects my Thinkpad X32, with ipw2200 chipset.

[Keith (pantherse)]

I encounter this problem when I'm connected to Wired Network. The network card is a Broadcom BCM5705M. This started happening after upgrading to 7.10

[Seth Kinast (seth)]

It's rather reversed for me. When connected to the wired net (eth0), I cannot shutdown and it hangs when trying to stop eth1 (wireless). When connected to wireless, I shut down cleanly.

Dell Inspiron 9100 with Broadcom stuff:
gwenhefar@Gwenhefar:~$ lspci | grep Broadcom
02:00.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01)
02:03.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)

[Thom Pischke (thom-pischke)]

Can confirm at least a similar problem, where shutting down the wifi interface (eth1) hangs. This prevents shutdown from completing, hanging forever on the splash screen. Can also duplicate simply by deactivating the wireless connectivity via right click on the network manager applet. This brings an instant hang to the network manager, system monitor and other applets, and prevents much of anything else from working. Not even possible to launch a terminal at that point.

All problems fixed by uninstalling Network Manager and using the gnome network configuration tools.

Broadcom 4306 rev2.

[Thom Pischke (thom-pischke)]

Maybe worth noting that actual internet connection is over wired connection, eth0. eth1 not actually in use, except to scan available networks.

[logari81 (logari81)]

Similar problem using:
06:03.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)
on an Acer Aspire 1690 laptop.

After upgrading from 7.04 to 7.10 I started having random problems with shutting down. Sometimes the system hung and I had to push the power off button to get my laptop off. More often I have seen my system waiting for about 40 sec after the "Will now halt" message and then getting down after showing the next message:
.
.
 * Will now halt
[41055.354000] ipw2200: ipw2200-bss.fw request_firmware failed
[41055.356000] ipw2200: unable to load firmware: -2
[41055.356000] ipw2200: failed to up device
halt: Unable to iterate IDE devices: No such file or directory

(The last line shows up even if the problem doesn't happen, propably has nothing with this problem to do)

Actually the problem of hanging up at shutting down doesn't occur anymore, whether the problem of retarding the shuting down occurs randomly about 50% I shut down.

At the time after upgrading to gutsy I 've been also experimenting with suspend and hibernate, which initially didn't work. Thus I can't say if the factor that triggered the problem was the upgrade or my Suspend/Hibernate testing.

[Alexander Sack (asac)]

Hi,

I am not yet sure what this is about, but maybe its worth testing the 0.6.5-0ubuntu16.7.10.0 package from gutsy-proposed. You can enable the proposed archive in System -> Administration -> Software Sources.

Thanks,
 - Alexander

[logari81 (logari81)]

Hi,
the problem with the retarded shutting down is still there with the network-manager-0.6.5-0ubuntu16.7.10.0 . Occurs always with an Ad-Hoc / WEP wifi, works fine with a non-Ad-Hoc / WPA wifi. I can avoid the problem by disabling Wireless over the nm-applet before shutting down.

thanks

[Märt Suga (mart-suga)]

I have the same shutdown/restart problem with my HP nx9125 with Broadcom 4318 wireless card switched on (shuts down normally if wifi is switched off). I also attach the photo from my hanged screen.

[Toni Förster (stonerl)]

Same Problem here. But it seems that this problem doesn't only appear when i'm connected with a wireless network. The reboot or shutdown-process takes several minutes but in the end it shuts the system down or reboots. This problem doesn't only appear when i remove my wifi-card (3com OfficeConnect 3CRSHPW196) the system shuts down properly. I have a second wifi-card (Corega something - a brand sold in Japan) and this card doesn't cause this error. Also when i disable the Network before shutdown/reboot or set the wifi-card to static-mode (uncheck the Roaming-Mode) the system shuts down/reboots without problems.

I'm using the latest Hardy-Kernel (2.6.24.15-generic)

stonerl

Those Bugreports describe the same problem, I assume:

Bug #208705
Bug #128895
Bug #138691

[JPBoyer (jp-boyer)]

I have same problem... but on a desktop. So the WiFi may not be the culprit. I've attached a pic of the final screen, similar to the one Märt has (except the ethernet lines, but I do not think this matters?).
On the Ubuntu forum, there's quite a lot of people with the same problem, with very different machines. One was able to apparently stop this to occur by:
- System>Administration>Login Window
Click "Edit Commands" and remove the last "Shut down via gdm." in both the Halt Command and the Reboot Command.
For him that apparently does the trick.
I tried and got finally the normal shut-down screen with the progrees bar, and a normal shut-down time. But only once.
I discover however that, every time I change and save the Halt or Reboot command in the Login Window dialog, I got my clean shut-down process.
I mean that if I delete the "Shut down via gdm.", save, then put it back again and save, so I have not changed anything in the end but to "refresh" these commands (dates? sorry I am really poor at this stuff), I got the clean shut-down.
When doing this with the grub option "quiet splash" taken out, I got a clean screen as well (i.e just "System is restarting please wait" for a reboot), with nothing at all about network manager or else, meaning that the shut-down is really clean and proper.
It is not a fix though, as I cannot keep changing these commands at each session, but that may give a clue as to where to look for a proper fix?

[JPBoyer (jp-boyer)]

There were positive comments on the forum regarding this bug.
http://ubuntuforums.org/showthread.php?t=772733&page=2

Does that help?

[guenthert (guenthert)]

My laptop hung after calling NetworkManager on shutdown too this morning. Here the cause was that it tried to deconfigure a network interface which wasn't listed in /etc/network/interfaces (file edited).

What's actually the motivation to call NetworkManager on shutdown? Why deconfigure network interfaces then, if the machine is going to be down anyway? Why telling applications (via DBus?) that the network connection is lost, when those applications are going to be terminated anyway (if they haven't been terminated already)?

What problem is the NetworkManager attempting to solve on shutdown?

I noticed that some DHCP clients tell the DHCP server, when they disconnect, but why? They received a lease, not a lock, it will expire as it is meant to.

So why waste time and energy (and exposing the system to potential bugs) by calling NetworkManager on the way out?

[Nick Steeves (nick-0)]

Has this bug been resolved yet? (I've grown re-accustomed to living without NM, though it would be really nice to have again...)

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

 Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Closing the bug because of no response. Please reopen if this is still an issue.