I sleep the computer, and in the first 10 or 15 minutes I can wake up by WOL without any problem, after this 10 or 15 min. I have the 2 computers in differents locations (not are in the same lan). I have configured the router for redirect the port for WOL to my computer and the computer have a static ip assigned by router. If anyone could offer some advice in words of few syllables (assume you're talking to someone who knows nothing!) that would be very kindly received.I have t his problem in two computers with Linux Mint 17.3 圆4 KDE. I have very little idea of what's really going on here, but those "System wakeup enabled by ACPI" followed by "System wakeup disabled by ACPI" messages look suspicious to me. Mar 3 15:15:02 Tower kernel: PM: early resume of devices complete after 0.149 msecs Mar 3 15:15:02 Tower kernel: PM: noirq resume of devices complete after 11.295 msecs Mar 3 15:15:02 Tower kernel: ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI Mar 3 15:15:02 Tower kernel: xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI Mar 3 15:15:02 Tower kernel: pcieport 0000:00:1c.4: System wakeup disabled by ACPI Mar 3 15:15:02 Tower kernel: ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI Mar 3 15:15:02 Tower kernel: ACPI: Waking up from system sleep state S3 Mar 3 15:15:02 Tower kernel: cache: parent cpu1 should not be sleeping Mar 3 15:15:02 Tower kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2 Mar 3 15:15:02 Tower kernel: x86: Booting SMP configuration: Mar 3 15:15:02 Tower kernel: Enabling non-boot CPUs. Mar 3 15:15:02 Tower kernel: PM: Restoring platform NVS memory Mar 3 15:15:02 Tower kernel: ACPI: Low-level resume complete
#Wakeonlan pm suspend Offline
Mar 3 15:15:02 Tower kernel: smpboot: CPU 1 is now offline Mar 3 15:15:02 Tower kernel: Disabling non-boot CPUs. Mar 3 15:15:02 Tower kernel: PM: Saving platform NVS memory Mar 3 15:15:02 Tower kernel: ACPI: Preparing to enter system sleep state S3 Mar 3 15:15:02 Tower kernel: PM: noirq suspend of devices complete after 10.732 msecs Mar 3 15:15:02 Tower kernel: xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI Mar 3 15:15:02 Tower kernel: ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI Mar 3 15:15:02 Tower kernel: ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI Mar 3 15:15:02 Tower kernel: pcieport 0000:00:1c.3: System wakeup enabled by ACPI Mar 3 15:15:02 Tower kernel: pcieport 0000:00:1c.4: System wakeup enabled by ACPI Mar 3 15:15:02 Tower kernel: PM: late suspend of devices complete after 0.247 msecs Mar 3 15:15:02 Tower kernel: PM: suspend of devices complete after 1529.904 msecs Mar 3 15:15:02 Tower kernel: sd 1:0:0:0: Synchronizing SCSI cache
![wakeonlan pm suspend wakeonlan pm suspend](http://www.pifpaf.ch/Forums/Bios2.jpg)
Mar 3 15:15:02 Tower kernel: sd 2:0:0:0: Synchronizing SCSI cache Mar 3 15:15:02 Tower kernel: parport_pc 00:05: disabled
#Wakeonlan pm suspend serial
Mar 3 15:15:02 Tower kernel: serial 00:07: System wakeup disabled by ACPI Mar 3 15:15:02 Tower kernel: serial 00:07: disabled Mar 3 15:15:02 Tower kernel: sd 6:0:0:0: Synchronizing SCSI cache Mar 3 15:15:02 Tower kernel: Suspending console(s) (use no_console_suspend to debug) Mar 3 15:15:02 Tower kernel: Freezing remaining freezable tasks.
![wakeonlan pm suspend wakeonlan pm suspend](https://globalbihari.com/wp-content/uploads/2020/04/Screenshot_20200420-1127222-1024x1024.png)
Mar 3 15:15:02 Tower kernel: Freezing user space processes. Mar 2 00:01:53 Tower kernel: PM: Syncing filesystems. Mar 2 00:01:53 Tower s3_sleep: Enter sleep state now I've set Dynamix Sleep to log what it's doing and here's what I see: The output from 'ethtool eth0' includes "Supports Wake-on: pumbg" and "Wake-on: g". Most annoying when the server is in an out-of-the way place.ĭynamix is configured to use sleep mode exclude 10:00-13:00 and 17:00-23:00 (I rather hoped this meant the server would automatically wake during these periods) wait 60 minutes after array inactivity wait for < 100kbps ethernet traffic not wait for user inactivity use WoL option 'g' before sleep. Instead I have to prod it back into life by tapping the power button. If the server goes to sleep by itself, it does not respond to the WoL packet. If I put it to sleep from the Main page, then I can reliably wake it again by sending the appropriate magic WoL packet. I have a happy UnRAID system except for one thing: wake-on-lan basically doesn't work properly.