I thought I'd chip in that I have the same intermittent problems on a
Thinkpad T60 after resuming from suspend.

Here's the messages from the driver after resume (slightly edited to
include just the relevant bits).  The laptop was suspended for about 2
hours before resume.

[    3.743679] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection 
driver for Linux, 1.2.25
[    3.743687] iwl3945: Copyright(c) 2003-2007 Intel Corporation
[    3.743851] iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
[    3.806361] wmaster0: Selected rate control algorithm 'iwl-3945-rs'
[    4.178487] iwl3945: Tunable channels: 11 802.11bg, 13 802.11a channels
[    4.181676] Registered led device: iwl-phy0:RX
[    4.181698] Registered led device: iwl-phy0:TX
[    4.186622] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[    4.452017] Registered led device: iwl-phy0:RX
[    4.452041] Registered led device: iwl-phy0:TX
[    4.457973] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   10.810461] iwl3945: Radio Frequency Kill Switch is On:
[   10.810467] Kill switch must be turned off for wireless networking to work.
[   10.928410] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up 
NIC
[   10.978228] iwl3945: MAC is in deep sleep!
[   10.978296] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up 
NIC
[   11.038074] iwl3945: MAC is in deep sleep!
[   11.038118] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up 
NIC
[   11.097914] iwl3945: MAC is in deep sleep!
[   11.207999] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up 
NIC
[   53.596763] iwl3945: No space for Tx
[   53.596775] iwl3945: Error sending REPLY_CARD_STATE_CMD: 
iwl3945_enqueue_hcmd failed: -28
[   55.118839] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up 
NIC

I tried toggling the physical hardware kill switch, which has helped in
the past, but no luck.  Then I suspended and immediately resumed in the
hope that it would fix the issue upon coming back.  Luckily, it did.
Here's the log from after that resume:

[    3.678740] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection 
driver for Linux, 1.2.25
[    3.678749] iwl3945: Copyright(c) 2003-2007 Intel Corporation
[    3.680391] iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
[    3.745056] wmaster0: Selected rate control algorithm 'iwl-3945-rs'
[    3.825019] iwl3945: Tunable channels: 11 802.11bg, 13 802.11a channels
[    3.827920] Registered led device: iwl-phy0:RX
[    3.827954] Registered led device: iwl-phy0:TX
[    3.839250] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[    4.187407] Registered led device: iwl-phy0:RX
[    4.187429] Registered led device: iwl-phy0:TX
[    4.194779] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[    9.257513] wlan0: Initial auth_alg=0
[    9.257524] wlan0: authenticate with AP 00:0c:41:66:23:0e
[    9.258702] wlan0: RX authentication from 00:0c:41:66:23:0e (alg=0 
transaction=2 status=0)
[    9.258709] wlan0: authenticated
[    9.258714] wlan0: associate with AP 00:0c:41:66:23:0e
[    9.260589] wlan0: authentication frame received from 00:0c:41:66:23:0e, but 
not in authenticate state - ignored
[    9.261721] wlan0: authentication frame received from 00:0c:41:66:23:0e, but 
not in authenticate state - ignored
[    9.262465] wlan0: RX AssocResp from 00:0c:41:66:23:0e (capab=0x11 status=0 
aid=1)
[    9.262471] wlan0: associated
[    9.265723] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   14.880956] wlan0: no IPv6 routers present

Don't know if any of that will help, but at least it's a data point.

I'm not up to trying the new kernel suggested right now, as I've just
recently switched to Ubuntu from another distro after getting fed up
with it (various reasons).  My system is now much nicer and generally
more stable, so I don't feel like tinkering.  If the issue starts to
become more than a minor nuisance once in a while, I might give it a try
though.

-- 
iwl3945 can't wake up Intel(R) PRO/Wireless 3945 mini card
https://bugs.launchpad.net/bugs/203329
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to