Hello Jan, Jan Rathmann [2015-06-15 14:06 -0000]: > - 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!
That's indeed interesting -- After a clean boot, if you just do "sudo ethtool eth0", it should show you the default WOL status; for me it is "g". So running "ethtool -s eth0 wol g" *should* be a no-op, but maybe it actually isn't. > - 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. Yes, that's expected. The driver ought to remember the WOL status across suspends. > 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. That'll be interesting indeed! It'll also show the kernel developers where to fix this. > (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.) This could also explain bug 1270257, and its more recent duplicates like bug 1431582. Thanks for your investigations! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1450396 Title: Gigabyte P35-DS3: does not stay suspended Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Bug description: Hello, using Suspend-to-RAM on my system has stopped working reliably on Vivid when booting with Systemd. When I try to suspend my PC the following happens: - PC turns off - PC unwantedly wakes up (turns on) by itself again. This time span until it turns on again can reach from a second (almost immediately) until two or three minutes. - In a few cases (<25%), the PC stays suspended properly. A way to workaround this problem is to boot my PC with Upstart instead of Systemd, then this problem never happens (and has never happened in any of the previous Ubuntu versions since 2008). Thus it seems to be a bug somehow related to Systemd. Other steps I have tried to solve the problem (without any success): - Checking BIOS settings, all options are set that way that the PC should never wake up by any event other than pressing the power button. - Checking by running "cat /proc/acpi/wakeup | grep enabled" if any device could cause wake up events. This lists my USB controller, but deactivating it (with commands like "echo USB0 > /proc/acpi/wakeup") had no success on the problem. Also suspend while running Upstart works fine despite the USB controller listed as "enabled". In the system logs I could see no hint what causes the undesired wake- ups. Allthough there is one factor which seems to have a certain influence: If I close programs like Pidgin, Skype or Firefox that cause continuous network traffic, the chance is higher that my PC will stay suspened (while runinng Systemd). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 30 11:24:46 2015 InstallationDate: Installed on 2015-04-16 (13 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150415) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
