From: Pavel Machek <pavel@ucw.cz>
To: Norman Diamond <ndiamond@wta.att.ne.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0 swsusp
Date: Mon, 29 Dec 2003 03:19:16 +0100 [thread overview]
Message-ID: <20031229021916.GA22903@elf.ucw.cz> (raw)
In-Reply-To: <18d001c3cdb0$2c083760$43ee4ca5@DIAMONDLX60>
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?
prev parent reply other threads:[~2003-12-29 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-28 2:33 Norman Diamond
2003-12-28 14:47 ` Pavel Machek
2003-12-29 2:04 ` Norman Diamond
2003-12-29 2:19 ` Pavel Machek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031229021916.GA22903@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=ndiamond@wta.att.ne.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome