linux-kernel - Re: Immediate wakeup after suspend

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1612326.XDA8n1le4S@vostro.rjw.lan>
Date:	Tue, 07 May 2013 01:56:08 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Parag Warudkar <parag.lkml@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
	Linux PM list <linux-pm@...r.kernel.org>
Subject: Re: Immediate wakeup after suspend

On Monday, May 06, 2013 06:22:47 PM Parag Warudkar wrote:
> Sometime after 3.9 my iMac has started to resume almost immediately
> after suspend.  Even with 3.9 it was all working as expected.

It'd be good to know something more precise, like for example which merge
introduced the problem.  I'm not aware of anything that might result is this
kind of breakage.

> Relevant dmesg output below. Any way to find out the source of the wakeup?

Not really.

You can play with the wakeup settings of various devices.

Can you send the contents of /proc/acpi/wakeup from the machine?

Rafael


> Linux parag-iMac 3.9.0+ #5 SMP PREEMPT Mon May 6 17:01:19 EDT 2013
> x86_64 x86_64 x86_64 GNU/Linux
> 
> [ 3631.441257] PM: Entering mem sleep
> [ 3631.441274] Suspending console(s) (use no_console_suspend to debug)
> [ 3631.441825] sd 0:0:0:0: [sda] Synchronizing SCSI cache
> [ 3631.442003] sd 0:0:0:0: [sda] Stopping disk
> [ 3631.755076] PM: suspend of devices complete after 313.257 msecs
> [ 3631.755219] PM: late suspend of devices complete after 0.134 msecs
> [ 3631.795185] PM: noirq suspend of devices complete after 39.904 msecs
> [ 3631.821922] pcieport 0000:00:1c.1: power state changed by ACPI to D0
> [ 3631.915378] PM: noirq resume of devices complete after 119.999 msecs
> [ 3631.915459] PM: early resume of devices complete after 0.062 msecs
> [ 3631.915525] ahci 0000:00:1f.2: setting latency timer to 64
> [ 3631.915609] ehci-pci 0000:00:1a.7: setting latency timer to 64
> [ 3631.915654] uhci_hcd 0000:00:1a.0: setting latency timer to 64
> [ 3631.915690] usb usb1: root hub lost power or was reset
> [ 3631.915709] snd_hda_intel 0000:00:1b.0: irq 46 for MSI/MSI-X
> [ 3631.915770] uhci_hcd 0000:00:1d.0: setting latency timer to 64
> [ 3631.915792] usb usb2: root hub lost power or was reset
> [ 3631.915804] ehci-pci 0000:00:1d.7: setting latency timer to 64
> [ 3631.915821] snd_hda_intel 0000:01:00.1: irq 48 for MSI/MSI-X
> [ 3631.918662] [drm] probing gen 2 caps for device 8086:101 = 2212d02/0
> [ 3631.918665] [drm] PCIE gen 2 link speeds already enabled
> [ 3631.921479] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
> [ 3631.921584] radeon 0000:01:00.0: WB enabled
-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
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/