From: Gianluca Anzolin <gianluca@sottospazio.it>
To: linux-acpi@vger.kernel.org
Subject: Re: Debugging spurious wakeup
Date: Fri, 15 May 2015 09:52:36 +0200 [thread overview]
Message-ID: <20150515075236.GA14918@sottospazio.it> (raw)
In-Reply-To: <20150514125148.GA9039@sottospazio.it>
On Thu, May 14, 2015 at 02:51:48PM +0200, Gianluca Anzolin wrote:
> I'm sorry to bother again but since the previous debug aids didn't go
> anywhere I'm here to ask again if there is a command, a debug parameter,
> something that could tell me the cause of the last system wake up.
>
> I'm aware that in Windows there is the command "powercfg -lastwake", I need
> something similar for linux, since this issue is linux specific (I can't
> reproduce it in Windows).
>
> Thank you,
>
> Gianluca
>
Hello,
since I can reproduce the issue so easily I tried to take the output of lspci
-vvvxxx when the system stays off and when it turns on by itself.
The diff between the two outputs is mainly due to changes of IRQs and
addresses but there is something else:
- RootSta: PME ReqID 0000, PMEStatus- PMEPending-
+ RootSta: PME ReqID 0400, PMEStatus- PMEPending-
for this entry:
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI
Express Root Port 6 (rev b5) (prog-if 00 [Normal decode])
Basically when PME ReqID is 0400 the system turn on. I don't really know what
that means but I noticed that the PCIe port is connected to the network
controller.
This is the output of lspci -t:
-[0000:00]-+-00.0
+-01.0-[01]--+-00.0
| \-00.1
+-06.0-[02]--
+-16.0
+-1a.0
+-1b.0
+-1c.0-[03]--
+-1c.5-[04]----00.0
+-1c.6-[05]----00.0
+-1c.7-[06]----00.0
+-1d.0
+-1e.0-[07]----03.0
+-1f.0
+-1f.2
\-1f.3
And this is the entry 04:00.0:
04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network
Connection
So it's really the ethernet driver that's misbehaving?
Thank you,
Gianluca
next prev parent reply other threads:[~2015-05-15 7:52 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
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 [this message]
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=20150515075236.GA14918@sottospazio.it \
--to=gianluca@sottospazio.it \
--cc=linux-acpi@vger.kernel.org \
/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.