Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759241AbYCTXVl (ORCPT ); Thu, 20 Mar 2008 19:21:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754655AbYCTXVd (ORCPT ); Thu, 20 Mar 2008 19:21:33 -0400 Received: from gprs189-60.eurotel.cz ([160.218.189.60]:52878 "EHLO gprs189-60.eurotel.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754116AbYCTXVc (ORCPT ); Thu, 20 Mar 2008 19:21:32 -0400 Date: Fri, 21 Mar 2008 00:22:05 +0100 From: Pavel Machek To: Alan Stern Cc: "Rafael J. Wysocki" , "Eric W. Biederman" , nigel@nigel.suspend2.net, Kexec Mailing List , linux-kernel@vger.kernel.org, Andrew Morton , linux-pm@lists.linux-foundation.org, Vivek Goyal , Len Brown Subject: Re: [linux-pm] [PATCH -mm] kexec jump -v9 Message-ID: <20080320232205.GF17431@elf.ucw.cz> References: <200803202345.25083.rjw@sisk.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Warning: Reading this can be dangerous to your mental health. User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2631 Lines: 58 On Thu 2008-03-20 19:01:56, Alan Stern wrote: > On Thu, 20 Mar 2008, Rafael J. Wysocki wrote: > > > > > >> Well, I've been saying that for I-don't-remember-how-long: on my box, if you > > > > >> use S5 instead of entering S4, the fan doesn't work correctly after the > > > > >> resume. Plain and simple. > > > > >> > > > > >> Perhaps there's a problem with our ACPI drivers that causes this to happen, > > > > >> but I have no idea what that can be at the moment. > > > > > > > > > > IMO it would be worthwhile to track this down. It's a clear indication > > > > > that something is wrong somewhere. > > > > > > > > > > Could it be connected with the way the boot kernel hands control over > > > > > to the image kernel? Presumably ACPI isn't prepared to deal with that > > > > > sort of thing during a boot from S5. It would have to be fooled into > > > > > thinking the two kernels were one and the same. > > > > > > > > It should be easy to test if it is a hand over problem, by turning off > > > > the laptop by placing it in S5 (shutdown -h now) and then booting same > > > > kernel again. > > > > > > Feel free to help with testing. > > > > > > I believe ACPI is simply getting confused by us overwriting memory > > > with that from old image. I don't see how you can emulate it with > > > shutdown. > > > > Well, in fact ACPI has something called the NVS memory, which we're supposed > > to restore during the resume and which we're not doing. The problem may be > > related to this. > > No, it can't be. ACPI won't expect the NVS memory to be restored > following an S5-shutdown. In fact, as far as ACPI is concerned, > resuming from an S5-type hibernation should not be considered a resume > at all but just an ordinary reboot. All ACPI-related memory areas > in the boot kernel should be passed directly through to the image > kernel. How can we pass interpretter state? I do not think we do this kind of passing. If it was enough to pass some static area, we could just mark it nosave... Len: Is ACPI AML permitted to allocate memory (like in ACPI_ALLOC or something)? Could we easily identify BIOS data so we could mark them nosave? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html pomozte zachranit klanovicky les: http://www.ujezdskystrom.info/ -- 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/