All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Hamilton <martin@net.lut.ac.uk>
To: ookhoi@dds.nl
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"Grover, Andrew" <andrew.grover@intel.com>,
	"Acpi-PM (E-mail)"
	<linux-power@phobos.fachschaften.tu-muenchen.de>,
	linux-kernel@vger.kernel.org,
	acpi@phobos.fachschaften.tu-muenchen.de
Subject: Re: Linux 2.4.3-ac7
Date: Thu, 19 Apr 2001 11:35:13 +0100	[thread overview]
Message-ID: <E14qBmL-0000BM-00@gadget.lut.ac.uk> (raw)
In-Reply-To: Message from Ookhoi <ookhoi@dds.nl>  of "Thu, 19 Apr 2001 08:46:35 +0200." <20010419084635.D545@humilis>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Content-Type: text/plain; charset=us-ascii

(cc'd to the acpi list, where people have also been talking about 
this recently...)

Ookhoi writes:

| 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. 

FWIW, I didn't have any luck with the 2.4.3 swsusp-v8pre3 patch - my
C1VE suspended to disk, but on re-reading the memory image from swap
space the machine reset and we were back to the LILO prompt & fsck.

I tried turning everything off at build time that I didn't need to
actually boot the machine, and with 'CONFIG_HWSTATE_RESTORE' both on
and off - to no avail.  Will do a bit more digging to see if I can
figure out the problem, since I was enjoying running the bleeding edge
kernels on this box...

On the other hand the swsusp-v7c patch worked against 2.2.19 with only
minor tweakings, and presumably out-of-the-box against 2.2.18, which
is what it was actually indended for.  Yay!

Just so you don't get your hopes up too high, with this patch (only
tried with CONFIG_HWSTATE_RESTORE off so far) I still had to restart
networking and X after powering up again.  Compared with a full reboot
(of RedHat 7.1!) that's a small price to pay ;-)

But as Alan Cox says, expected the unexpected if you use this in
conjunction with ext3 or ReiserFS at the minute... !

Cheers,

Martin



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999 + martin

iD8DBQE63r9gVw+hz3xBJfQRAnVLAKCaKjSbR7wbRMGQIEFYMRXNDDM8tgCffGTO
MAC6PG1MyHCcaD7vsCvpdh4=
=7nBk
-----END PGP SIGNATURE-----


  reply	other threads:[~2001-04-19 10:36 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
2001-04-19 10:35     ` Martin Hamilton [this message]
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=E14qBmL-0000BM-00@gadget.lut.ac.uk \
    --to=martin@net.lut.ac.uk \
    --cc=acpi@phobos.fachschaften.tu-muenchen.de \
    --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=ookhoi@dds.nl \
    /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.