On my Debian/sid laptop, hibernate failed for a couple of times: the screen was cleared with only one message on it (I always get a message, so that I think it's unrelated), but the hard disk and the screen were still on. The only thing I could do was to switch off the machine.
Concerning the second time, Fn-F1 (to put the machine into sleep) didn't seem to have any effect, except that the wicd client was not responding any more: its window was just grey. Immediately after I killed its window, the screen got cleared (see above). I've looked at the logs and here's what I got concerning the kernel and dhclient logs (nothing else interesting in /var/log/syslog): Aug 8 04:58:29 xvii dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1 Aug 8 04:58:29 xvii dhclient: Copyright 2004-2010 Internet Systems Consortium. Aug 8 04:58:29 xvii dhclient: All rights reserved. Aug 8 04:58:29 xvii dhclient: For info, please visit https://www.isc.org/software/dhcp/ Aug 8 04:58:29 xvii dhclient: Aug 8 04:58:29 xvii dhclient: Listening on LPF/wlan0/00:21:6a:47:b3:80 Aug 8 04:58:29 xvii dhclient: Sending on LPF/wlan0/00:21:6a:47:b3:80 Aug 8 04:58:29 xvii dhclient: Sending on Socket/fallback Aug 8 04:58:29 xvii dhclient: DHCPRELEASE on wlan0 to 192.168.0.1 port 67 Aug 8 04:58:29 xvii kernel: [80303.411088] wlan0: deauthenticating from 00:1f:33:89:73:4e by local choice (reason=3) Aug 8 04:58:29 xvii kernel: [80303.442398] cfg80211: Calling CRDA to update world regulatory domain Aug 8 04:58:30 xvii kernel: [80303.537280] ADDRCONF(NETDEV_UP): wlan0: link is not ready Aug 8 04:58:33 xvii kernel: [80306.802635] wlan0: authenticate with 00:1f:33:89:73:4e (try 1) Aug 8 04:58:33 xvii kernel: [80306.805599] wlan0: authenticated Aug 8 04:58:33 xvii kernel: [80306.814294] wlan0: associate with 00:1f:33:89:73:4e (try 1) Aug 8 04:58:33 xvii kernel: [80306.818192] wlan0: RX AssocResp from 00:1f:33:89:73:4e (capab=0x411 status=0 aid=1) Aug 8 04:58:33 xvii kernel: [80306.818201] wlan0: associated Aug 8 04:58:33 xvii kernel: [80306.826674] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Aug 8 04:58:40 xvii kernel: [80313.908978] wlan0: deauthenticating from 00:1f:33:89:73:4e by local choice (reason=3) Aug 8 04:58:40 xvii kernel: [80313.937929] cfg80211: Calling CRDA to update world regulatory domain Aug 8 04:58:40 xvii dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1 Aug 8 04:58:40 xvii dhclient: Copyright 2004-2010 Internet Systems Consortium. Aug 8 04:58:40 xvii dhclient: All rights reserved. Aug 8 04:58:40 xvii dhclient: For info, please visit https://www.isc.org/software/dhcp/ Aug 8 04:58:40 xvii dhclient: Aug 8 04:58:40 xvii dhclient: Listening on LPF/eth0/00:24:e8:97:5f:73 Aug 8 04:58:40 xvii dhclient: Sending on LPF/eth0/00:24:e8:97:5f:73 Aug 8 04:58:40 xvii dhclient: Sending on Socket/fallback Aug 8 04:58:40 xvii dhclient: DHCPRELEASE on eth0 to 192.168.0.1 port 67 Aug 8 04:58:40 xvii dhclient: send_packet: Network is unreachable Aug 8 04:58:40 xvii dhclient: send_packet: please consult README file regarding broadcast address. Aug 8 04:58:40 xvii kernel: [80314.327402] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X Aug 8 04:58:40 xvii kernel: [80314.380407] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X Aug 8 04:58:40 xvii kernel: [80314.381797] ADDRCONF(NETDEV_UP): eth0: link is not ready Aug 8 04:58:51 xvii dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1 Aug 8 04:58:51 xvii dhclient: Copyright 2004-2010 Internet Systems Consortium. Aug 8 04:58:51 xvii dhclient: All rights reserved. Aug 8 04:58:51 xvii dhclient: For info, please visit https://www.isc.org/software/dhcp/ Aug 8 04:58:51 xvii dhclient: Aug 8 04:58:51 xvii dhclient: Listening on LPF/wlan0/00:21:6a:47:b3:80 Aug 8 04:58:51 xvii dhclient: Sending on LPF/wlan0/00:21:6a:47:b3:80 Aug 8 04:58:51 xvii dhclient: Sending on Socket/fallback Aug 8 04:58:51 xvii dhclient: DHCPRELEASE on wlan0 to 192.168.0.1 port 67 Aug 8 04:58:51 xvii dhclient: send_packet: Network is unreachable Aug 8 04:58:51 xvii dhclient: send_packet: please consult README file regarding broadcast address. Aug 8 04:58:51 xvii kernel: [80324.804322] ADDRCONF(NETDEV_UP): wlan0: link is not ready Aug 8 04:58:51 xvii kernel: [80324.993778] ADDRCONF(NETDEV_UP): wlan0: link is not ready Aug 8 04:59:01 xvii dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1 Aug 8 04:59:01 xvii dhclient: Copyright 2004-2010 Internet Systems Consortium. Aug 8 04:59:01 xvii dhclient: All rights reserved. Aug 8 04:59:01 xvii dhclient: For info, please visit https://www.isc.org/software/dhcp/ Aug 8 04:59:01 xvii dhclient: Aug 8 04:59:01 xvii dhclient: Listening on LPF/eth0/00:24:e8:97:5f:73 Aug 8 04:59:01 xvii dhclient: Sending on LPF/eth0/00:24:e8:97:5f:73 Aug 8 04:59:01 xvii dhclient: Sending on Socket/fallback Aug 8 04:59:01 xvii dhclient: DHCPRELEASE on eth0 to 192.168.0.1 port 67 Aug 8 04:59:01 xvii dhclient: send_packet: Network is unreachable Aug 8 04:59:01 xvii dhclient: send_packet: please consult README file regarding broadcast address. Aug 8 04:59:02 xvii kernel: [80335.559194] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X Aug 8 04:59:02 xvii kernel: [80335.612309] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X Aug 8 04:59:02 xvii kernel: [80335.613696] ADDRCONF(NETDEV_UP): eth0: link is not ready I think I switched off the machine just after that. /var/log/wicd/wicd.log contains: 2011/08/08 04:58:29 :: attempting to set hostname with dhclient 2011/08/08 04:58:29 :: using dhcpcd or another supported client may work better 2011/08/08 04:58:40 :: attempting to set hostname with dhclient 2011/08/08 04:58:40 :: using dhcpcd or another supported client may work better 2011/08/08 04:58:51 :: attempting to set hostname with dhclient 2011/08/08 04:58:51 :: using dhcpcd or another supported client may work better 2011/08/08 04:59:01 :: attempting to set hostname with dhclient 2011/08/08 04:59:01 :: using dhcpcd or another supported client may work better So, there seems to be a bad interaction between hibernate and the network, apparently due to wicd: from its logs, one can see that it was respondible for restarting dhclient. I wonder why dhclient is (re)started every 10 seconds. I have the wicd client option "Automatically connect to this network" ticked (though it doesn't work just after booting and starting the wicd client!). Anyone knows where the problem could come from more precisely or has similar problems? Should wicd have detected the hibernate process and avoid restarting dhclient? Is there a kernel bug (some form of race condition) because the hibernate process froze due to the fact that dhclient restarted (or perhaps for some other reason)? FYI, I use the 3.0.0-1-amd64 kernel. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon) -- 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/20110808130403.gc11...@xvii.vinc17.org
