Yes, it takes roughly 60 seconds before networking is started. Hibernation would not be an option for us, the hardware is capable of resuming, and the subsequent attempts show that it should be able to do so quickly.
Attached is a log again of login, suspend, and resume cycles. 16:02:27 the machine goes out of suspend 16:03:26 sends a DHCP request 16:04:18 machine is put back into suspend 16:04:26 machine resumes 16:04:30 sends a DHCP request There is almost a full minute between the first resume and the DHCP request being sent out. In a subsequent resume there is only 4 seconds. The latter is the behaviour that we want consistently. I do not see why this is not possible. ** Attachment added: "desktop-syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352379/+attachment/4172024/+files/desktop-syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1352379 Title: Network broken after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
