On Tue, 2013-12-10 at 14:04 -0800, Adam Williamson wrote: > I'm seeing something like this on my desktop lately, but I think it's > actually suspend failing messily, not a problem on resume. > > Do you see something like this around the time of the attempted > suspend? I haven't been able to find any errors relating to suspend. It shows these lines for each suspend I attempted: > [asinha@ankur-laptop ~]$ sudo journalctl --no-pager --since="2013-12-10 00:01" | egrep "suspend" > Dec 10 08:27:04 ankur-laptop kernel: Suspending console(s) (use no_console_suspend to debug) > Dec 10 08:27:04 ankur-laptop kernel: nouveau [ DRM] suspending fbcon... > Dec 10 08:27:04 ankur-laptop kernel: nouveau [ DRM] suspending display... > Dec 10 08:27:04 ankur-laptop kernel: mei_me 0000:00:16.0: suspend > Dec 10 08:27:04 ankur-laptop kernel: nouveau [ DRM] suspending client object trees... > Dec 10 08:27:04 ankur-laptop kernel: nouveau [ DRM] suspending kernel object tree... > Dec 10 08:27:04 ankur-laptop kernel: PM: suspend of devices complete after 2224.750 msecs > Dec 10 08:27:04 ankur-laptop kernel: PM: late suspend of devices complete after 0.232 msecs > Dec 10 08:27:04 ankur-laptop kernel: PM: noirq suspend of devices complete after 59.778 msecs Resume does show some errors, but it spews "System resumed" after, so I'm not sure about this again: > [asinha@ankur-laptop ~]$ sudo journalctl --no-pager --since="2013-12-10 00:01" | egrep "systemd" | egrep "suspend|resume" > Dec 10 08:27:00 ankur-laptop systemd-sleep[20600]: System resumed. > Dec 10 08:46:35 ankur-laptop systemd-udevd[159]: unknown key '\nSYMLINK' in /etc/udev/rules.d/99-resume.rules:1 > Dec 10 08:46:35 ankur-laptop systemd-udevd[159]: invalid rule '/etc/udev/rules.d/99-resume.rules:1' > Dec 10 09:14:01 ankur-laptop systemd-udevd[160]: unknown key '\nSYMLINK' in /etc/udev/rules.d/99-resume.rules:1 > Dec 10 09:14:01 ankur-laptop systemd-udevd[160]: invalid rule '/etc/udev/rules.d/99-resume.rules:1' > Dec 10 09:16:42 ankur-laptop systemd-sleep[2495]: System resumed. > Dec 10 09:19:51 ankur-laptop systemd-udevd[159]: unknown key '\nSYMLINK' in /etc/udev/rules.d/99-resume.rules:1 > Dec 10 09:19:51 ankur-laptop systemd-udevd[159]: invalid rule '/etc/udev/rules.d/99-resume.rules:1' > Dec 10 09:22:30 ankur-laptop systemd-sleep[2466]: System resumed. > Dec 10 09:23:20 ankur-laptop systemd-sleep[2855]: System resumed. > Dec 11 08:12:57 ankur-laptop systemd-sleep[21685]: System resumed. > Dec 11 08:17:56 ankur-laptop systemd-udevd[159]: unknown key '\nSYMLINK' in /etc/udev/rules.d/99-resume.rules:1 > Dec 11 08:17:56 ankur-laptop systemd-udevd[159]: invalid rule '/etc/udev/rules.d/99-resume.rules:1' > [asinha@ankur-laptop ~]$ There is no /etc/udev/rules.d/99-resume.rules file: > [asinha@ankur-laptop ~]$ ls /etc/udev/rules.d/ > 98-kexec.rules Here's something else, from dracut: > [asinha@ankur-laptop ~]$ sudo journalctl --no-pager --since="2013-12-11 08:00" | egrep "dracut" > Dec 11 08:17:56 ankur-laptop systemd[1]: Starting dracut cmdline hook... > Dec 11 08:17:56 ankur-laptop dracut-cmdline[94]: dracut-20 (Heisenbug) dracut-034-64.git20131205.fc20 > Dec 11 08:17:56 ankur-laptop dracut-cmdline[94]: warn "Cancelling resume operation. Device not found."; > Dec 11 08:17:56 ankur-laptop systemd[1]: Started dracut cmdline hook. > Dec 11 08:17:56 ankur-laptop systemd[1]: Started dracut pre-udev hook. > I haven't been able to get any more info on what device this is referring to though. At the moment, I can only think of downgrading systemd as a way to confirm it's the culprit here. -- Thanks, Warm regards, Ankur (FranciscoD) http://fedoraproject.org/wiki/User:Ankursinha Join Fedora! Come talk to us! http://fedoraproject.org/wiki/Fedora_Join_SIG
Attachment:
signature.asc
Description: This is a digitally signed message part
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
