[Bug 841937] New: Wake on LAN does not work because the network IF is being powered off
https://bugzilla.novell.com/show_bug.cgi?id=841937 https://bugzilla.novell.com/show_bug.cgi?id=841937#c0 Summary: Wake on LAN does not work because the network IF is being powered off Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: cruff@ruffspot.net QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Firefox/23.0 I have an Asus P6T WS based system that was running OpenSuse 11.1 previously and WOL worked correctly when the proper packet was sent to either of the two Ethernet IFs. After the upgrade to 12.3, WOL no longer works, even though "wol g" definitely set in the ethtool options for both Ethernet IFs. Running "ethtool ethX" shows that wol g is set before the system is powered off via the power switch ACPI notification, or when powered off from the KDM login screen. The BIOS definitely has wake up enabled for PCIe devices. The Ethernet IFs are Realtek 8111C Gigabit devices. Examining the status LEDs of the IFs shows they appear to be powered off. Reproducible: Always Steps to Reproduce: 1. Boot system. 2. Verify WOL is enabled for the Ethernet IFs. 3. Shutdown the system. 4. Send WOL packet to the MAC with ether-wake. 5. System fails to power on. Actual Results: The system fails to power on in response to the WOL packet. Expected Results: The system should power on. -- 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=841937 https://bugzilla.novell.com/show_bug.cgi?id=841937#c Ye Yuan <yyuan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yyuan@suse.com AssignedTo|bnc-team-screening@forge.pr |mrueckert@suse.com |ovo.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=841937 https://bugzilla.novell.com/show_bug.cgi?id=841937#c1 Marcus Rückert <mrueckert@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |cruff@ruffspot.net --- Comment #1 from Marcus Rückert <mrueckert@suse.com> 2013-12-09 11:35:14 UTC --- please see bnc #846760 and make sure you dont run into the same issue -- 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=841937 https://bugzilla.novell.com/show_bug.cgi?id=841937#c2 Craig Ruff <cruff@ruffspot.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|cruff@ruffspot.net | --- Comment #2 from Craig Ruff <cruff@ruffspot.net> 2013-12-10 01:41:30 UTC --- I don't see the PCI device number for eth1 listed in the contents of /proc/acpi/wakeup, but do see the device number for eth0, which is not in use at the moment. # grep eth1 /var/log/messages 2013-12-09T16:49:55.207257-07:00 elkhound kernel: [ 11.716824] r8169 0000:06:00.0 eth1: RTL8168c/8111c at 0xffffc90012962000, e0:cb:4e:01:47:85, XID 1c4000c0 IRQ 71 2013-12-09T16:49:55.207260-07:00 elkhound kernel: [ 11.716827] r8169 0000:06:00.0 eth1: jumbo features [frames: 6128 bytes, tx checksumming: ko] 2013-12-09T16:49:56.528808-07:00 elkhound network[713]: ..skipped eth1 device: Realtek Semiconductor Co., Ltd. RTL8111/8168 2013-12-09T16:49:56.529763-07:00 elkhound ifup[1277]: eth1 device: Realtek Semiconductor Co., Ltd. RTL8111/8168 2013-12-09T16:49:56.579370-07:00 elkhound kernel: [ 30.897868] r8169 0000:06:00.0 eth1: link down 2013-12-09T16:49:56.579389-07:00 elkhound kernel: [ 30.897875] r8169 0000:06:00.0 eth1: link down 2013-12-09T16:49:56.579391-07:00 elkhound kernel: [ 30.897900] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready 2013-12-09T16:49:56.583611-07:00 elkhound ifup[1277]: eth1 2013-12-09T16:49:56.585911-07:00 elkhound network[713]: eth1 IP address: 10.0.0.4/24 2013-12-09T16:49:56.588670-07:00 elkhound avahi-daemon[696]: Joining mDNS multicast group on interface eth1.IPv4 with address 10.0.0.4. 2013-12-09T16:49:56.589135-07:00 elkhound avahi-daemon[696]: New relevant interface eth1.IPv4 for mDNS. 2013-12-09T16:49:56.589496-07:00 elkhound avahi-daemon[696]: Registering new address record for 10.0.0.4 on eth1.IPv4. 2013-12-09T16:49:59.072365-07:00 elkhound kernel: [ 33.386491] r8169 0000:06:00.0 eth1: link up 2013-12-09T16:49:59.072381-07:00 elkhound kernel: [ 33.386502] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready # ethtool eth1 Settings for eth1: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Link partner advertised pause frame use: Symmetric Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) drv probe ifdown ifup Link detected: yes # cat /proc/acpi/wakeup Device S-state Status Sysfs node NPE2 S4 *disabled NPE4 S4 *disabled NPE5 S4 *disabled NPE6 S4 *disabled NPE8 S4 *disabled NPE9 S4 *disabled NPEA S4 *disabled P0P1 S4 *disabled pci:0000:00:1e.0 PS2K S4 *enabled pnp:00:0c USB0 S4 *enabled pci:0000:00:1d.0 USB1 S4 *enabled pci:0000:00:1d.1 USB2 S4 *enabled pci:0000:00:1d.2 USB5 S4 *disabled EUSB S4 *enabled pci:0000:00:1d.7 USB3 S4 *enabled pci:0000:00:1a.0 USB4 S4 *enabled pci:0000:00:1a.1 USB6 S4 *enabled pci:0000:00:1a.2 USBE S4 *enabled pci:0000:00:1a.7 P0P4 S4 *disabled pci:0000:00:1c.0 P0P5 S4 *disabled pci:0000:00:1c.1 P0P6 S4 *disabled pci:0000:00:1c.2 P0P7 S4 *disabled P0P8 S4 *disabled P0P9 S4 *disabled NPE1 S4 *disabled pci:0000:00:01.0 NPE3 S4 *disabled pci:0000:00:03.0 NPE7 S4 *disabled pci:0000:00:07.0 GBE S4 *disabled -- 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=841937 https://bugzilla.novell.com/show_bug.cgi?id=841937#c3 Thomas Renninger <trenn@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |trenn@suse.com InfoProvider| |cruff@ruffspot.net --- Comment #3 from Thomas Renninger <trenn@suse.com> 2013-12-10 12:05:14 UTC --- It looks like the ACPI wakeup bit for the network card is not set. But from the provided data it cannot be said for sure. USB devices are enabled by default (all USBX, but not USB5, strange). We need to know on which PCI bus:slot.func the network card is, can you please provide: hwinfo --netcard One of these should be the network card: P0P1 S4 *disabled pci:0000:00:1e.0 P0P4 S4 *disabled pci:0000:00:1c.0 P0P5 S4 *disabled pci:0000:00:1c.1 P0P6 S4 *disabled pci:0000:00:1c.2 NPE1 S4 *disabled pci:0000:00:01.0 NPE3 S4 *disabled pci:0000:00:03.0 NPE7 S4 *disabled pci:0000:00:07.0 If you found out which one it is, you can already manually enable the bit, for example via: echo NPE1 >/proc/acpi/wakeup should toggle the NPE1 wakeup bit to "enabled" If this helps, this could be a kernel bug. For some time using ethtool to enable wake on lan network card capability should make the kernel also turning on the corresponding ACPI wakeup bit automatically. You can also try to manually disable and re-enable wol via ethtool ('g' is set by default already, right?). This would be: ethtool -s eth1 wol d ethtool -s eth1 wol g and then check /proc/acpi/wakeup again. Has the wakeup bit for the network card now been enabled? -- 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=841937 https://bugzilla.novell.com/show_bug.cgi?id=841937#c4 Craig Ruff <cruff@ruffspot.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|cruff@ruffspot.net | --- Comment #4 from Craig Ruff <cruff@ruffspot.net> 2013-12-10 17:47:22 UTC --- elkhound home/cruff# ip link show eth1 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000 link/ether e0:cb:4e:01:47:85 brd ff:ff:ff:ff:ff:ff elkhound home/cruff# hwinfo --netcard 36: PCI 600.0: 0200 Ethernet controller [Created at pci.319] Unique ID: JNkJ.grmZBEFhCxF Parent ID: hoOk.n1+ctqrE_b0 SysFS ID: /devices/pci0000:00/0000:00:1c.2/0000:06:00.0 SysFS BusID: 0000:06:00.0 Hardware Class: network Model: "Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller" Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd." Device: pci 0x8168 "RTL8111/8168B PCI Express Gigabit Ethernet controller" SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x8367 Revision: 0x02 Driver: "r8169" Driver Modules: "r8169" Device File: eth1 I/O Ports: 0xc800-0xc8ff (rw) Memory Range: 0xfbbff000-0xfbbfffff (rw,non-prefetchable) Memory Range: 0xf8ef0000-0xf8efffff (ro,non-prefetchable) Memory Range: 0xfbbc0000-0xfbbdffff (ro,non-prefetchable,disabled) IRQ: 71 (422 events) HW Address: e0:cb:4e:01:47:85 Link detected: yes Module Alias: "pci:v000010ECd00008168sv00001043sd00008367bc02sc00i00" Driver Info #0: Driver Status: r8169 is active Driver Activation Cmd: "modprobe r8169" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #23 (PCI bridge) 37: PCI 700.0: 0200 Ethernet controller [Created at pci.319] Unique ID: rBUF.grmZBEFhCxF Parent ID: qTvu.lC67whcqwqF SysFS ID: /devices/pci0000:00/0000:00:1c.1/0000:07:00.0 SysFS BusID: 0000:07:00.0 Hardware Class: network Model: "Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller" Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd." Device: pci 0x8168 "RTL8111/8168B PCI Express Gigabit Ethernet controller" SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x8367 Revision: 0x02 Driver: "r8169" Driver Modules: "r8169" Device File: eth0 I/O Ports: 0xd800-0xd8ff (rw) Memory Range: 0xfbcff000-0xfbcfffff (rw,non-prefetchable) Memory Range: 0xf8ff0000-0xf8ffffff (ro,non-prefetchable) Memory Range: 0xfbcc0000-0xfbcdffff (ro,non-prefetchable,disabled) IRQ: 70 (no events) HW Address: e0:cb:4e:01:49:1c Link detected: no Module Alias: "pci:v000010ECd00008168sv00001043sd00008367bc02sc00i00" Driver Info #0: Driver Status: r8169 is active Driver Activation Cmd: "modprobe r8169" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #22 (PCI bridge) elkhound home/cruff# cat /proc/acpi/wakeup Device S-state Status Sysfs node NPE2 S4 *disabled NPE4 S4 *disabled NPE5 S4 *disabled NPE6 S4 *disabled NPE8 S4 *disabled NPE9 S4 *disabled NPEA S4 *disabled P0P1 S4 *disabled pci:0000:00:1e.0 PS2K S4 *enabled pnp:00:0c USB0 S4 *enabled pci:0000:00:1d.0 USB1 S4 *enabled pci:0000:00:1d.1 USB2 S4 *enabled pci:0000:00:1d.2 USB5 S4 *disabled EUSB S4 *enabled pci:0000:00:1d.7 USB3 S4 *enabled pci:0000:00:1a.0 USB4 S4 *enabled pci:0000:00:1a.1 USB6 S4 *enabled pci:0000:00:1a.2 USBE S4 *enabled pci:0000:00:1a.7 P0P4 S4 *disabled pci:0000:00:1c.0 P0P5 S4 *disabled pci:0000:00:1c.1 P0P6 S4 *disabled pci:0000:00:1c.2 P0P7 S4 *disabled P0P8 S4 *disabled P0P9 S4 *disabled NPE1 S4 *disabled pci:0000:00:01.0 NPE3 S4 *disabled pci:0000:00:03.0 NPE7 S4 *disabled pci:0000:00:07.0 GBE S4 *disabled I don't see that the pci device for eth1 (0000:06:00.0) is listed in the sysfs node column at all. I assume that the entry for NPE7 does not actually refer to the other Ethernet I/F eth0 (0000:07:00.0), but is a PCI bridge according to lspci, as enabling NPE7 and sending a wol packet to eth0's MAC does not result in a wakeup after enabling wol for eth0. Toggling wol with ethtool does not result in an entry in /proc/acpi/wakeup for eth1. -- 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=841937 https://bugzilla.novell.com/show_bug.cgi?id=841937#c5 --- Comment #5 from Craig Ruff <cruff@ruffspot.net> 2013-12-10 17:48:53 UTC --- Here is the output of lspci for completeness: 00:00.0 Host bridge: Intel Corporation 5520/5500/X58 I/O Hub to ESI Port (rev 13) 00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 13) 00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 13) 00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 13) 00:14.0 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub System Management Registers (rev 13) 00:14.1 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 13) 00:14.2 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 13) 00:14.3 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub Throttle Registers (rev 13) 00:1a.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 00:1a.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 00:1a.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 00:1a.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller 00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1 00:1c.1 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 2 00:1c.2 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 3 00:1d.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 00:1d.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 00:1d.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 00:1d.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90) 00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller 00:1f.2 RAID bus controller: Intel Corporation 82801 SATA Controller [RAID mode] 00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller 01:00.0 PCI bridge: NEC Corporation uPD720400 PCI Express - PCI/PCI-X Bridge (rev 06) 01:00.1 PCI bridge: NEC Corporation uPD720400 PCI Express - PCI/PCI-X Bridge (rev 06) 04:00.0 VGA compatible controller: NVIDIA Corporation GeForce GT 620 (rev a1) 04:00.1 Audio device: NVIDIA Corporation GF108 High Definition Audio Controller (rev a1) 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 02) 07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 02) 08:00.0 PCI bridge: Texas Instruments XIO2000(A)/XIO2200A PCI Express-to-PCI Bridge (rev 02) 09:00.0 Serial controller: Timedia Technology Co Ltd PCI2S550 (Dual 16550 UART) (rev 01) 0a:04.0 FireWire (IEEE 1394): LSI Corporation FW322/323 [TrueFire] 1394a Controller (rev 70) ff:00.0 Host bridge: Intel Corporation Xeon 5500/Core i7 QuickPath Architecture Generic Non-Core Registers (rev 05) ff:00.1 Host bridge: Intel Corporation Xeon 5500/Core i7 QuickPath Architecture System Address Decoder (rev 05) ff:02.0 Host bridge: Intel Corporation Xeon 5500/Core i7 QPI Link 0 (rev 05) ff:02.1 Host bridge: Intel Corporation Xeon 5500/Core i7 QPI Physical 0 (rev 05) ff:02.4 Host bridge: Intel Corporation Xeon 5500/Core i7 QPI Link 1 (rev 05) ff:02.5 Host bridge: Intel Corporation Xeon 5500/Core i7 QPI Physical 1 (rev 05) ff:03.0 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller (rev 05) ff:03.1 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Target Address Decoder (rev 05) ff:03.2 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller RAS Registers (rev 05) ff:03.4 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Test Registers (rev 05) ff:04.0 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 0 Control Registers (rev 05) ff:04.1 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 0 Address Registers (rev 05) ff:04.2 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 0 Rank Registers (rev 05) ff:04.3 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 0 Thermal Control Registers (rev 05) ff:05.0 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Control Registers (rev 05) ff:05.1 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Address Registers (rev 05) ff:05.2 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Rank Registers (rev 05) ff:05.3 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Thermal Control Registers (rev 05) ff:06.0 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Control Registers (rev 05) ff:06.1 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Address Registers (rev 05) ff:06.2 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Rank Registers (rev 05) ff:06.3 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Thermal Control Registers (rev 05) -- 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=841937 https://bugzilla.novell.com/show_bug.cgi?id=841937#c6 Thomas Renninger <trenn@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |cruff@ruffspot.net --- Comment #6 from Thomas Renninger <trenn@suse.com> 2013-12-11 11:17:21 UTC --- These are the two network cards: eth0 (no link/cable connected): P0P5 S4 *disabled pci:0000:00:1c.1 eth1 (the one which is in use): P0P6 S4 *disabled pci:0000:00:1c.2 Please try to get P0P6 enabled by: echo P0P6 >/proc/acpi/wakeup and try again. An easy test could also be to use the other NIC (eth0), did you try this already? For this one P0P5 must be set enabled in /proc/acpi/wakeup. I should have asked for that already. I cannot see behind which bridge the network card(s) are. lspci -t should show that. If you can also attach dmesg that may help as well (maybe there is an unobtrusive warning or similar which might give a hint). -- 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=841937 https://bugzilla.novell.com/show_bug.cgi?id=841937#c7 --- Comment #7 from Craig Ruff <cruff@ruffspot.net> 2013-12-12 01:16:32 UTC --- Created an attachment (id=571443) --> (http://bugzilla.novell.com/attachment.cgi?id=571443) dmesg output -- 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=841937 https://bugzilla.novell.com/show_bug.cgi?id=841937#c8 Craig Ruff <cruff@ruffspot.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|cruff@ruffspot.net | --- Comment #8 from Craig Ruff <cruff@ruffspot.net> 2013-12-12 01:20:31 UTC --- I enabled both P0P{5,6}, and attached eth0 to the switch and enabled wol on eth0, but wol packets to either MAC addr still do not result in a wakeup. The dmesg output has been attached. elkhound home/cruff# lspci -t -+-[0000:ff]-+-00.0 | +-00.1 | +-02.0 | +-02.1 | +-02.4 | +-02.5 | +-03.0 | +-03.1 | +-03.2 | +-03.4 | +-04.0 | +-04.1 | +-04.2 | +-04.3 | +-05.0 | +-05.1 | +-05.2 | +-05.3 | +-06.0 | +-06.1 | +-06.2 | \-06.3 \-[0000:00]-+-00.0 +-01.0-[01-03]--+-00.0-[03]-- | \-00.1-[02]-- +-03.0-[04]--+-00.0 | \-00.1 +-07.0-[05]-- +-14.0 +-14.1 +-14.2 +-14.3 +-1a.0 +-1a.1 +-1a.2 +-1a.7 +-1b.0 +-1c.0-[08-09]----00.0-[09]----00.0 +-1c.1-[07]----00.0 +-1c.2-[06]----00.0 +-1d.0 +-1d.1 +-1d.2 +-1d.7 +-1e.0-[0a]----04.0 +-1f.0 +-1f.2 \-1f.3 elkhound home/cruff# cat /proc/acpi/wakeup Device S-state Status Sysfs node NPE2 S4 *disabled NPE4 S4 *disabled NPE5 S4 *disabled NPE6 S4 *disabled NPE8 S4 *disabled NPE9 S4 *disabled NPEA S4 *disabled P0P1 S4 *disabled pci:0000:00:1e.0 PS2K S4 *enabled pnp:00:0c USB0 S4 *enabled pci:0000:00:1d.0 USB1 S4 *enabled pci:0000:00:1d.1 USB2 S4 *enabled pci:0000:00:1d.2 USB5 S4 *disabled EUSB S4 *enabled pci:0000:00:1d.7 USB3 S4 *enabled pci:0000:00:1a.0 USB4 S4 *enabled pci:0000:00:1a.1 USB6 S4 *enabled pci:0000:00:1a.2 USBE S4 *enabled pci:0000:00:1a.7 P0P4 S4 *disabled pci:0000:00:1c.0 P0P5 S4 *enabled pci:0000:00:1c.1 P0P6 S4 *enabled pci:0000:00:1c.2 P0P7 S4 *disabled P0P8 S4 *disabled P0P9 S4 *disabled NPE1 S4 *disabled pci:0000:00:01.0 NPE3 S4 *disabled pci:0000:00:03.0 NPE7 S4 *disabled pci:0000:00:07.0 GBE S4 *disabled -- 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=841937 https://bugzilla.novell.com/show_bug.cgi?id=841937#c9 Joschi Brauchle <joschibrauchle@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joschibrauchle@gmx.de --- Comment #9 from Joschi Brauchle <joschibrauchle@gmx.de> 2014-05-05 14:55:22 UTC --- I have the same problem in openSUSE 13.1 but decided to open up a NEW bugreport to strip the hardware problems contained in here. See BNC#876346 -- 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=841937 https://bugzilla.novell.com/show_bug.cgi?id=841937#c10 --- Comment #10 from Craig Ruff <cruff@ruffspot.net> 2014-07-05 16:32:38 UTC --- I was able to get WOL working with the target system running the openSuSE 13.1 kernel 3.11.10-17-desktop by using the wol command instead of the ether-wake command on the remote system. -- 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