June 2, 201412 yr Hi guys, I recently started messing around with the S3 sleep function through the Dynamix webgui. I am running unRaid 5.05 and the current versions of the Dynamix webgui and plugins. I am using the stock setting for sleep except I am forcing DHCP renewal and GB (I set these after it didnt work the first time). I am manually sleeping the sever with the button on the array operation tab and I am using an app called WakeMe (on my Mac) using the MAC address and port 4343, the app then sends the magic packet. The server wakes immediately when the packet is sent (fans, hard drives, lights) however video, telnet, webgui, etc does NOT function. It is like it is still asleep. After that, I hold the power button down AND I must UNPLUG the computer from the wall (shut of the SMPS), otherwise it shows the same symptoms. I enabled the DEBUG mode and this is what I got in the log Sun Jun 1 22:38:58 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive stat e is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle / dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle /dev/sdg drive state is: active/idle /dev/sdh drive state is: active/idle /dev/sdi drive state is: active/idle I have read some stuff on the forums, but nothing that I find intelligible. I am fairly useless at coding customs scripts. I can only do basic telnet stuff. I am not exactly sure where to start diagnosing the problem. Any help would be appreciated. EDIT Also, this is in my syslog, not sure if it is relevant PME# supported from D0 D3hot D3cold Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:04.0: System wakeup disabled by ACPI Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:10.0: [1022:7812] type 00 class 0x0c0330 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:10.0: reg 10: [mem 0xfeb4a000-0xfeb4bfff 64bit] Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:10.0: PME# supported from D0 D3hot D3cold Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:10.0: System wakeup disabled by ACPI Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:10.1: [1022:7812] type 00 class 0x0c0330 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:10.1: reg 10: [mem 0xfeb48000-0xfeb49fff 64bit] Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:10.1: PME# supported from D0 D3hot D3cold Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:10.1: System wakeup disabled by ACPI Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:11.0: [1022:7800] type 00 class 0x01018f Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:11.0: reg 10: [io 0xf190-0xf197] Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:11.0: reg 14: [io 0xf180-0xf183] Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:11.0: reg 18: [io 0xf170-0xf177] Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:11.0: reg 1c: [io 0xf160-0xf163] Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:11.0: reg 20: [io 0xf150-0xf15f] Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:11.0: reg 24: [mem 0xfeb51000-0xfeb517ff] Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:11.0: set SATA to AHCI mode Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:12.0: [1022:7807] type 00 class 0x0c0310 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:12.0: reg 10: [mem 0xfeb50000-0xfeb50fff] Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:12.0: System wakeup disabled by ACPI Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:12.2: [1022:7808] type 00 class 0x0c0320 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:12.2: reg 10: [mem 0xfeb4f000-0xfeb4f0ff] Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:12.2: supports D1 D2 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:12.2: System wakeup disabled by ACPI Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:13.0: [1022:7807] type 00 class 0x0c0310 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:13.0: reg 10: [mem 0xfeb4e000-0xfeb4efff] Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:13.0: System wakeup disabled by ACPI Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:13.2: [1022:7808] type 00 class 0x0c0320 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:13.2: reg 10: [mem 0xfeb4d000-0xfeb4d0ff] Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:13.2: supports D1 D2 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:13.2: System wakeup disabled by ACPI Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:14.0: [1022:780b] type 00 class 0x0c0500 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:14.1: [1022:780c] type 00 class 0x01018a Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:14.1: reg 10: [io 0xf140-0xf147] Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:14.1: reg 14: [io 0xf130-0xf133] Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:14.1: reg 18: [io 0xf120-0xf127] Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:14.1: reg 1c: [io 0xf110-0xf113] Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:14.1: reg 20: [io 0xf100-0xf10f] Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:14.2: [1022:780d] type 00 class 0x040300 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:14.2: reg 10: [mem 0xfeb40000-0xfeb43fff 64bit] Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:14.2: PME# supported from D0 D3hot D3cold Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:14.2: System wakeup disabled by ACPI Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:14.3: [1022:780e] type 00 class 0x060100 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:14.4: [1022:780f] type 01 class 0x060401 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:14.4: System wakeup disabled by ACPI Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:14.5: [1022:7809] type 00 class 0x0c0310 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:14.5: reg 10: [mem 0xfeb4c000-0xfeb4cfff] Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:14.5: System wakeup disabled by ACPI Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:15.0: [1022:43a0] type 01 class 0x060400 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:15.0: supports D1 D2 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:15.0: System wakeup disabled by ACPI Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:15.1: [1022:43a1] type 01 class 0x060400 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:15.1: supports D1 D2 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:15.1: System wakeup disabled by ACPI Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:15.2: [1022:43a2] type 01 class 0x060400 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:15.2: supports D1 D2 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:15.2: System wakeup disabled by ACPI Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:15.3: [1022:43a3] type 01 class 0x060400 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:15.3: supports D1 D2 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:15.3: System wakeup disabled by ACPI Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:18.0: [1022:1700] type 00 class 0x060000 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:18.1: [1022:1701] type 00 class 0x060000 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:18.2: [1022:1702] type 00 class 0x060000 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:18.3: [1022:1703] type 00 class 0x060000 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:18.4: [1022:1704] type 00 class 0x060000 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:18.5: [1022:1718] type 00 class 0x060000 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:18.6: [1022:1716] type 00 class 0x060000 Jun 1 22:42:56 MasterStructure kernel: pci 0000:00:18.7: [1022:1719] type 00 class 0x060000 Jun 1 22:42:56 MasterStructure kernel: pci 0000:01:00.0: [1000:0072] type 00 class 0x01070
June 2, 201412 yr What NIC driver is used on your server! Maybe Realtek ?? Sent from my iPhone using Tapatalk 2
June 2, 201412 yr Author Yep how did you guess? haha Realtek® 8111E , 1 x Gigabit LAN Controller(s) - It's integrated on my MOBO also, the result of ifconfig Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes
June 3, 201412 yr If the module is r8169 for your NIC you will not get wake working, however I have compiled the bzroot with Realtek r8168 linux driver and all working 100%. But, when booting with Xen,you break wake even with r8168, but I run instead KVM for visualization, and WOL works great, ask Tom to change to r8168, he have done that in the past, but last time I ask, he will not do it :-( Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) drv probe ifdown ifup Link detected: yes NIC driver info (from ethtool -i) driver: r8168 version: 8.038.00-NAPI firmware-version: bus-info: 0000:03:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no //Peter
June 9, 201412 yr Author I believe v5 is compiled with the r8168 driver per the release notes. I am running 5.0.5, so I should have the r8168 module correct? However, WOL is still not working?
June 9, 201412 yr Do you have a cheap, non-RTL-based NIC you can use in the server just to see whether it is the RTL drivers that are causing the problem?
June 9, 201412 yr I had the same problem, running an AMD zacate board with a Realtek NIC. Got it working now under 5.0.5 even with r8169 loaded. In my case, I believe it was because there was no driver for the GPU. Since you are using a Llano CPU which also has an embedded AMD GPU if I'm not mistaken, I assume it might be the same problem. I'm no linux expert at all obviously, but I had the same symptoms and error messages, even in the syslog. You can search my posts if you like. I tried compiling a kernel with error reporting enabled (or something like that) to find out what device was causing the issue, tried various utilities and sleep command line options, all to no avail. What I did (had to do) is compile my own kernel with driver support for the GPU. Of course this loads a whole bunch of other stuff because of dependencies but it has been running flawless so far. I haven't had the time to fine tune it unfortunately. Again, more info in my previous posts. Also, there is (was?) a problem with the Dynamix sleep plugin when you're running the free version (without cache) and rely on a disk outside the array ( i.e. mounted with SNAP). --> Fixed with latest version (2.1.1). Of course, again, no linux expert and would love to get it working without it ...
June 9, 201412 yr You can also try to add this to the syslinux.cfg, after initrd=/bzroot acpi_sleep=s3_bios //Peter
June 25, 201412 yr Author I am thinking of buying a PCI GB Adapter and just forgetting the onboard NIC. Any recommendations? Also, is it possible to bind the two channels on a dual port card (NIC Teaming)? I have a ssd cache and would like to improve write speeds.
June 25, 201412 yr Intel NICs are usually recommended. Make sure to buy a PCI-E card when going this route, PCI will get saturated with a single gigabit NIC. Did you get sleep working?
June 25, 201412 yr @the ones with working S3 sleep How is the status of the unRAID if you wake up from sleep? Any errors? (in the log) All working fine?
June 25, 201412 yr I never had any issues to resume from suspend, some log below. Jun 21 12:36:17 tower kernel: PM: Syncing filesystems ... done. Jun 21 12:38:43 tower kernel: Freezing user space processes ... (elapsed 0.001 seconds) done. Jun 21 12:38:43 tower kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jun 21 12:38:43 tower kernel: Suspending console(s) (use no_console_suspend to debug) Jun 21 12:38:43 tower kernel: sd 9:0:7:0: [sdp] Synchronizing SCSI cache Jun 21 12:38:43 tower kernel: sd 9:0:6:0: [sdo] Synchronizing SCSI cache Jun 21 12:38:43 tower kernel: sd 9:0:5:0: [sdn] Synchronizing SCSI cache Jun 21 12:38:43 tower kernel: sd 9:0:4:0: [sdm] Synchronizing SCSI cache Jun 21 12:38:43 tower kernel: sd 9:0:3:0: [sdl] Synchronizing SCSI cache Jun 21 12:38:43 tower kernel: sd 9:0:2:0: [sdk] Synchronizing SCSI cache Jun 21 12:38:43 tower kernel: sd 9:0:1:0: [sdj] Synchronizing SCSI cache Jun 21 12:38:43 tower kernel: sd 9:0:0:0: [sdi] Synchronizing SCSI cache Jun 21 12:38:43 tower kernel: sd 8:0:0:0: [sdh] Synchronizing SCSI cache Jun 21 12:38:43 tower kernel: sd 8:0:0:0: [sdh] Stopping disk Jun 21 12:38:43 tower kernel: sd 7:0:0:0: [sdg] Synchronizing SCSI cache Jun 21 12:38:43 tower kernel: sd 7:0:0:0: [sdg] Stopping disk Jun 21 12:38:43 tower kernel: sd 4:0:0:0: [sdf] Synchronizing SCSI cache Jun 21 12:38:43 tower kernel: sd 3:0:0:0: [sde] Synchronizing SCSI cache Jun 21 12:38:43 tower kernel: sd 4:0:0:0: [sdf] Stopping disk Jun 21 12:38:43 tower kernel: sd 2:0:0:0: [sdd] Synchronizing SCSI cache Jun 21 12:38:43 tower kernel: sd 3:0:0:0: [sde] Stopping disk Jun 21 12:38:43 tower kernel: sd 2:0:0:0: [sdd] Stopping disk Jun 21 12:38:43 tower kernel: sd 1:0:0:0: [sdc] Synchronizing SCSI cache Jun 21 12:38:43 tower kernel: sd 1:0:0:0: [sdc] Stopping disk Jun 21 12:38:43 tower kernel: i8042 kbd 00:0b: System wakeup enabled by ACPI Jun 21 12:38:43 tower kernel: mptbase: ioc0: pci-suspend: pdev=0xffff880418e4d000, slot=0000:01:00.0, Entering operating state [D3] Jun 21 12:38:43 tower kernel: PM: suspend of devices complete after 836.094 msecs Jun 21 12:38:43 tower kernel: PM: late suspend of devices complete after 0.634 msecs Jun 21 12:38:43 tower kernel: pcieport 0000:00:1c.5: System wakeup enabled by ACPI Jun 21 12:38:43 tower kernel: ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI Jun 21 12:38:43 tower kernel: xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI Jun 21 12:38:43 tower kernel: PM: noirq suspend of devices complete after 19.356 msecs Jun 21 12:38:43 tower kernel: ACPI: Preparing to enter system sleep state S3 Jun 21 12:38:43 tower kernel: PM: Saving platform NVS memory Jun 21 12:38:43 tower kernel: Disabling non-boot CPUs ... Jun 21 12:38:43 tower kernel: intel_pstate CPU 1 exiting Jun 21 12:38:43 tower kernel: kvm: disabling virtualization on CPU1 Jun 21 12:38:43 tower kernel: smpboot: CPU 1 is now offline Jun 21 12:38:43 tower kernel: intel_pstate CPU 2 exiting Jun 21 12:38:43 tower kernel: kvm: disabling virtualization on CPU2 Jun 21 12:38:43 tower kernel: smpboot: CPU 2 is now offline Jun 21 12:38:43 tower kernel: intel_pstate CPU 3 exiting Jun 21 12:38:43 tower kernel: kvm: disabling virtualization on CPU3 Jun 21 12:38:43 tower kernel: smpboot: CPU 3 is now offline Jun 21 12:38:43 tower kernel: intel_pstate CPU 4 exiting Jun 21 12:38:43 tower kernel: kvm: disabling virtualization on CPU4 Jun 21 12:38:43 tower kernel: smpboot: CPU 4 is now offline Jun 21 12:38:43 tower kernel: intel_pstate CPU 5 exiting Jun 21 12:38:43 tower kernel: kvm: disabling virtualization on CPU5 Jun 21 12:38:43 tower kernel: smpboot: CPU 5 is now offline Jun 21 12:38:43 tower kernel: intel_pstate CPU 6 exiting Jun 21 12:38:43 tower kernel: kvm: disabling virtualization on CPU6 Jun 21 12:38:43 tower kernel: smpboot: CPU 6 is now offline Jun 21 12:38:43 tower kernel: intel_pstate CPU 7 exiting Jun 21 12:38:43 tower kernel: kvm: disabling virtualization on CPU7 Jun 21 12:38:43 tower kernel: smpboot: CPU 7 is now offline Jun 21 12:38:43 tower kernel: ACPI: Low-level resume complete Jun 21 12:38:43 tower kernel: PM: Restoring platform NVS memory Jun 21 12:38:43 tower kernel: Enabling non-boot CPUs ... Jun 21 12:38:43 tower kernel: x86: Booting SMP configuration: Jun 21 12:38:43 tower kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2 Jun 21 12:38:43 tower kernel: kvm: enabling virtualization on CPU1 Jun 21 12:38:43 tower kernel: Intel pstate controlling: cpu 1 Jun 21 12:38:43 tower kernel: CPU1 is up Jun 21 12:38:43 tower kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4 Jun 21 12:38:43 tower kernel: kvm: enabling virtualization on CPU2 Jun 21 12:38:43 tower kernel: Intel pstate controlling: cpu 2 Jun 21 12:38:43 tower kernel: CPU2 is up Jun 21 12:38:43 tower kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6 Jun 21 12:38:43 tower kernel: kvm: enabling virtualization on CPU3 Jun 21 12:38:43 tower kernel: Intel pstate controlling: cpu 3 Jun 21 12:38:43 tower kernel: CPU3 is up Jun 21 12:38:43 tower kernel: smpboot: Booting Node 0 Processor 4 APIC 0x1 Jun 21 12:38:43 tower kernel: kvm: enabling virtualization on CPU4 Jun 21 12:38:43 tower kernel: Intel pstate controlling: cpu 4 Jun 21 12:38:43 tower kernel: CPU4 is up Jun 21 12:38:43 tower kernel: smpboot: Booting Node 0 Processor 5 APIC 0x3 Jun 21 12:38:43 tower kernel: kvm: enabling virtualization on CPU5 Jun 21 12:38:43 tower kernel: Intel pstate controlling: cpu 5 Jun 21 12:38:43 tower kernel: CPU5 is up Jun 21 12:38:43 tower kernel: smpboot: Booting Node 0 Processor 6 APIC 0x5 Jun 21 12:38:43 tower kernel: kvm: enabling virtualization on CPU6 Jun 21 12:38:43 tower kernel: Intel pstate controlling: cpu 6 Jun 21 12:38:43 tower kernel: CPU6 is up Jun 21 12:38:43 tower kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7 Jun 21 12:38:43 tower kernel: kvm: enabling virtualization on CPU7 Jun 21 12:38:43 tower kernel: Intel pstate controlling: cpu 7 Jun 21 12:38:43 tower kernel: CPU7 is up Jun 21 12:38:43 tower kernel: ACPI: Waking up from system sleep state S3
June 25, 201412 yr Interesting! How is S3 initiated? Are there any preparations done (by a script or so)? How is S3 initiated? Only with this line? echo -n mem > /sys/power/state
June 26, 201412 yr Would you mind sharing that script so I can have a closer look how it performs S3?
June 26, 201412 yr Look here http://lime-technology.com/forum/index.php?topic=3657.msg313351#msg313351 and here http://lime-technology.com/forum/index.php?topic=31113.msg307926#msg307926
June 26, 201412 yr OK, thanks. I know the first link. The second is related to dynamix s3. Does it run standalone or is dynamix required?
June 27, 201412 yr Also found this s3_sleep script: http://lime-technology.com/forum/index.php?topic=28526.msg266052#msg266052 It seems to be a standalone version cut out from the simple features plugin. There is no difference in the way how S3 sleep is called though.
Archived
This topic is now archived and is closed to further replies.