From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: "Anthony J. Breeds-Taurima"
<tony-xfCdrj5MXxYnC9Muvcwxkw@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: swsusp acpi-20021022
Date: Thu, 31 Oct 2002 22:58:53 +0100 [thread overview]
Message-ID: <20021031215852.GB4331@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0210310944170.11540-100000-optB1Q+C1bO+ZPExc8Iw5bpzq4S04n8Q@public.gmane.org>
Hi!
> Hello All,
> Firstly I'm not 100% certain if this is better here or LKML, If I'm
> wrong then I'll happily move the discussion there.
>
> I'm running kernel 2.5.44 with the acpi-20021022 aptches applied. I do how
> ever have a small problem. I have tested swsusp and the suspend went well.
> Unfortuantly I get an ooops on resume. I'm happy to look at the cause
> (provide oops and ksyms) BUT the docs say more or less "If you touch your FS
> between suspend and resume then kiss your data goodbye".
If you can't resume, forcing fsck is okay. Suspend-modify-successfull
resume would be time-to-kiss-data.
Pavel
--
When do you have heart between your knees?
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
prev parent reply other threads:[~2002-10-31 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 1:50 swsusp acpi-20021022 Anthony J. Breeds-Taurima
[not found] ` <Pine.LNX.4.44.0210310944170.11540-100000-optB1Q+C1bO+ZPExc8Iw5bpzq4S04n8Q@public.gmane.org>
2002-10-31 11:06 ` Ducrot Bruno
[not found] ` <20021031110654.GB27413-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2002-11-02 6:54 ` Anthony J. Breeds-Taurima
2002-10-31 21:58 ` 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=20021031215852.GB4331@elf.ucw.cz \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=tony-xfCdrj5MXxYnC9Muvcwxkw@public.gmane.org \
/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