Hi - 
I'm running current Karmic 9.10 beta (2.6.31-14-generic), and am experiencing 
this problem. What's odd is that I had thought this issue had gone away in 
Jaunty, but upon doing a fresh install of karmic beta, it's back. It seems I 
have a 50/50 chance of having the iwl3945 come back upon resume. I've compared 
syslogs of a successful wakeup vs. a failed one, and the difference seems to 
occur here:

Here is the failed entry:
Oct 15 17:26:08 lappy586 NetworkManager: <info>  Waking up...
Oct 15 17:26:08 lappy586 NetworkManager: <info>  (wlan0): now managed
Oct 15 17:26:08 lappy586 NetworkManager: <info>  (wlan0): device state change: 
1 -> 2 (reason 2)
Oct 15 17:26:08 lappy586 NetworkManager: <info>  (wlan0): bringing up device.
Oct 15 17:26:08 lappy586 kernel: [ 7391.036019] iwl3945 0000:0c:00.0: MAC is in 
deep sleep!.  CSR_GP_CNTRL = 0xFFFFFFFF
Oct 15 17:26:08 lappy586 kernel: [ 7391.036019] iwl3945 0000:0c:00.0: MAC is in 
deep sleep!.  CSR_GP_CNTRL = 0xFFFFFFFF
Oct 15 17:26:08 lappy586 kernel: [ 7391.036019] iwl3945 0000:0c:00.0: MAC is in 
deep sleep!.  CSR_GP_CNTRL = 0xFFFFFFFF
Oct 15 17:26:08 lappy586 kernel: [ 7391.086873] iwl3945 0000:0c:00.0: MAC is in 
deep sleep!.  CSR_GP_CNTRL = 0xFFFFFFFF
Oct 15 17:26:08 lappy586 kernel: [ 7391.198189] iwl3945 0000:0c:00.0: MAC is in 
deep sleep!.  CSR_GP_CNTRL = 0xFFFFFFFF


and here is a successful wakeup (discarding non-NetworkManager messages):
Oct 15 17:44:38 lappy586 NetworkManager: <info>  Waking up...
Oct 15 17:44:38 lappy586 NetworkManager: <info>  (wlan0): now managed
Oct 15 17:44:38 lappy586 NetworkManager: <info>  (wlan0): device state change: 
1 -> 2 (reason 2)
Oct 15 17:44:38 lappy586 NetworkManager: <info>  (wlan0): bringing up device.
Oct 15 17:44:38 lappy586 kernel: [ 1048.313312] Registered led device: 
iwl-phy0::radio
Oct 15 17:44:38 lappy586 kernel: [ 1048.313330] Registered led device: 
iwl-phy0::assoc
Oct 15 17:44:38 lappy586 kernel: [ 1048.313386] Registered led device: 
iwl-phy0::RX
Oct 15 17:44:38 lappy586 kernel: [ 1048.313402] Registered led device: 
iwl-phy0::TX
Oct 15 17:44:38 lappy586 kernel: [ 1048.341468] ADDRCONF(NETDEV_UP): wlan0: 
link is not ready
Oct 15 17:44:38 lappy586 NetworkManager: <info>  (wlan0): preparing device.
Oct 15 17:44:38 lappy586 NetworkManager: <info>  (wlan0): deactivating device 
(reason: 2).
Oct 15 17:44:38 lappy586 NetworkManager: <info>  Unmanaged Device found; state 
CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 15 17:44:38 lappy586 NetworkManager: <info>  Unmanaged Device found; state 
CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 15 17:44:38 lappy586 NetworkManager: <info>  (eth0): now managed

--greg


** Changed in: linux (Ubuntu)
       Status: Incomplete => New

-- 
iwl3945 sometimes fails to resume after suspend
https://bugs.launchpad.net/bugs/297385
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