linux-kernel - Re: [PATCH 0/3] ACPI / PM: Make ACPI-based PCI wakeup work for the "freeze" sleep state

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 22 Jul 2014 14:23:03 +0200
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux PM list <linux-pm@...r.kernel.org>,
	Linux PCI <linux-pci@...r.kernel.org>,
	Zhang Rui <rui.zhang@...el.com>
Subject: Re: [PATCH 0/3] ACPI / PM: Make ACPI-based PCI wakeup work for the "freeze" sleep state

On Tuesday, July 22, 2014 10:55:38 AM Peter Zijlstra wrote:
> On Tue, Jul 22, 2014 at 03:23:29AM +0200, Rafael J. Wysocki wrote:
> 
> > That turned out to be more challenging than I had thought initially.
> > 
> > The last version I sent was almost OK, but it had some issues (like it could
> > walk the PCI hierarchy before resuming any PCI devices during system resume),
> > so a new version follows.  I did my best to avoid introducing any new problems
> > with it, but I obviously might overlook something.
> > 
> > It works for me and doesn't seem to break anything as far as I can say.
> > 
> > [1/3] Make PM workqueue available for CONFIG_PM_RUNTIME unset.
> > [2/3] Rework the handling of ACPI device wakeup notifications.
> > [3/3] Enable wakeup GPEs while setting up devices for wakeup during system
> >       suspend too.
> 
> Doesn't break, doesn't 'work' either.

This probably means that WoL on that machine is not ACPI-based.

> Is there anything I can provide you with to make this easier? lspci output
> or anything like that?

Yes, /proc/interrupts from the machine in question would help to start with.

Also /sys/kernel/debug/wakeup_sources (if /sys/kernel/debug/ is where your debugfs
lives) before and after a "freeze" with an attempt to use WoL to wake it up.

Rafael

--
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/