linux-kernel - How to determine what hardware initiated a wake? Better tools required?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Fri, 20 Mar 2015 09:28:56 -0700
From:	Malcolm Hoar <malch@...ch.com>
To:	linux-kernel@...r.kernel.org
Subject: How to determine what hardware initiated a wake? Better tools required?

I have been struggling to solve a problem with a system that
unexpectedly wakes up (from an S5 state).

I have searched the log files to no avail. Mr Google reveals
others will the same problem, but no meaningful solutions as
far as I can tell.

Even when I intentionally wake the system from S5 (via WOL for
example) I am unable to find that event reflected anywhere in
the logs. Booting with acpi.debug_layer=0xffffffff and
acpi.debug_level=0x2 didn't seem to help either.

It seems to me that we need a better diagnostic tool for
tracing the source of wake events; something akin to the
Windows powercfg -lastwake command.

-- 
|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| Malcolm Hoar           "The more I practice, the luckier I get". |
| malch@...ch.com                                     Gary Player. |
| http://www.malch.com/                                            |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/