Hi, I recently installed Wheezy with XFCE desktop on my Thinkpad T400 laptop. Things work great, but I notice that suspend-to-RAM has some quirks. I chose to set "suspend" as the action "when the sleep button is pressed" (see xfce power manager). Here's what happens if I press the sleep button (special Fn+F4 combination):
*) the computer will wait for about 2 seconds before the screen blanking is activated and the computer eventually goes to sleep. I don't understand why the extra 2 second wait. Here's the output of syslog, which may help: Jun 23 09:29:56 wirawan1 NetworkManager[3935]: <info> sleep requested (sleeping: no enabled: yes) Jun 23 09:29:56 wirawan1 NetworkManager[3935]: <info> sleeping or disabling... Jun 23 09:29:56 wirawan1 NetworkManager[3935]: <info> (eth0): now unmanaged Jun 23 09:29:56 wirawan1 NetworkManager[3935]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37] Jun 23 09:29:56 wirawan1 NetworkManager[3935]: <info> (eth0): cleaning up... Jun 23 09:29:56 wirawan1 NetworkManager[3935]: <info> (eth0): taking down device. Jun 23 09:29:56 wirawan1 kernel: [156983.772225] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X Jun 23 09:29:56 wirawan1 NetworkManager[3935]: <info> (wlan0): now unmanaged Jun 23 09:29:56 wirawan1 NetworkManager[3935]: <info> (wlan0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Jun 23 09:29:56 wirawan1 NetworkManager[3935]: <info> (wlan0): deactivating device (reason 'sleeping') [37] Jun 23 09:29:56 wirawan1 kernel: [156983.961505] wlan0: deauthenticating from 00:90:4c:7e:00:6e by local choice (reason=3) Jun 23 09:29:56 wirawan1 kernel: [156983.981670] cfg80211: Calling CRDA to update world regulatory domain Jun 23 09:29:56 wirawan1 avahi-daemon[3772]: Withdrawing address record for 192.168.0.178 on wlan0. Jun 23 09:29:56 wirawan1 avahi-daemon[3772]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.178. Jun 23 09:29:56 wirawan1 avahi-daemon[3772]: Interface wlan0.IPv4 no longer relevant for mDNS. Jun 23 09:29:56 wirawan1 NetworkManager[3935]: <info> (wlan0): cleaning up... Jun 23 09:29:56 wirawan1 NetworkManager[3935]: <info> (wlan0): taking down device. Jun 23 09:29:56 wirawan1 wpa_supplicant[4079]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3 Jun 23 09:29:56 wirawan1 kernel: [156983.999553] cfg80211: World regulatory domain updated: Jun 23 09:29:56 wirawan1 kernel: [156983.999557] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Jun 23 09:29:56 wirawan1 kernel: [156983.999560] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Jun 23 09:29:56 wirawan1 kernel: [156983.999563] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Jun 23 09:29:56 wirawan1 kernel: [156983.999566] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Jun 23 09:29:56 wirawan1 kernel: [156983.999569] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Jun 23 09:29:56 wirawan1 kernel: [156983.999572] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Jun 23 09:29:56 wirawan1 avahi-daemon[3772]: Interface wlan0.IPv6 no longer relevant for mDNS. Jun 23 09:29:56 wirawan1 avahi-daemon[3772]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::221:6bff:fec6:a68. Jun 23 09:29:56 wirawan1 avahi-daemon[3772]: Withdrawing address record for fe80::221:6bff:fec6:a68 on wlan0. Jun 23 09:29:56 wirawan1 dbus[3713]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) Jun 23 09:29:56 wirawan1 dbus[3713]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jun 23 09:29:58 wirawan1 kernel: [156985.533439] PM: Syncing filesystems ... done. Jun 23 09:29:58 wirawan1 kernel: [156985.642155] PM: Preparing system for mem sleep Jun 23 09:29:58 wirawan1 ntpd[3971]: Deleting interface #77 wlan0, fe80::221:6bff:fec6:a68#123, interface stats: received=0, sent=0, dropped=0, active_time=61 secs Jun 23 09:29:58 wirawan1 ntpd[3971]: Deleting interface #76 wlan0, 192.168.0.178#123, interface stats: received=18, sent=18, dropped=0, active_time=61 secs Jun 23 09:29:58 wirawan1 ntpd[3971]: 138.236.128.36 interface 192.168.0.178 -> (none) Jun 23 09:29:58 wirawan1 ntpd[3971]: 204.2.134.163 interface 192.168.0.178 -> (none) Jun 23 09:29:58 wirawan1 ntpd[3971]: 74.123.28.4 interface 192.168.0.178 -> (none) Jun 23 09:29:58 wirawan1 ntpd[3971]: 199.102.46.72 interface 192.168.0.178 -> (none) Jun 23 09:29:58 wirawan1 ntpd[3971]: peers refreshed Jun 24 00:43:55 wirawan1 acpid: client 4013[0:0] has disconnected Jun 24 00:43:55 wirawan1 kernel: [156985.728302] Freezing user space processes ... (elapsed 0.01 seconds) done. Jun 24 00:43:55 wirawan1 kernel: [156985.744175] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. Jun 24 00:43:55 wirawan1 kernel: [156985.760116] PM: Entering mem sleep Jun 24 00:43:55 wirawan1 kernel: [156985.760210] Suspending console(s) (use no_console_suspend to debug) At around 9:29:56 I pushed Fn+F4 so the chain actions began. But it was not until 9:29:58 that PM would kick in and the "moon" LED begins to blink. (The 00:43:55 time marker refers to when the computer was awaken again; apparently the remaining events in the logging system did not flush until after the computer was resumed from suspend.) I notice that this delayed behavior is consistent and always reproducible. Any explanation? This delay does not happen if I use pm-suspend command directly. I was using Debian Squeeze (with kernel backport 3.2 also!) before installing Wheezy and this kind of delay is observed a bit differently. Note I was using GNOME 2.x then, instead of XFCE. With Squeeze, the moon LED blink happens almost right after I pressed the Fn+F4 key but the actual sleep (where the moon LED becomes solid on) happened somewhat longer, but did not feel like as long as 2 seconds here. *) I noticed that the USB ports are still powered even when the computer is suspended to RAM. Is this a normal behavior of T400? Nice for charging other device, but it seemed superfluous and using energy unnecessarily to do this. *) Once I plugged external wireless keyboard/mouse receiver to the laptop when I pressed Fn+F4. The computer went to sleep, but to my surprise, when the external keyboard key is pressed (any key, apparently), the computer wakes up! It did not do this with the internal keyboard. I wonder if the USB has "wake on keypress" feature or something like this. The keyboard on the laptop itself has never responded to key presses if the computer is in the sleep/suspended state. As a note, this behavior does not occur if I plugged the wireless receiver *after* the laptop is suspended, not before. -- Wirawan Purwanto Research Scientist College of William and Mary Physics Department Williamsburg, VA 23187 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CANhMBk1NvwDx307LnjPLmf=foghiiljlv6sbimyefnaiow5...@mail.gmail.com
