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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
