All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gianluca Anzolin <gianluca@sottospazio.it>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Debugging spurious wakeup
Date: Fri, 15 May 2015 10:35:28 +0200	[thread overview]
Message-ID: <20150515083528.GA15215@sottospazio.it> (raw)
In-Reply-To: <5555A64D.6060200@linaro.org>

On Fri, May 15, 2015 at 09:54:53AM +0200, Daniel Lezcano wrote:
> 
> Hi Gianluca,
> 
> do yo have the option "Remain off after power failure" in the BIOS ?
> 
> Does the issue occur if you set this option ?

Hi,

The BIOS option "Restore AC Power Loss" is set to "Power Off".

The other options are "Last State" and "Power On". I could change it to "Last
State", I can do it later if needed since I've no physical access to the PC
right now.

However I'm beginning to think it's the NIC driver, even though it occurs also
with no cable attached, I sent a while ago an email with my findings.

Thank you,

Gianluca

  reply	other threads:[~2015-05-15  8:35 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 [this message]
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=20150515083528.GA15215@sottospazio.it \
    --to=gianluca@sottospazio.it \
    --cc=daniel.lezcano@linaro.org \
    --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.