From: Gianluca Anzolin <gianluca@sottospazio.it>
To: "Zhang, Rui" <rui.zhang@intel.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: Debugging spurious wakeup
Date: Wed, 13 May 2015 11:03:40 +0200 [thread overview]
Message-ID: <20150513090340.GA11529@sottospazio.it> (raw)
In-Reply-To: <744357E9AAD1214791ACBA4B0B90926301501298@SHSMSX101.ccr.corp.intel.com>
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@sottospazio.it]
> > Sent: Wednesday, May 13, 2015 4:26 PM
> > To: Zhang, Rui
> > Cc: linux-acpi@vger.kernel.org
> > 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
next prev parent reply other threads:[~2015-05-13 9:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 6:58 Debugging spurious wakeup Gianluca Anzolin
2015-05-13 7:46 ` Zhang, Rui
2015-05-13 8:12 ` Gianluca Anzolin
2015-05-13 8:13 ` Zhang, Rui
2015-05-13 8:26 ` Gianluca Anzolin
2015-05-13 8:30 ` Zhang, Rui
2015-05-13 9:03 ` Gianluca Anzolin [this message]
2015-05-13 9:42 ` Zhang, Rui
2015-05-13 10:17 ` Gianluca Anzolin
2015-05-13 10:51 ` Gianluca Anzolin
2015-05-14 12:51 ` Gianluca Anzolin
2015-05-15 7:52 ` Gianluca Anzolin
2015-05-15 7:54 ` Daniel Lezcano
2015-05-15 8:35 ` Gianluca Anzolin
2015-05-15 8:49 ` Daniel Lezcano
2015-06-20 21:54 ` Andreas Mohr
2015-06-22 19:48 ` Gianluca Anzolin
2015-06-23 6:36 ` Gianluca Anzolin
2015-06-23 8:32 ` Daniel Lezcano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150513090340.GA11529@sottospazio.it \
--to=gianluca@sottospazio.it \
--cc=linux-acpi@vger.kernel.org \
--cc=rui.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.