Are you affected by this wireless resume bug?

[aysiu]

Since upgrading my netbook to 10.04, I've noticed a regression, and I'm curious as to what others' experiences of this have been.

Have you also experienced this bug? If so, does it bother you? What workarounds have worked for you, if applicable?

How long does it take you to resume? (It takes my computer anywhere between 15 seconds and 2 minutes with a Broadcom 4312 and the wl driver.)

If you're not experiencing this bug, what wireless card do you have?

Here's the bug report:
network manager slow to reconnect after suspend/resume

P.S. WICD hasn't given me any faster a resume after sleep.

[mamamia88]

it usually reconnects pretty quickly. probably 15 seconds tops. never actually timed it. btw it's a broadcom card not sure which one

[aysiu]

it usually reconnects pretty quickly. probably 15 seconds tops. never actually timed it. btw it's a broadcom card not sure which one

The bug isn't that it times out but that it just takes a really long time to reconnect.

By the way, do you mind if I ask what wireless card you're using?

[FuturePilot]

Every once in a while that will happen to me on my laptop. It has an Intel 3945ABG card. It happens a lot less frequently than it used to though. However, I've never had it happen on my netbook which has a Broadcom BCM4312 card and I've never had it happen on my old laptop which has an Atheros card. Both are always connected before I can unlock the screen.

When it does happen though, usually right clicking on network manager and disabling and re-enabling wireless usually gives it good kick.

[PuddingKnife]

I do not have it, but my wireless is disabled every time I power on the laptop.

[aysiu]

By the way, the /usr/lib/pm-utils/sleep.d/55NetworkManager file says this at the top:

# If we are running NetworkManager, tell it we are going to sleep.
# TODO: Make NetworkManager smarter about how to handle sleep/resume
# If we are asleep for less time than it takes for TCP to reset a
# connection, and we are assigned the same IP on resume, we should
# not break established connections. Apple can do this, and it is
# rather nifty.

Yes, Apple does do this on Macs, and it is rather nifty. Too bad Ubuntu's undergone several releases with this comment in the file and no actual progress on fixing this problem.

[NightwishFan]

The resume bug is probably an upstream issue, perhaps talk with the driver developers themselves.

[witeshark17]

My laptop resumes essentially instantly, in fact it appears to leave the connection active in sleep. My wireless card:

Dell 1397 Wireless-G

[seenthelite]

Intel wifi link 5100 AGN from suspend 6 seconds with Network Manager
Broadcom BCM4328 a/b/g/n from suspend 10 seconds with WICD

Both on 5GHz N, they connect to the access point instantly and acquiring IP address takes the time.

[witeshark17]

I looked more carefully, the wireless card is disconnected in sleep, but reconnects quickly with the last used WiFi