From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755259AbXJ1UBR (ORCPT ); Sun, 28 Oct 2007 16:01:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752228AbXJ1UBE (ORCPT ); Sun, 28 Oct 2007 16:01:04 -0400 Received: from ug-out-1314.google.com ([66.249.92.169]:38049 "EHLO ug-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752180AbXJ1UBD (ORCPT ); Sun, 28 Oct 2007 16:01:03 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=FKDvQkw4KLLTB9SLwtULBqoFGxzU4oCD0o3sLkpn/U6vnP4L2Og7nc/pei4A+Eoo7QusRDL/R+kLB8gkHzuuNg8H/Yf5peERtVeg3ofprZ0ZwpRw3vGw8ZDsm4ukSTfOexDhFlNa96T5l4ZvySgW5FnTczq8EcOj6ND5FeX9p2Q= From: Maxim Levitsky To: "Rafael J. Wysocki" Subject: Re: [BUG] [linux-pm] Commit "Hibernation: Enter platform hibernation state in a consistent way)" makes my system to resume instantly from S4 Date: Sun, 28 Oct 2007 22:00:53 +0200 User-Agent: KMail/1.9.6 Cc: LKML , pm list References: <200710271405.32908.maximlevitsky@gmail.com> <200710272346.46226.rjw@sisk.pl> In-Reply-To: <200710272346.46226.rjw@sisk.pl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710282200.53910.maximlevitsky@gmail.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Saturday 27 October 2007 23:46:45 Rafael J. Wysocki wrote: > On Saturday, 27 October 2007 14:05, Maxim Levitsky wrote: > > Hi, > > > > Recently I noticed that my system resumes just after suspend to disk. > > > > I traced this to commit 9cd9a0058dd35268b24fa16795a92c800f4086d4. > > > > Note: > > > > This happens only if I enable WOL using /proc/acpi/wakeup > > (echo "ILAN" > /proc/acpi/wakeup) > > What happens after a suspend to RAM? I do more testing tomorrow, but what I remember is that, I had no issues with suspend-to-ram. (And take into account the fact that _all_ wakeup devices were enabled always, the rc.local does that for me, and still I did quite a lot of suspends, but I got the immediate resume, only and always after suspend to disk. > > > and have > > "ACPI-Hibernate-erroneously-disabled-Suspend-wakeup" applied, since otherwise > > all wake-up sources are disabled in S4. > > > > > > Clearly the above commit confuses the BIOS. > > Using latest -git with the above patch reverted makes everything work again fine. > > Well, this patch is needed to make wakeup from peripherals (eg. RTC alarm) work > on some boxes. > > The symptom that you describe is similar to what I'm observing after a suspend > to RAM on one test box. > > Can you produce a log of kernel messages printed before powering off the > system? How :-) (I will try to set up netconsole, and turn on acpi debugging, maybe this will help) > > Greetings, > Rafael > Thanks, Best regards, Maxim Levitsky