I think this bug should be reopened, since the problem persists. I'm running Intrepid on a Dell 1330 with the Intel 3495 card:
0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) and I get the same 30 second delay before the wireless connection starts up again after suspending. Here's some perhaps useful info from dmesg... After resuming: [167761.512525] Enabling non-boot CPUs ... [167761.512525] SMP alternatives: switching to SMP code [167761.519438] Booting processor 1/1 ip 6000 [167761.507072] Initializing CPU#1 ... About 6 seconds later, the wifi card comes up (and the LED confirms this): [167767.261785] iwl3945 0000:0c:00.0: enabling device (0000 -> 0002) [167767.261797] iwl3945 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [167767.261867] iwl3945 0000:0c:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10a) [167767.261936] iwl3945 0000:0c:00.0: restoring config space at offset 0x4 (was 0x0, writing 0xf6cff000) [167767.261950] iwl3945 0000:0c:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10) [167767.261969] iwl3945 0000:0c:00.0: restoring config space at offset 0x1 (was 0x100002, writing 0x100106) [167767.344091] Registered led device: iwl-phy0:radio [167767.345162] Registered led device: iwl-phy0:assoc [167767.346115] Registered led device: iwl-phy0:RX [167767.347004] Registered led device: iwl-phy0:TX Here, it seems to try to immediately authenticate with some AP: [167767.347661] eth1: authenticate with AP 00:11:0a:e9:a4:e1 [167767.365973] ADDRCONF(NETDEV_UP): eth1: link is not ready [167767.385833] eth1: authenticate with AP 00:11:0a:e9:a4:e1 [167767.584035] eth1: authenticate with AP 00:11:0a:e9:a4:e1 [167767.784085] eth1: authenticate with AP 00:11:0a:e9:a4:e1 [167767.984028] eth1: authentication with AP 00:11:0a:e9:a4:e1 timed out But that didn't work, and next it tries another one, about 30 seconds later: [167795.730581] eth1: authenticate with AP 00:1e:c7:4f:2f:f1 [167795.732466] eth1: authenticated [167795.732481] eth1: associate with AP 00:1e:c7:4f:2f:f1 [167795.735924] eth1: RX AssocResp from 00:1e:c7:4f:2f:f1 (capab=0x431 status=0 aid=4) [167795.735937] eth1: associated [167795.737327] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [167805.893058] eth1: no IPv6 routers present And that worked. Now, I have no idea what the first AP might be, but it's NOT the network I was just on (I did this test by suspending and resuming my laptop at home, without moving or changing networks). I noticed that my EEE PC on which I just yesterday put 8.10, and which ONLY knows about this AP, reconnects instantly on resume. So I'm wondering if the problem is that NetworkManager is by default attempting to connect to some other AP first, instead of to my main one... I'll be happy to provide more details if needed, I'd really like to see this fixed. -- [hardy] wifi (iwl4965) is slow to return after suspend/resume https://bugs.launchpad.net/bugs/178509 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
