From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751706AbbCTQ24 (ORCPT ); Fri, 20 Mar 2015 12:28:56 -0400 Received: from mail-pd0-f179.google.com ([209.85.192.179]:33805 "EHLO mail-pd0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750916AbbCTQ2y (ORCPT ); Fri, 20 Mar 2015 12:28:54 -0400 Message-ID: <550C4AC8.1000405@malch.com> Date: Fri, 20 Mar 2015 09:28:56 -0700 From: Malcolm Hoar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: How to determine what hardware initiated a wake? Better tools required? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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@malch.com Gary Player. | | http://www.malch.com/ | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~