Comment 6 for bug 12558

(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.