[Bug 412634] New: Wake on LAN (s2ram) via Magic Packet works only the first time after reboot
https://bugzilla.novell.com/show_bug.cgi?id=412634 Summary: Wake on LAN (s2ram) via Magic Packet works only the first time after reboot Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jms@eviolis.de QAContact: qa@suse.de CC: jms@eviolis.de Found By: Outsourced Testing After many hours of testing the problem can described as follows: After boot/reboot the command: "s2ram -f -a 3" works in a correct manner and puts the system into S3-State (suspend to ram). After doing a WakeUp via MagicWOL the system is awakening and the graphics works properly. Doing a second "s2ram -f -a 3" the system seems to go into S3-State but awakes within 3-5 seconds without any interaction from outside. After a reboot the "s2ram" command works correct, but only for one time. After that same procedure as mentioned above. Hardware: MB: ASROCK ALIVE NF7G-HDready with BIOS V. 2.10 (newest Version) CPU: AMD BE-2400, 2 Cores, 2,3 GHz RAM: 1 GB DDR2 HDD: Samsung 320 GB SATA in AHCI Mode CD: DVD-ROM with IDE-Interface NIC: Intel Pro 1000 Desktop MT (because onboard NIC doesn't work with WOL) Software: OS: OpenSUSE 11.0 x86 (32bit-Version) with all Updates until 28th July 2008 Drivers: Nvidia Graphics Driver installed via 1-Klick install x11-video-nvidiaG01-173.14.09-0.1 nvidia-gfxG01-kmp-default-173.14.09_2.6.25.5_1.1-0.1 nvidia-gfxG01-kmp-pae-173.14.09_2.6.25.5_1.1-0.1 More Informations: The used Intel Pro 1000 NIC works on a ECS AMD A780GM Motherboard correct with s2ram and WakeonLAN. So I used this NIC for testing on the ASROCK-System. On both systems the onboard NIC will not work with WakeonLan via Magic Packet. Tests wihtout the nVidia Graphics driver keeps the system Monitor black after a wakeup. But this ist mentioned on www.opensuse.org/Dokumentation. Tests with OpenSUSE 10.3 and 10.2 on the same Hardwaresystems did not work with WakeonLAN via MagicPacket. Many articles in forums found via google are talking about the fact that OpenSUSE does shutdown the NICs in case of suspend so that they can't be wakedup by the Magic Packet. Therefore I made a script witch will enable the NIC after the interface has been shutdown by its network configuration script. See here: beta:~ # cat /etc/sysconfig/network/scripts/reactivate-wol-eth0 #!/bin/bash # /sbin/ethtool -s eth0 wol g if (grep P0P1 /proc/acpi/wakeup | grep disabled 2>&1 >> /dev/null); then echo -n P0P1 > /proc/acpi/wakeup fi Output of s2ram -n: beta:~ # s2ram -n Machine unknown This machine can be identified by: sys_vendor = "To Be Filled By O.E.M." sys_product = "To Be Filled By O.E.M." sys_version = "To Be Filled By O.E.M." bios_version = "P2.10" See http://en.opensuse.org/S2ram for details. Output of lspci: beta:~ # lspci 00:00.0 RAM memory: nVidia Corporation MCP67 Memory Controller (rev a2) 00:01.0 ISA bridge: nVidia Corporation MCP67 ISA Bridge (rev a2) 00:01.1 SMBus: nVidia Corporation MCP67 SMBus (rev a2) 00:01.3 Co-processor: nVidia Corporation MCP67 Co-processor (rev a2) 00:02.0 USB Controller: nVidia Corporation MCP67 OHCI USB 1.1 Controller (rev a2) 00:02.1 USB Controller: nVidia Corporation MCP67 EHCI USB 2.0 Controller (rev a2) 00:04.0 USB Controller: nVidia Corporation MCP67 OHCI USB 1.1 Controller (rev a2) 00:04.1 USB Controller: nVidia Corporation MCP67 EHCI USB 2.0 Controller (rev a2) 00:06.0 IDE interface: nVidia Corporation MCP67 IDE Controller (rev a1) 00:07.0 Audio device: nVidia Corporation MCP67 High Definition Audio (rev a1) 00:08.0 PCI bridge: nVidia Corporation MCP67 PCI Bridge (rev a2) 00:09.0 SATA controller: nVidia Corporation MCP67 AHCI Controller (rev a2) 00:0b.0 PCI bridge: nVidia Corporation MCP67 PCI Express Bridge (rev a2) 00:0c.0 PCI bridge: nVidia Corporation MCP67 PCI Express Bridge (rev a2) 00:0d.0 PCI bridge: nVidia Corporation MCP67 PCI Express Bridge (rev a2) 00:0e.0 PCI bridge: nVidia Corporation MCP67 PCI Express Bridge (rev a2) 00:0f.0 PCI bridge: nVidia Corporation MCP67 PCI Express Bridge (rev a2) 00:10.0 PCI bridge: nVidia Corporation MCP67 PCI Express Bridge (rev a2) 00:11.0 PCI bridge: nVidia Corporation MCP67 PCI Express Bridge (rev a2) 00:12.0 VGA compatible controller: nVidia Corporation GeForce 7050 PV / nForce 630a (rev a2) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) 01:0a.0 Ethernet controller: Intel Corporation 82541GI Gigabit Ethernet Controller Ouptput of "cat /proc/acpi/wakeup" before reactivate-wol-eth0-script worked: beta:~ # cat /proc/acpi/wakeup Device S-state Status Sysfs node PS2K S4 disabled pnp:00:08 PS2M S4 disabled pnp:00:09 NSMB S4 disabled pci:0000:00:01.1 USB0 S4 disabled pci:0000:00:02.0 USB2 S4 disabled pci:0000:00:02.1 US15 S4 disabled pci:0000:00:04.0 US12 S4 disabled pci:0000:00:04.1 NMAC S5 disabled P0P1 S4 disabled pci:0000:00:08.0 HDAC S4 disabled pci:0000:00:07.0 BR10 S4 disabled pci:0000:00:0b.0 BR12 S4 disabled pci:0000:00:0d.0 BR13 S4 disabled pci:0000:00:0e.0 BR14 S4 disabled pci:0000:00:0f.0 BR15 S4 disabled pci:0000:00:10.0 BR16 S4 disabled pci:0000:00:11.0 BR11 S4 disabled pci:0000:00:0c.0 Please do net hesitate to contact me for further information. Kind regards, Josef jms@eviolis.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412634 Cyril Hrubis <chrubis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |kernel-maintainers@forge.provo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412634 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412634#c1 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bphilips@novell.com AssignedTo|kernel-maintainers@forge.provo.novell.com |kkeil@novell.com --- Comment #1 from Jeff Mahoney <jeffm@novell.com> 2008-08-08 12:20:32 MDT --- That's a good analysis. I know on my notebook, I needed to add e1000e to the blacklist for suspend. This is probably a general e1000e suspend problem and not particular to WOL. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412634 Karsten Keil <kkeil@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Priority|P5 - None |P4 - Low -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=412634 Karsten Keil <kkeil@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kkeil@novell.com |jeffm@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com