On Wed, May 13, 2015 at 08:30:41AM +0000, Zhang, Rui wrote:
> 04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
> Kernel driver in use: e1000e
> Kernel modules: e1000e
> PXSX S4 *enabled pci:0000:04:00.0
>
> Please run "echo PXSX > /proc/acpi/wakeup" before shutdown and then checks if
> the problem still exists.
Thank you for directions. Here follows what I did:
root@zanac:~$ echo PXSX > /proc/acpi/wakeup
root@zanac:~$ cat /proc/acpi/wakeup | grep PX
PXSX S4 *disabled
PXSX S4 *disabled
PXSX S4 *disabled
PXSX S4 *disabled
PXSX S4 *disabled
PXSX S4 *enabled pci:0000:04:00.0
PXSX S4 *enabled pci:0000:06:00.0
root@zanac:$ poweroff
Then after 2-3 seconds the system turns on.
The echo command didn't work: infact I double checked, it didn't change the
wakeup status.
But if I disabled the wakeup would WOL packets still work?
I ask because if I disable 'Wake-up by PCIe' in the BIOS the system stays off,
but I need the WOL functionality.
Currently ethtool eth0 says:
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
This should only allow magic-packets to wake up the system. To be sure I even
disconnected the cable from the NIC. Unfortunately it still turns on by itself.
Thanks,
Gianluca
>
> Thanks,
> Rui
>
> > -----Original Message-----
> > From: Gianluca Anzolin [mailto:gianluca@xxxxxxxxxxxxxx]
> > Sent: Wednesday, May 13, 2015 4:26 PM
> > To: Zhang, Rui
> > Cc: linux-acpi@xxxxxxxxxxxxxxx
> > Subject: Re: Debugging spurious wakeup
> > Importance: High
> >
> > On Wed, May 13, 2015 at 08:13:46AM +0000, Zhang, Rui wrote:
> > > Hmm, none of them seems to be NIC related, can you please attach the
> > output of lspci -vvxx as well?
> > >
> >
> > file attached (with I blanked the mac address)
> >
> > Gianluca
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
