All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gianluca Anzolin <gianluca@sottospazio.it>
To: linux-acpi@vger.kernel.org
Subject: Re: Debugging spurious wakeup
Date: Thu, 14 May 2015 14:51:48 +0200	[thread overview]
Message-ID: <20150514125148.GA9039@sottospazio.it> (raw)
In-Reply-To: <20150513065825.GA10680@sottospazio.it>

On Wed, May 13, 2015 at 08:58:25AM +0200, Gianluca Anzolin wrote:
> 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
> 

Hello,

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


  parent reply	other threads:[~2015-05-14 12:51 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 [this message]
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=20150514125148.GA9039@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.