Comment 20 for bug 227033

So I tried following the WirelessTroubleShootingGuide that was provided, but it turns out that many of the commands will not run properly because when this bug occurs, sudo doesn't work anymore. Sudo probably opens some kind of socket to work its magic, and that makes it freeze when this bug appears. Also all commands that try to diagnose the problem by opening a connection to somewhere (and that includes DNS) lock up without providing any information and have to be forcefully killed.

And I can confirm that this bug really tends to happen when you do a lot of simultaneous opening/closing of connections (for example, when you download a torrent). I managed not to have any problems for more than a week by nothing more than browsing the web, but as soon as I started using Bittorrent this bug occured twice within a few hours.

Note that on the contrary to what didix says, modprobe -r ndiswrapper followed by modprobe ndiswrapper doesn't work and locks up too.

As to the questions asked in one of the top posts, the answers would be:

* Is this reproducible?
Yes, but not completely at will, trying to saturate the connection with a lot connection creation/destruction will make the bug appear much faster

* If so, what specific steps should we take to recreate this bug?
The best way I've found is to start any bittorrent on a popular torrent and wait a few ours. When the speed drops to zero, you can verify that all the applications that use a socket do not work anymore.

* Is this a laptop or a desktop?
I'm using a desktop.

* Does this happen on a clean boot? (booting from scratch, not using resume/suspend)
It happens from a clean boot.