From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Gianluca Anzolin <gianluca@sottospazio.it>, linux-acpi@vger.kernel.org
Subject: Re: Debugging spurious wakeup
Date: Fri, 15 May 2015 09:54:53 +0200 [thread overview]
Message-ID: <5555A64D.6060200@linaro.org> (raw)
In-Reply-To: <20150513065825.GA10680@sottospazio.it>
Hi Gianluca,
do yo have the option "Remain off after power failure" in the BIOS ?
Does the issue occur if you set this option ?
On 05/13/2015 08:58 AM, Gianluca Anzolin wrote:
> Hello,
>
> I have a curious problem with my system: whenever I wake up the PC with a WOL
> magic packet and then power it off the systems comes back to life after a
> couple of seconds, by itself.
>
> I can reproduce the problem 100% of the times.
>
> I've been having this problems for years. I remember this same issue occurred
> also with my previous computer, with a different mainboard. My current system
> has an ASUS P8B-WS mb with a Xeon 1275v2 CPU.
>
> I've ruled out in the time many factors: traffic on the net (by disconnecting
> the cable), RTC alarms (by disabling them)... long story short: I'm stuck.
>
> While I'm not the only one with this issue (see[1]), some people have reported
> mixed success by blacklisting some components (xhci-pci) or by setting
> unrelated BIOS options. Unfortunately these workarounds never worked for me.
>
> So I'm here to ask if there is a way to get the source/cause of the last wakeup
> by setting some ACPI debug option. This way I could at least pinpoint the
> device/interface that caused the spontaneous wakeup and then debug further or
> at least disable it.
>
> I've tried to enable the ACPI hardware-related messages with the kernel
> arguments: acpi.debug_layer=0x2 acpi.debug_level=0xffffffff
>
> Unfortunately I can't see the information I'm looking for in the resulting
> output. Should I enable some other debug_layer? Could anybody point me in the
> right direction?
>
> Thank you and best regards,
>
> Gianluca
>
> [1] https://bbs.archlinux.org/viewtopic.php?id=173648
> --
> 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
>
--
<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
next prev parent reply other threads:[~2015-05-15 7:54 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 [this message]
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=5555A64D.6060200@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=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.