Date: Sun, 27 May 2007 21:20:03 +0000
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?
Message-ID: <20070527212002.GI3989@ucw.cz>
References: <4658B7DD.3060309@tmr.com> <4659442E.2060307@dgreaves.com> <4659834E.4070506@tmr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4659834E.4070506@tmr.com>
User-Agent: Mutt/1.5.9i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 962
Lines: 28

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/