From: Pavel Machek <pavel@ucw.cz>
To: Bill Davidsen <davidsen@tmr.com>
Cc: David Greaves <david@dgreaves.com>,
Linux Kernel M/L <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.21.1] resume doesn't run suspended kernel?
Date: Sun, 27 May 2007 21:20:03 +0000 [thread overview]
Message-ID: <20070527212002.GI3989@ucw.cz> (raw)
In-Reply-To: <4659834E.4070506@tmr.com>
Hi!
> >It is very dangerous to attempt a resume with a
> >different kernel than the one
> >that has gone to sleep.
> >Different kernels may be compiled with different
> >options that affect where or
> >how in-memory structures are saved.
> >
> If the mainline resume is depending on that no wonder
> resume is so fragile. User action can change order of
> module loads, kmalloc calls move allocated structures,
> etc. Counting on anything to be locked in place seems
> naive.
Look at code before spreading FUD. (suspend and suspend2 are same in
this matter).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-05-27 21:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 22:42 Bill Davidsen
2007-05-27 8:41 ` David Greaves
2007-05-27 13:10 ` Bill Davidsen
2007-05-27 15:26 ` David Greaves
2007-05-27 21:20 ` Pavel Machek [this message]
2007-05-27 21:17 ` Pavel Machek
2007-05-27 21:14 ` Pavel Machek
2007-05-28 3:15 ` Bill Davidsen
2007-05-28 13:21 ` Bill Davidsen
2007-05-28 13:26 ` Pavel Machek
2007-05-28 17:57 ` Rafael J. Wysocki
2007-05-28 22:48 ` Nigel Cunningham
2007-05-29 11:29 ` Pavel Machek
2007-05-29 12:03 ` Rafael J. Wysocki
2007-05-29 12:23 ` Nigel Cunningham
2007-05-29 12:40 ` Pavel Machek
2007-05-29 13:13 ` Nigel Cunningham
2007-05-29 21:51 ` Rafael J. Wysocki
2007-06-04 11:02 ` Pavel Machek
2007-06-04 11:05 ` Nigel Cunningham
2007-06-05 7:23 ` Stefan Seyfried
2007-06-05 14:08 ` Bill Davidsen
[not found] <fa.rXcMBo+RSE/6L84EBqFCeyFql/k@ifi.uio.no>
2007-05-27 2:44 ` Robert Hancock
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=20070527212002.GI3989@ucw.cz \
--to=pavel@ucw.cz \
--cc=david@dgreaves.com \
--cc=davidsen@tmr.com \
--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
all inboxes | Powered by JetHome®