All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ookhoi <ookhoi@dds.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Grover, Andrew" <andrew.grover@intel.com>,
	"'Martin Hamilton'" <martin@net.lut.ac.uk>,
	"Acpi-PM (E-mail)"
	<linux-power@phobos.fachschaften.tu-muenchen.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.3-ac7
Date: Thu, 19 Apr 2001 08:46:35 +0200	[thread overview]
Message-ID: <20010419084635.D545@humilis> (raw)
In-Reply-To: <4148FEAAD879D311AC5700A0C969E89006CDDD9B@orsmsx35.jf.intel.com> <E14pyG2-0005c5-00@the-village.bc.nu>
In-Reply-To: <E14pyG2-0005c5-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Wed, Apr 18, 2001 at 09:08:55PM +0100

> > > I was wondering whether the swsusp work might form a useful basis
> > > for the eventual ACPI implementation of the to-disk hibernation
> > > stuff:
> > 
> > I (and others) have looked at it. It's a pretty cool patch, but it
> > really isn't the right way to do things.
> 
> swsusp is most definitely the right way to do things. It works on my
> laptop which has non suspend to disk APM, it even works on my MVP3
> board where ACPI bombs totally (BIOS bug).
> 
> It might not be the right thing to do if ACPI suspend is present
> though.
> 
> Actually swsusp has one minor problem. Because of implementation bugs
> in some of the journalled file systems like ext3 using swsusp with
> those file systems can corrupt your disks (they write to disk even
> when told to mount read only rather than replaying the log to disk
> when the mount goes r/w - which is really antisocial, breaks if you
> are trying to recover from a failed disk and wants fixing.)

I tried swsusp on my vaio (also a c1ve :-) and it didn't work because it
(said it) couldn't stop [kreiserfsd]. :-(  It didn't do any harm also
afaics. 
I have zero experience with apm and acpi, but the thing I liked about
swsusp is that it works with a sysrq key combo. 

	Ookhoi

  reply	other threads:[~2001-04-19  6:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-18 18:54 Linux 2.4.3-ac7 Grover, Andrew
2001-04-18 20:08 ` Alan Cox
2001-04-19  6:46   ` Ookhoi [this message]
2001-04-19 10:35     ` Martin Hamilton
2001-04-19 10:49       ` [linux-power]Re: " Akos Maroy
2001-04-19 10:23 ` Martin Hamilton
  -- strict thread matches above, loose matches on Subject: below --
2001-04-17 17:41 Grover, Andrew
2001-04-18 17:10 ` Martin Hamilton
2001-04-16 17:52 Grover, Andrew
2001-04-16 16:12 Sergey Kubushin
2001-04-16 16:16 ` Alan Cox
2001-04-16 16:44   ` Sergey Kubushin
2001-04-16 22:37   ` Arnaldo Carvalho de Melo
2001-04-16 12:27 Alan Cox
2001-04-16 12:56 ` Chris Meadors
2001-04-16 12:57   ` Alan Cox
2001-04-17 10:35     ` Martin Hamilton
2001-04-16 17:27 ` John Cavan
2001-04-16 23:40   ` Alan Cox
2001-04-17  5:39 ` Geert Uytterhoeven
2001-04-17 12:11   ` Alan Cox

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=20010419084635.D545@humilis \
    --to=ookhoi@dds.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andrew.grover@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-power@phobos.fachschaften.tu-muenchen.de \
    --cc=martin@net.lut.ac.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.