Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764351AbXIUVNY (ORCPT ); Fri, 21 Sep 2007 17:13:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1762337AbXIUVNQ (ORCPT ); Fri, 21 Sep 2007 17:13:16 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:44585 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757631AbXIUVNP (ORCPT ); Fri, 21 Sep 2007 17:13:15 -0400 From: "Rafael J. Wysocki" To: Jeremy Maitin-Shepard Subject: Re: [linux-pm] Re: [RFC][PATCH 1/2 -mm] kexec based hibernation -v3: kexec jump Date: Fri, 21 Sep 2007 23:25:37 +0200 User-Agent: KMail/1.9.5 Cc: Alan Stern , Nigel Cunningham , nigel@suspend2.net, Kexec Mailing List , linux-kernel@vger.kernel.org, "Eric W. Biederman" , "Huang\, Ying" , linux-pm@lists.linux-foundation.org, huang ying , Andrew Morton References: <200709212253.02158.rjw@sisk.pl> <87d4wb680u.fsf@jbms.ath.cx> In-Reply-To: <87d4wb680u.fsf@jbms.ath.cx> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709212325.39599.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1442 Lines: 37 On Friday, 21 September 2007 23:08, Jeremy Maitin-Shepard wrote: > "Rafael J. Wysocki" writes: > > > On Friday, 21 September 2007 22:26, Jeremy Maitin-Shepard wrote: > >> "Rafael J. Wysocki" writes: > >> > >> [snip] > >> > >> > The ACPI NVS area is explicitly marked as reserved and we don't save it. > >> > On x86_64 we don't save any memory areas marked as reserved and yet the > > above > >> > happens. > >> > >> I think you have mentioned before, though, that ACPI is first > >> initialized by the boot kernel, before it is later initialized by > >> resuming kernel. This could well be the source of the problem. > > > No, it's not. I have tested that too with an ACPI-less boot kernel. > > Well, it seems that there just must be some other bug. I would define > anything that differs between the post-resume initialization of ACPI I'm not sure what you mean. > from the normal boot initialization of ACPI as a bug. If the interaction > with the hardware is the same, then the behavior will be the same. The ACPI platform firmware is allowed to preserve information accross the hibernation-resume cycle, so this need not be the same. Greetings, Rafael - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/