Hello Martin, I think I have found the real cause of the bug: It seems to always happen when the wol flag is set to 'ug' (instead of 'g' or 'd'). I made a few reboots and checked the wol value with 'ethtool eth0' and it was always set to 'ug' by default after system startup (I don't know if this _really_ is always the case by default, because there were a few times in the past where suspend has worked without manually applying 'ethtool wol g'. I'll try to check that.). And I crosschecked that if I first set manually wol to 'g', do a successfull suspend, then set manually wol to 'ug' and then suspend again, the bug indeed appears.
This explains why the bug did never happen all the years when suspending with pm-suspend: The disable_wol hook always sets the flag explicitly to 'g' before suspend and thus the fact that the flag has the value 'ug' by default at system startup has no negative impact. If I add 'ethtool -s eth0 wol g' to /etc/rc.local, this is indeed a good workaround for the bug - it seems to change the state of the wol flag reliably. Martin, I really want to thank you for supporting me so far in finding the cause and also a workaround :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450396 Title: Gigabyte P35-DS3: does not stay suspended To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450396/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
