Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762482AbXIUU1E (ORCPT ); Fri, 21 Sep 2007 16:27:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756224AbXIUU0y (ORCPT ); Fri, 21 Sep 2007 16:26:54 -0400 Received: from smtp.andrew.cmu.edu ([128.2.10.83]:43727 "EHLO smtp.andrew.cmu.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761776AbXIUU0x (ORCPT ); Fri, 21 Sep 2007 16:26:53 -0400 From: Jeremy Maitin-Shepard To: "Rafael J. Wysocki" 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 Subject: Re: [linux-pm] Re: [RFC][PATCH 1/2 -mm] kexec based hibernation -v3: kexec jump References: <200709212215.26978.rjw@sisk.pl> X-Habeas-SWE-9: mark in spam to . X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-1: winter into spring Date: Fri, 21 Sep 2007 16:26:12 -0400 In-Reply-To: <200709212215.26978.rjw@sisk.pl> (Rafael J. Wysocki's message of "Fri\, 21 Sep 2007 22\:15\:25 +0200") Message-ID: <87hcln69zv.fsf@jbms.ath.cx> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.990 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 783 Lines: 22 "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. In particular, isn't it the case that you also switch the devices to low power mode before resuming? -- Jeremy Maitin-Shepard - 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/