Martin, I did check that and I think I can preliminary give results that are quite interesting:
- If I run the ethtool command before 'systemctl suspend', the bug hasn't appeared so far - and it does not seem to matter if I run ethtool with the 'wol g' (enable WOL) or with the 'wol d' flag! - After I suspended my PC succesfull by running e.g. 'ethtool -s eth0 wol g ; systemctl suspend', the bug seems to stay away untill the next reboot even I simply use 'systemctl suspend' without ethtool on the next attempts to suspend. Thus it seems that for proper suspend on my system it only matters that ethtool is "poking" the network card one-time after system startup, regardless if I use it to enable or disable WOL. I'll do further testing if it is indeed sufficient to put the ethtool command e.g. in /etc/rc.local to make the bug disappear without any additional steps. (Allthough it has no influence on the bug there is one relevant difference between running ethtool to disable or enable WOL before systemctl: If I disable WOL, my network is offline after resume, and I have do run 'ifdown eth0; ifup eth0' to make it work again. If I enable WOL instead, my network is up after suspend at least most of the time.) -- 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
