You are not logged in.
Pages: 1
HI everyone,
I've had troubles with hibernation for a few weeks (can't remember precisely when it began). Before describing the problem, I insist that everything used to work fine.
Here is the problem: sometimes, when I wake up my laptop from hibernation, it fails and just reboots. That is, after grub, I have a black screen, and after a short moment it reboots (and the hibernation image is lost).
The tricky part is that I have nothing to help me debug, in particular journalctl gives me about nothing. Here are the entries in journalctl from the moment I ask for hibernation:
sept. 24 01:38:51 ColdFire-Arch NetworkManager[487]: <info> (wlp4s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
sept. 24 01:38:51 ColdFire-Arch NetworkManager[487]: <info> (wlp4s0): deactivating device (reason 'sleeping') [37]
sept. 24 01:38:51 ColdFire-Arch dhcpcd[27213]: received signal TERM from PID 487, stopping
sept. 24 01:38:51 ColdFire-Arch dhcpcd[27213]: wlp4s0: removing interface
sept. 24 01:38:51 ColdFire-Arch NetworkManager[487]: dhcpcd[27213]: received signal TERM from PID 487, stopping
sept. 24 01:38:51 ColdFire-Arch NetworkManager[487]: dhcpcd[27213]: wlp4s0: removing interface
sept. 24 01:38:52 ColdFire-Arch NetworkManager[487]: <warn> (wlp4s0): DHCP client pid 27213 didn't exit, will kill it.
sept. 24 01:38:52 ColdFire-Arch NetworkManager[487]: <info> (wlp4s0): canceled DHCP transaction, DHCP client pid 27213
sept. 24 01:38:52 ColdFire-Arch avahi-daemon[489]: Withdrawing address record for fe80::caf7:33ff:feef:8ef9 on wlp4s0.
sept. 24 01:38:52 ColdFire-Arch avahi-daemon[489]: Withdrawing address record for 192.168.0.6 on wlp4s0.
sept. 24 01:38:52 ColdFire-Arch avahi-daemon[489]: Leaving mDNS multicast group on interface wlp4s0.IPv4 with address 192.168.0.6.
sept. 24 01:38:52 ColdFire-Arch avahi-daemon[489]: Interface wlp4s0.IPv4 no longer relevant for mDNS.
sept. 24 01:38:52 ColdFire-Arch NetworkManager[487]: <info> Writing DNS information to /usr/bin/resolvconf
sept. 24 01:38:52 ColdFire-Arch kernel: wlp4s0: deauthenticating from a0:21:b7:ce:5a:d6 by local choice (Reason: 3=DEAUTH_LEAVING)
sept. 24 01:38:52 ColdFire-Arch NetworkManager[487]: <info> NetworkManager state is now ASLEEP
sept. 24 01:38:52 ColdFire-Arch kernel: cfg80211: Calling CRDA to update world regulatory domain
sept. 24 01:38:52 ColdFire-Arch kernel: IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
sept. 24 01:38:52 ColdFire-Arch NetworkManager[487]: <info> Policy set 'tun0' (tun0) as default for IPv4 routing and DNS.
sept. 24 01:38:52 ColdFire-Arch NetworkManager[487]: <info> Writing DNS information to /usr/bin/resolvconf
sept. 24 01:38:52 ColdFire-Arch dbus[499]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
sept. 24 01:38:52 ColdFire-Arch NetworkManager[487]: nm-openvpn-Message: Terminated openvpn daemon with PID 28949.
sept. 24 01:38:52 ColdFire-Arch systemd[1]: Starting Network Manager Script Dispatcher Service...
sept. 24 01:38:52 ColdFire-Arch systemd-timesyncd[480]: No network connectivity, watching for changes.
sept. 24 01:38:52 ColdFire-Arch NetworkManager[487]: <info> (tun0): link disconnected (deferring action for 4 seconds)
sept. 24 01:38:52 ColdFire-Arch systemd-networkd[504]: tun0 : removing non-existent address: 10.197.1.6/32 (valid for ever)
sept. 24 01:38:52 ColdFire-Arch avahi-daemon[489]: Withdrawing workstation service for tun0.
sept. 24 01:38:52 ColdFire-Arch NetworkManager[487]: <warn> (pid 27213) unhandled DHCP event for interface wlp4s0
sept. 24 01:38:52 ColdFire-Arch NetworkManager[487]: <info> (tun0): device state change: activated -> unmanaged (reason 'removed') [100 10 36]
sept. 24 01:38:52 ColdFire-Arch NetworkManager[487]: <info> (tun0): deactivating device (reason 'removed') [36]
sept. 24 01:38:52 ColdFire-Arch dbus[499]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
sept. 24 01:38:52 ColdFire-Arch systemd[1]: Starting Sleep.
sept. 24 01:38:52 ColdFire-Arch systemd[1]: Reached target Sleep.
sept. 24 01:38:52 ColdFire-Arch systemd[1]: Starting Hibernate...
sept. 24 01:38:52 ColdFire-Arch systemd[1]: Started Network Manager Script Dispatcher Service.
sept. 24 01:38:52 ColdFire-Arch systemd-sleep[30809]: Suspending system...
sept. 24 01:38:52 ColdFire-Arch kernel: PM: Hibernation mode set to 'platform'
sept. 24 01:38:52 ColdFire-Arch NetworkManager[487]: <info> Removing DNS information from /usr/bin/resolvconf
sept. 24 01:38:52 ColdFire-Arch kernel: bbswitch: enabling discrete graphics
sept. 24 01:38:52 ColdFire-Arch nm-openvpn[28949]: SIGTERM[hard,] received, process exiting
-- Reboot --Between the last message and the reboot mark, there is the part where I start my laptop and it fails to recover, but it leaves no message whatsoever in the logs.
For the record, at the end of Xorg.0.log.old, I have this (but I don't think it's really related):
[ 9582.530] (EE) intel(0): [DRI2] DRI2SwapComplete: bad drawable
[ 19078.353] (EE) intel(0): [DRI2] DRI2SwapComplete: bad drawable
[ 23238.900] (II) intel(0): EDID vendor "LGD", prod id 601
[ 23238.902] (II) intel(0): Printing DDC gathered Modelines:
[ 23238.902] (II) intel(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 -hsync -vsync (66.6 kHz eP)
[ 48904.855] (EE) intel(0): [DRI2] DRI2SwapComplete: bad drawableSomething that's worth considering, is that I had this problem with Xorg, which is now solved with xf86-video-intel-2.99.916. However, before it was solved, I had switched to SNA instead of UXA, and I think I had no hibernation problem. I'm back to UXA so I may try to revert again to SNA, but first I would like to know where the problem comes from...
Config
Graphics: Intel + NVidia (nvidia driver), with Bumblebee
linux 3.16.3
Xorg 1.16.0-6
xf86-video-intel-2.99.916
Thanks!
Last edited by Corax (2014-09-24 16:17:44)
Offline
Update: I tried switching to SNA, but I still got the problem (I also updated all my packages on Sunday). Anyone has any idea on the matter?
Offline
Try with linux-lts.
Offline
Try with linux-lts.
Well if this an unique bug that only op has, it should be reported/fixed upstream otherwise there is no guaranty that it will be fixed in the next lts release.
Offline
I think you're right ugjka, so I should report it on Linux bugzilla? The thing is I have almost nothing to report in terms of logs...
Offline
Well, see if it occurs on linux-lts, at least it might tell you if it's really the kernel.
I had something like that, my netbook was randomly rebooting instead of thawing, I think it was mostly on linux-ck.
The problem indeed is that you can't really get any logs. You can only see if it occurs on different kernels (or try to find some other variable that triggers it). At least it would give the kernel guys something to work with.
Offline
Just an update to say that after having another 3.16-related issue (kernel panic with VirtualBox and a VM on an NTFS partition), I decided to move to linux-lts. The bug has not occurred since, so it is very likely that it is indeed a bug in Linux 3.16 (or even 3.15).
I just looked at the the changelog of 3.16.4, and this commit may very well apply to my case: https://git.kernel.org/cgit/linux/kerne … 95cfe005c0. But I think I'll stay on LTS until the NTFS issues are resolved...
Offline
Pages: 1