From: Pavel Machek <pavel@suse.cz>
To: Bj?rn Mork <bmork@dod.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Resume from swsusp stopped working with 2.6.14 and 2.6.15-rc1
Date: Tue, 22 Nov 2005 19:53:23 +0100 [thread overview]
Message-ID: <20051122185323.GC1748@elf.ucw.cz> (raw)
In-Reply-To: <871x18ed96.fsf@obelix.mork.no>
Hi!
> >> Maybe that even would give me a chance to fix some hardware problem
> >> causing the timeout, and then retry the resume.
> >
> > ..while doing resume few times, trying to change hw config to make it
> > resume is _way_ more dangerous.
>
> I guess it would be. But then, what are the chances it would make the
> situation any worse? Probably never would work, but at least I would
Yes, you could make the situation worse -- if you actually
succeeded. We are talking silent corruption on filesystem here...
("swsusp gives you enough rope to blow up small town")...
> Thanks for all the good work! I've been running Linux on a number of
> laptops since 1998 and am most impressed by the swsusp evolution the
> last few years. Things weren't too bad when APM used to work and
> "lots of RAM" meant 80GB, but today I don't think I could use a laptop
> without swsusp.
Thanks. (I'd still like to see that 80GB laptop :-).
Pavel
--
Thanks, Sharp!
next prev parent reply other threads:[~2005-11-22 18:55 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-12 13:39 Resume from swsusp stopped working with 2.6.14 and 2.6.15-rc1 Bjørn Mork
2005-11-12 15:23 ` Dmitry Torokhov
2005-11-12 20:01 ` Pavel Machek
2005-11-12 20:39 ` Pavel Machek
2005-11-13 1:53 ` Dmitry Torokhov
2005-11-13 10:09 ` Bjørn Mork
2005-11-17 21:57 ` Dmitry Torokhov
2005-11-18 9:37 ` Bjørn Mork
2005-11-18 11:40 ` Pavel Machek
2005-11-18 11:49 ` Bjørn Mork
2005-11-18 18:31 ` Pavel Machek
2005-11-18 23:32 ` Dmitry Torokhov
2005-11-19 23:48 ` Pavel Machek
2005-11-22 5:26 ` Dmitry Torokhov
2005-11-22 8:57 ` Bjørn Mork
2005-11-22 17:46 ` Pavel Machek
2005-11-22 18:41 ` Bjørn Mork
2005-11-22 18:53 ` Pavel Machek [this message]
2005-11-22 18:45 ` Dmitry Torokhov
2005-11-22 18:59 ` Pavel Machek
2005-11-22 19:08 ` Dmitry Torokhov
2005-11-22 20:37 ` Dmitry Torokhov
2005-11-22 18:47 ` Pavel Machek
2005-11-22 22:15 ` Rafael J. Wysocki
2005-11-22 22:51 ` Pavel Machek
2005-11-23 10:09 ` Bjørn Mork
2005-11-23 12:01 ` Pavel Machek
2005-11-23 13:14 ` Bjørn Mork
2005-11-23 13:25 ` Pavel Machek
2005-11-23 10:53 ` Rafael J. Wysocki
2005-11-18 13:46 ` Bernd Donner
-- strict thread matches above, loose matches on Subject: below --
2005-11-13 3:08 Bernd Donner
2005-11-13 12:13 ` Jacek Kawa
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=20051122185323.GC1748@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=bmork@dod.no \
--cc=linux-kernel@vger.kernel.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