unregister_netdevice: waiting for eth1 (ipw2100, Intel PRO/Wireless LAN 2100 3B Mini PCI)

[Loïc d'Anterroches]

When shutting down the computer ubuntu hoary
The message "unregister_netdevice: waiting for eth1 ... " is displayed with a
count that is never incremented (staying at one)
The system is stuck, and I need to force the shutdown of the computer. (IBM
t41p, no problem at all with warty)

lspci output:

0000:00:00.0 Host bridge: Intel Corp. 82855PM Processor to I/O Controller (rev 03)
0000:00:01.0 PCI bridge: Intel Corp. 82855PM Processor to AGP Controller (rev 03)
0000:00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
USB UHCI Controller #1 (rev 01)
0000:00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
USB UHCI Controller #2 (rev 01)
0000:00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
USB UHCI Controller #3 (rev 01)
0000:00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI
Controller (rev 01)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 81)
0000:00:1f.0 ISA bridge: Intel Corp. 82801DBM LPC Interface Controller (rev 01)
0000:00:1f.1 IDE interface: Intel Corp. 82801DBM (ICH4) Ultra ATA Storage
Controller (rev 01)
0000:00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus
Controller (rev 01)
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
0000:00:1f.6 Modem: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem
Controller (rev 01)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc M10 NT [FireGL
Mobility T2] (rev 80)
0000:02:00.0 CardBus bridge: Texas Instruments PCI4520 PC card Cardbus
Controller (rev 01)
0000:02:00.1 CardBus bridge: Texas Instruments PCI4520 PC card Cardbus
Controller (rev 01)
0000:02:01.0 Ethernet controller: Intel Corp. 82540EP Gigabit Ethernet
Controller (Mobile) (rev 03)
0000:02:02.0 Network controller: Intel Corp. PRO/Wireless LAN 2100 3B Mini PCI
Adapter (rev 04)

With the 2.6.10 kernel.

[Loïc d'Anterroches (diaeresis+bugs)]

Sorry, I did not precised that eth1 is the wireless connection in my case.

[Loïc d'Anterroches (diaeresis+bugs)]

I have upgraded again to hoary to test another time.
I do not have this problem anymore. As I went back to warty in the middle I
can't tell what has changed.
From my point you can consider the bug as fixed.

$ uname -a
Linux cargo 2.6.10-4-686 #1 Fri Feb 25 05:28:14 UTC 2005 i686 GNU/Linux

[Matt Zimmerman (mdz)]

Thanks for testing

[Henning Best (hbest)]

Same problem with Wireless USB Adaptor on hoary with stock kernel 2.6.10-5-k7:
The computer won't reboot or shutdown and endlessly reports the following Message

unregister_netdevice: waiting for wlan0 to become free. Usage count = 1

So I suppose, it's not a specific problem of the former reporter's ipw2100 hardware.

Regards,

Henning Best

$ uname -a
Linux nisim 2.6.10-5-k7 #1 Thu Mar 24 15:28:01 GMT 2005 i686 GNU/Linux

$ lsusb
Bus 001 Device 003: ID 2001:3700 D-Link Corp. [hex] DWL-122 802.11b

[Matt Zimmerman (mdz)]

As you are using a different driver and different hardware, this may be a
different bug.

Please don't change the target milestone field.

[Frido Roose (frido)]

(In reply to comment #2)
> I have upgraded again to hoary to test another time.
> I do not have this problem anymore. As I went back to warty in the middle I
> can't tell what has changed.
> From my point you can consider the bug as fixed.
>
> $ uname -a
> Linux cargo 2.6.10-4-686 #1 Fri Feb 25 05:28:14 UTC 2005 i686 GNU/Linux

(In reply to comment #2)
> I have upgraded again to hoary to test another time.
> I do not have this problem anymore. As I went back to warty in the middle I
> can't tell what has changed.
> From my point you can consider the bug as fixed.
>
> $ uname -a
> Linux cargo 2.6.10-4-686 #1 Fri Feb 25 05:28:14 UTC 2005 i686 GNU/Linux

I don't think this problem is fixed. It might be related to
http://lists.debian.org/debian-kernel/2005/02/msg00464.html
I have a clean Hoary install on my laptop, and when I try to go into standby, I
doesn't... After quite some debugging to find out what could be the problem,
these are my conclusions:

After some debugging with /etc/acpi/prepare.sh, I found that I tries to discover
the network interfaces, and then does an ifdown for each interface. After that
I does an rmmod for each nic module. When the loopback interface is shut down,
I can't do an rmmod ndiswrapper anymore, I get the kernel message: waiting wlan0
to become free.

I can manually reproduce the problem like this:

So:
ifdown lo
ifdown wlan0
rmmod ndiswrapper
=> kernel message + ifconfig hangs, only reboot helps

If:
(leave lo up)
ifdown wlan0
rmmod ndiswrapper
=> module is unloaded immediatelly

I can reproduce this with eth0 too, so it's not wireless or ndiswrapper related.
 Just by doing the same for eth0 instead of wlan0.

[Paulus (donmatteo)]

I can reproduce this exactly as described by Frido on hoary final. Suspending hangs if lo was brought down before. The
following one-line patch for /etc/acpi/prepare.sh fixes suspending in hoary for me:

--- /etc/acpi/prepare.sh 2005-04-01 14:37:46.000000000 +0200
+++ prepare.sh 2005-06-04 01:00:18.078620840 +0200
@@ -4,7 +4,7 @@
 touch /var/lock/acpid

 # Find the currently running network interfaces...
-INTERFACES=`/sbin/ifconfig | awk '/^[^ ]+/ {print $1}'`
+INTERFACES=`/sbin/ifconfig | grep -v '^lo' | awk '/^[^ ]+/ {print $1}'`

 # And shut them down
 for x in $INTERFACES; do

[Matt Zimmerman (mdz)]

Does this still happen with the updated ipw2100 driver in linux-image-2.6.12-*
in breezy/universe?

[Amos Brocco (mriya3)]

I have the same problem with self compiled atmel-wlandriver 3.4.1.0
(http://atmelwlandriver.sourceforge.net/news.html) and a PCMCIA wireless Siemens
PC-Card 11.
When shutting down my notebook (Toshiba Satellite 2410) a message similar to the
one reported (nregister_netdevice: waiting for atml0 ...) is shown and there is
no way of cleanly shutdown the computer (I have to force disk sync and reboot
with ctrl+alt+sysrq+...).

If I disable the wireless interface (ifdown atml0) before rebooting or shutting
down there are no problems.

I'm using Hoary

uname -a returns:
Linux satellite 2.6.10-5-686 #1 Fri Jun 24 17:33:34 UTC 2005 i686 GNU/Linux

lspci returns :
0000:00:00.0 Host bridge: Intel Corp. 82845 845 (Brookdale) Chipset Host Bridge
(rev 04)
0000:00:01.0 PCI bridge: Intel Corp. 82845 845 (Brookdale) Chipset AGP Bridge
(rev 04)
0000:00:1d.0 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 02)
0000:00:1d.1 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #2) (rev 02)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 42)
0000:00:1f.0 ISA bridge: Intel Corp. 82801CAM ISA Bridge (LPC) (rev 02)
0000:00:1f.1 IDE interface: Intel Corp. 82801CAM IDE U100 (rev 02)
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801CA/CAM AC'97 Audio
Controller (rev 02)
0000:00:1f.6 Modem: Intel Corp. 82801CA/CAM AC'97 Modem Controller (rev 02)
0000:01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 420
Go] (rev a3)
0000:02:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000
Controller (PHY/Link)
0000:02:08.0 Ethernet controller: Intel Corp. 82801CAM (ICH3) PRO/100 VE (LOM)
Ethernet Controller (rev 42)
0000:02:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to Cardbus
Bridge with ZV Support (rev 32)
0000:02:0b.1 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to Cardbus
Bridge with ZV Support (rev 32)
0000:02:0d.0 System peripheral: Toshiba America Info Systems SD TypA Controller
(rev 03)

cardctl ident returns:
Socket 0:
  no product info available
Socket 1:
  product info: "IEEE 802.11b", "Wireless LAN Card S"
  manfid: 0x0000, 0x0000
  function: 6 (network)

lsmod returns: (atmelwlan driver is pcmf504_2958)
Module Size Used by
binfmt_misc 11496 1
ipv6 257888 17
proc_intf 3908 0
cpufreq_userspace 4348 1
cpufreq_ondemand 6140 0
cpufreq_powersave 1632 0
af_packet 21992 2
pcmf504_2958 110676 1
pcmcia 22244 5 pcmf504_2958
nfsd 207232 8
exportfs 6080 1 nfsd
lockd 63944 2 nfsd
sunrpc 149124 2 nfsd,lockd
video 15972 0
sony_acpi 5928 0
pcc_acpi 11008 0
button 6480 0
battery 9988 0
container 4320 0
ac 4676 0
yenta_socket 21344 1
pcmcia_core 57984 3 pcmf504_2958,pcmcia,yenta_socket
e100 33920 0
mii 4896 1 e100
ohci1394 34596 0
snd_intel8x0 32352 2
snd_ac97_codec 74144 1 snd_intel8x0
us...

[Ben Collins (ben-collins)]

So this has been worked around in acpi scripts (to let the machine
reboot/shutdown), it's just that we need to find out why unloading a network
driver wont work after doing ifdown lo?

[Matt Zimmerman (mdz)]

(In reply to comment #10)
> So this has been worked around in acpi scripts (to let the machine
> reboot/shutdown), it's just that we need to find out why unloading a network
> driver wont work after doing ifdown lo?

Correct. At least, we need to find out whether it's our kernel's fault or that
of the third-party NDIS driver, in which case we can't do anything about it.

[Matt Zimmerman (mdz)]

*** Bug 20338 has been marked as a duplicate of this bug. ***

[Christian Elkjaer (c.elkjaer)]

I have been using Hoary and Breezy with my IBM Thinkpad T41 that also has an
ipw2100 wireless NIC. However, I have not experienced the problem described in
this bug report.

Just to let you know.

[Ben Collins (ben-collins)]

(In reply to comment #13)
> I have been using Hoary and Breezy with my IBM Thinkpad T41 that also has an
> ipw2100 wireless NIC. However, I have not experienced the problem described in
> this bug report.
>
> Just to let you know.

Since the acpi scripts work around this, did you try the manual test case (ifdown lo...)?

[Lionel Dricot (ploum-deactivatedaccount)]

Today, I tried to upgrade my Compaq Presario 1245 with PCMCIA wireless card (see
https://wiki.ubuntu.com/LaptopTestingTeam/CompaqPresario1245 )

During the upgrade, the card service would not stop, allowing upgrade, due to
this bug.

The worst thing is that there's no way to stop this without rebooting the
computer. All the related processes are not responding, even to kill -9.
If you try an "ifconfig", it will wait forever without any chance to kill the
ifconfig process.

I think this bug might be really bad for people upgrading their laptop...

[Ben Collins (ben-collins)]

I tried reproducing this using the examples. I do not have a wireless card, so I was just trying to do it
with eth0 (since the report claimed that it worked with that too).

However, things unloaded for me fine. I did:

ifdown lo
ifdown eth0
rmmod ndiswrapper
rmmod 8139too (my eth0 driver)

So this has something to do with ndiswrapper. Since I have not done anything to get ndiswrapper working, it
isn't initializing any devices. Probably why I can't reproduce it.

[Ben Collins (ben-collins)]

Created an attachment (id=3800)
NDISWrapper v1.1 kernel module

Compiled against kernel 2.6.12-8

[Ben Collins (ben-collins)]

Please try the attached kernel module. Our current ndiswrapper is v1.1, and this
is v1.2.

To do this, remove the old module just as you did in your example, and then do
"insmod ndiswrapper.ko". Make sure to gunzip the downloaded attachment first.

Try to reproduce using this module. Thanks

[Lionel Dricot (ploum-deactivatedaccount)]

In my case, I have the problem without ndiswrapper. I don't use it and I don't
even have it on my computer. It's a Prism54h PCMCIA card.

I've seen that, when those messages occured, the process pccardctl was taking
100% of the CPU. So I believe it's related to PCMCIA.

[Ben Collins (ben-collins)]

As of right now, I've no solid evidence as to the cause of this problem, and no
way to reproduce it. The system scripts have been modified to avoid the problem
with standard usage. I'm lowering the priority of this bug, and I'll revisit it
post-breezy when we start working with 2.6.14-rc's.

[Ben Collins (ben-collins)]

This bug has been flagged because it is old and possibly inactive. It may or may
not be fixed in the latest release (Breezy Badger 5.10). It is being marked as
"NEEDSINFO". In two weeks time, if the bug is not updated back to "NEW" and
validated against Breezy, it will be closed.

This is needed in order to help manage the current bug list for the kernel. We
would like to fix all bugs, but need users to test and help with debugging.

If this change was in error for this bug, please respond and make the
appropriate change (or email <email address hidden> if you cannot make the
change).

Thanks for your help.

[Ben Collins (ben-collins)]

Please retest this with either dapper kernel, or wait for dapper flight 2 cd's
(within a few days).

[Martin Bergner (martin-bergner)]

There has not been an answer for over 3 months, I will close this bug because of its age, feel free to reopen if the problem still exists.