From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262369AbTL2CUH (ORCPT ); Sun, 28 Dec 2003 21:20:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262386AbTL2CUG (ORCPT ); Sun, 28 Dec 2003 21:20:06 -0500 Received: from smtp-out1.iol.cz ([194.228.2.86]:43694 "EHLO smtp-out1.iol.cz") by vger.kernel.org with ESMTP id S262369AbTL2CUB (ORCPT ); Sun, 28 Dec 2003 21:20:01 -0500 Date: Mon, 29 Dec 2003 03:19:16 +0100 From: Pavel Machek To: Norman Diamond Cc: linux-kernel@vger.kernel.org Subject: Re: 2.6.0 swsusp Message-ID: <20031229021916.GA22903@elf.ucw.cz> References: <173c01c3cceb$07352490$43ee4ca5@DIAMONDLX60> <20031228144707.GA1489@elf.ucw.cz> <18d001c3cdb0$2c083760$43ee4ca5@DIAMONDLX60> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18d001c3cdb0$2c083760$43ee4ca5@DIAMONDLX60> User-Agent: Mutt/1.4i X-Warning: Reading this can be dangerous to your mental health. Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi! > > > 2. When I forgot to say either "resume" or "noresume", the kernel detected > > > that it could not use the swap partition, but it did not offer the > > > possibility to resume. Surely it could detect early enough that the swap > > > partition is not usable for swap but is usable for resume, and could ask the > > > user whether to do a "resume" or "noresume". > > > > At *that* point, it is no longer possible to resume safely. > > Yes and no. Junio C. Hamano explained the same thing to me, but he ALSO > explained a trick that he uses. He ALWAYS tells the kernel to do a resume. > Then the kernel detects sufficiently early if a resume is really possible or > not. Yep, same trick I use... Hmm, perhaps it should be written somewhere. But that's why "noresume" makes sense. > Hmm, I guess I still see that if we wait for the kernel to mount / and read > /etc/fstab to find where the swap partition is then it will already be too > late to try resuming from the image in the swap partition. But > theoretically it must be possible, because a certain famous monopoly > software maker can resume from an image stored in a FILE after starting its > boot sequence. With enough thrust, you can make pig fly... [Not doable in 2.6, and I do not think it is good idea]. > > > 3. When swsusp completed its writing, it decided that my ACPI BIOS could > > > not power off automatically. I wonder why. No other OS has trouble > > > powering off this machine. Also on machines with older APM BIOSes, no OS > > > had trouble powering off the machines, not even Linux with APM drivers. So > > > I could hold the power switch for 4 seconds and the BIOS beeped a warning > > > before powering off, but I wonder why it was necessary. > > > > If regular halt is also unable to power off machine, fill the bug in > > ACPI bugzilla. > > Exactly the opposite. Regular halt works. For some reason I hadn't tested > regular halt under Linux on this particular machine before first writing the > above (many reboots and suspends but not plain shutdowns). But I tested a > regular halt later and it powered down automatically. Only swsusp refuses > to power it down. Ahha, okay. On swsusp (swsusp.sf.net) list, there was some patch for something pretty much unrelated; it put regular sys_reboot() into swsusp. Any chance to try that? Pavel -- When do you have heart between your knees?