All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Gianluca Anzolin <gianluca@sottospazio.it>, Andreas Mohr <andi@lisas.de>
Cc: Zhang Rui <rui.zhang@intel.com>, linux-acpi@vger.kernel.org
Subject: Re: Debugging spurious wakeup
Date: Tue, 23 Jun 2015 10:32:16 +0200	[thread overview]
Message-ID: <55891990.2090901@linaro.org> (raw)
In-Reply-To: <20150623063612.GA27891@sottospazio.it>

On 06/23/2015 08:36 AM, Gianluca Anzolin wrote:
> Hello,
>
> Yesterday I took the time to read the document about GPE / PME handling and I
> compared the wakeup code of my BIOS with the examples in that document.
>
> I noticed that some vital wakeup code was executed only when a variable (PMSX)
> was set. That variable was set by a global NPME() method and that method was
> called by _OSC().
>
> And in my logs I had this message:
>
> giu 19 18:31:06 zanac kernel: acpi PNP0A08:00: _OSC: OS supports
> [ExtendedConfig ASPM ClockPM Segments MSI]
> giu 19 18:31:06 zanac kernel: \_SB_.PCI0:_OSC invalid UUID
> giu 19 18:31:06 zanac kernel: _OSC request data:1 1f 0
> giu 19 18:31:06 zanac kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR);
> disabling ASPM
>
> A googled a bit and found the following bugzilla entry, that applies to my
> situation perfectly: the NEXP variable isn't set anywhere, yet in Windows it
> is.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=36932
>
> So I disassembled the DSDT, I removed any test involving the NEXP variable in
> the code, I recompiled and replaced the table with GRUB.
>
> And then the _OSC() invocation completed successfully, giving me a working WOL
> without spontaneous wakeups!

Great work and thanks for sharing you results !

> What puzzles me is that the location of the NEXP variables is marked as ACPI
> NVS and the kernel never touches that region of memory. What is Windows doing
> differently that makes it work?

Perhaps it is not Windows itself but the motherboard driver fixing a 
known bug ?

   -- Daniel

-- 
  <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2015-06-23  8:32 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
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 [this message]

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=55891990.2090901@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=andi@lisas.de \
    --cc=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.