wireless doesn't come back up after resume from suspend

T400/410/420 and T500/510/520 series specific matters only
Post Reply
Message
Author
firebird
Posts: 1
Joined: Sun Jun 17, 2012 11:53 am
Location: washington, dc

wireless doesn't come back up after resume from suspend

#1 Post by firebird » Sun Jun 17, 2012 12:14 pm

I have a T400 running Debian Squeeze with the built in Intel 5100 wifi card.

Everything works fine except that when I suspend and resume many hours later, the wifi doesn't come back up. If I suspend and resume immediately (or even after 5mins), the wifi comes back up automatically.

I have to manually do ifdown wlan0 and ifup wlan0 to restablish the wifi connection when it doesn't come back up.

Notice that below, after the machine is up, it knows the wifi router is there....but it just isn't connected to it. Instead, a new "wifi" device appears in ifconfig and it looks like it connects to that (dont know what that is).

Here the logs from dmesg:

Code: Select all

[37490.822554] ehci_hcd 0000:00:1d.7: PCI INT D -> GSI 19 (level, low) -> IRQ 19
[37490.822560] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[37490.822571] pci 0000:00:1e.0: setting latency timer to 64
[37490.822588] ahci 0000:00:1f.2: setting latency timer to 64
[37491.384058] sd 0:0:0:0: [sda] Starting disk
[37493.356730] ata1.00: configured for UDMA/100
[37493.404480] Registered led device: iwl-phy0::radio
[37493.404497] Registered led device: iwl-phy0::assoc
[37493.404514] Registered led device: iwl-phy0::RX
[37493.404529] Registered led device: iwl-phy0::TX
[37493.696052] usb 3-1: reset low speed USB device using uhci_hcd and address 2
[37494.003338] PM: Finishing wakeup.
[37494.003341] Restarting tasks ... done.
[37495.196582] wlan0: deauthenticating from ##:##:##:##:##:## by local choice (reason=3)
[37495.248438] bridge-wlan0: disabling the bridge on dev down
[37495.264027] bridge-wlan0: down
[37495.264068] bridge-wlan0: detached
[37495.536387] Registered led device: iwl-phy0::radio
[37495.536415] Registered led device: iwl-phy0::assoc
[37495.536461] Registered led device: iwl-phy0::RX
[37495.536505] Registered led device: iwl-phy0::TX
[37495.558790] ADDRCONF(NETDEV_UP): wlan0: link is not ready

iwconfig shows this (notice, it sees the wifi router):

Code: Select all

wlan0     IEEE 802.11abgn  ESSID:"Wifi"
          Mode:Managed  Access Point: Not-Associated   Tx-Power=15 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:####-####-####-####-####-####-##
          Power Management:off
ifconfig shows this (notice the wlan0:avahi entry which disappears after reconnecting manually):

Code: Select all

wlan0     Link encap:Ethernet  HWaddr ##:##:##:##:##:##
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:945091 errors:0 dropped:0 overruns:0 frame:0
          TX packets:569025 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1274506011 (1.1 GiB)  TX bytes:65553562 (62.5 MiB)

wlan0:avahi Link encap:Ethernet  HWaddr ##:##:##:##:##:##
          inet addr:###.###.#.##  Bcast:###.###.255.255  Mask:255.255.0.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
syslog shows this:

Code: Select all

Jun 17 12:32:24 thinkpad kernel: [37493.404480] Registered led device: iwl-phy0::radio
Jun 17 12:32:24 thinkpad kernel: [37493.404497] Registered led device: iwl-phy0::assoc
Jun 17 12:32:24 thinkpad kernel: [37493.404514] Registered led device: iwl-phy0::RX
Jun 17 12:32:24 thinkpad kernel: [37493.404529] Registered led device: iwl-phy0::TX
Jun 17 12:32:24 thinkpad kernel: [37493.696052] usb 3-1: reset low speed USB device using uhci_hcd and address 2
Jun 17 12:32:24 thinkpad kernel: [37494.003338] PM: Finishing wakeup.
Jun 17 12:32:24 thinkpad kernel: [37494.003341] Restarting tasks ... done.
Jun 17 12:32:25 thinkpad acpid: client 1471[0:0] has disconnected
Jun 17 12:32:25 thinkpad acpid: client connected from 1471[0:0]
Jun 17 12:32:25 thinkpad acpid: 1 client rule loaded
Jun 17 12:32:25 thinkpad dhclient: Listening on LPF/wlan0/##:##:##:##:##:##
Jun 17 12:32:25 thinkpad dhclient: Sending on   LPF/wlan0/##:##:##:##:##:##
Jun 17 12:32:25 thinkpad dhclient: Sending on   Socket/fallback
Jun 17 12:32:25 thinkpad dhclient: DHCPRELEASE on wlan0 to 192.168.1.1 port 67
Jun 17 12:32:25 thinkpad dhclient: send_packet: Operation not permitted
Jun 17 12:32:26 thinkpad kernel: [37495.196582] wlan0: deauthenticating from ##:##:##:##:##:## by local choice (reason=3)
Jun 17 12:32:26 thinkpad vmnetBridge: RTM_NEWLINK: name:wlan0 index:3 flags:0x00001002
Jun 17 12:32:26 thinkpad vmnetBridge: Removing interface wlan0 index:3
Jun 17 12:32:26 thinkpad kernel: [37495.248438] bridge-wlan0: disabling the bridge on dev down
Jun 17 12:32:26 thinkpad vmnetBridge: Stopped bridge wlan0 to virtual network 0.
Jun 17 12:32:26 thinkpad kernel: [37495.264027] bridge-wlan0: down
Jun 17 12:32:26 thinkpad kernel: [37495.264068] bridge-wlan0: detached
Jun 17 12:32:26 thinkpad vmnetBridge: RTM_NEWLINK: name:wlan0 index:3 flags:0x00001002
Jun 17 12:32:26 thinkpad kernel: [37495.536387] Registered led device: iwl-phy0::radio
Jun 17 12:32:26 thinkpad kernel: [37495.536415] Registered led device: iwl-phy0::assoc
Jun 17 12:32:26 thinkpad kernel: [37495.536461] Registered led device: iwl-phy0::RX
Jun 17 12:32:26 thinkpad kernel: [37495.536505] Registered led device: iwl-phy0::TX
Jun 17 12:32:26 thinkpad vmnetBridge: RTM_NEWLINK: name:wlan0 index:3 flags:0x00001003
Jun 17 12:32:26 thinkpad kernel: [37495.558790] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jun 17 12:32:26 thinkpad dhclient: Listening on LPF/wlan0/##:##:##:##:##:##
Jun 17 12:32:26 thinkpad dhclient: Sending on   LPF/wlan0/##:##:##:##:##:##
Jun 17 12:32:26 thinkpad dhclient: Sending on   Socket/fallback
Jun 17 12:32:29 thinkpad dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jun 17 12:32:32 thinkpad dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jun 17 12:32:35 thinkpad dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jun 17 12:32:42 thinkpad dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Jun 17 12:32:55 thinkpad dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Jun 17 12:33:13 thinkpad dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
Jun 17 12:33:30 thinkpad dhclient: No DHCPOFFERS received.
Jun 17 12:33:30 thinkpad dhclient: No working leases in persistent database - sleeping.
Jun 17 12:33:30 thinkpad avahi-autoipd(wlan0)[5691]: Found user 'avahi-autoipd' (UID 101) and group 'avahi-autoipd' (GID 103).
Jun 17 12:33:30 thinkpad avahi-autoipd(wlan0)[5691]: Successfully called chroot().
Jun 17 12:32:26 thinkpad vmnetBridge: RTM_NEWLINK: name:wlan0 index:3 flags:0x00001002
Jun 17 12:32:26 thinkpad kernel: [37495.536387] Registered led device: iwl-phy0::radio
Jun 17 12:32:26 thinkpad kernel: [37495.536415] Registered led device: iwl-phy0::assoc
Jun 17 12:32:26 thinkpad kernel: [37495.536461] Registered led device: iwl-phy0::RX
Jun 17 12:32:26 thinkpad kernel: [37495.536505] Registered led device: iwl-phy0::TX
Jun 17 12:32:26 thinkpad vmnetBridge: RTM_NEWLINK: name:wlan0 index:3 flags:0x00001003
Jun 17 12:32:26 thinkpad kernel: [37495.558790] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jun 17 12:32:26 thinkpad dhclient: Listening on LPF/wlan0/##:##:##:##:##:##
Jun 17 12:32:26 thinkpad dhclient: Sending on   LPF/wlan0/##:##:##:##:##:##
Jun 17 12:32:26 thinkpad dhclient: Sending on   Socket/fallback
Jun 17 12:32:29 thinkpad dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jun 17 12:32:32 thinkpad dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jun 17 12:32:35 thinkpad dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jun 17 12:32:42 thinkpad dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Jun 17 12:32:55 thinkpad dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Jun 17 12:33:13 thinkpad dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
Jun 17 12:33:30 thinkpad dhclient: No DHCPOFFERS received.
Jun 17 12:33:30 thinkpad dhclient: No working leases in persistent database - sleeping.
Jun 17 12:33:30 thinkpad avahi-autoipd(wlan0)[5691]: Found user 'avahi-autoipd' (UID 101) and group 'avahi-autoipd' (GID 103).
Jun 17 12:33:30 thinkpad avahi-autoipd(wlan0)[5691]: Successfully called chroot().
Jun 17 12:33:30 thinkpad avahi-autoipd(wlan0)[5691]: Successfully dropped root privileges.
Jun 17 12:33:30 thinkpad avahi-autoipd(wlan0)[5691]: Starting with address ###.###.#.##
Jun 17 12:33:36 thinkpad avahi-autoipd(wlan0)[5691]: Callout BIND, address ###.###.#.## on interface wlan0
Jun 17 12:33:36 thinkpad vmnetBridge: RTM_NEWROUTE: index:3
Jun 17 12:33:40 thinkpad avahi-autoipd(wlan0)[5691]: Successfully claimed IP address ###.###.#.##
Jun 17 12:33:49 thinkpad dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Jun 17 12:33:53 thinkpad dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
Jun 17 12:34:04 thinkpad dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Jun 17 12:34:16 thinkpad dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
Jun 17 12:34:31 thinkpad dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
Jun 17 12:34:41 thinkpad dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
Jun 17 12:34:50 thinkpad dhclient: No DHCPOFFERS received.
Jun 17 12:34:50 thinkpad dhclient: No working leases in persistent database - sleeping.

I have tried placing a ifdown ifup of wlan0 script in /etc/pm/sleep.d/ but that doesn't help. I also tried one fix where you have to put a config = "iwlagn" and that didn't work either.

Ramses
Posts: 1
Joined: Mon Jun 18, 2012 1:59 am
Location: Valkeakoski, Finland

Re: wireless doesn't come back up after resume from suspend

#2 Post by Ramses » Mon Jun 18, 2012 2:11 am

Have you tried newer iwlwifi package from backports? http://packages.debian.org/search?keywo ... -backports . I have T500 running Debian Squeeze, but I don't usually suspend machine for long periods of time, so have not personally seen this problem.

Post Reply
  • Similar Topics
    Replies
    Views
    Last post

Return to “ThinkPad T400/410/420 and T500/510/520 Series”

Who is online

Users browsing this forum: No registered users and 1 guest