Comment 54 for bug 569841

more progress... wicd was competing with network-manager!

I do feel like an idiot about this, but here we go:
Way back in May, when we suspected network-manager was the issue, somebody suggested to use "wicd" instead. This did not help, and we quickly came to the conclusion that the issue was the intel driver.

One of the issue I have had, is that it would take 5 or 10 minutes before getting a connection, get a connection, and within 10 seconds loose that connection, and it would do that again and again. Eventually, it would connect and stay connected. Tonight, my disk kept spinning and stopping while I was just reading a long email, wondering what was going on, I ran top, and found "wicd" running (don't think that's what made the disk spin up, but that's a different story). I removed wicd, and tried suspend/resume cycles several times, and it now takes only 5 to 10 minutes to connect, once it connects, it does not loose that connection again. I am now able to connect with 2.6.35, in less than 10 minutes, (and if not, rebooting fixes it). And I have done more testing with 2.6.35, it does not fail under load.

To check:
dpkg -l wicd-daemon

If it lists it with "ii" at the front, it means it is installed. then:

dpkg -r wicd-daemon wicd-gtk

Also, follow the link from Andreas and Martin to download 2.6.35, installing it is as simple as "dpkg -i linux-image-2.6.35*", 2.6.35 does NOT fail under load. It would be nice if Intel fixed that bug in 2.6.32, 33, and 34, but I have a feeling it is not going to happen.