Hi!
> > That is totally broken, because I may mount the disk in between
> > the suspend and resume. I might even:
> >
> > 1. boot kernel X
> > 2. suspend kernel X
> > 3. boot kernel Y
> > 4. suspend kernel Y
> > 5. resume kernel X
> > 6. suspend kernel X
> > 7. resume kernel Y
> > 8. suspend kernel Y
> > 9. goto #5
> >
> > You really have to close the logs and mark the disks clean
> > when you suspend. The problems here are similar the the ones
> > NFS faces. Between the suspend and resume, filesystems may be
> > modified in arbitrary ways.
>
> I missed the rest of the thread, but if you are talking about what I think
> you are talking about, I'll go <AOL>Me too</AOL>
>
> A horrible combination of accidents with scripts that set lilo to boot
> to the hibernated partition if last suspended, and an apparent BIOS bug
> that allowed me to boot out of a hibernated partition for a second
> time meant that my laptop came out of regular hibernation mode (as
swsusp code will not allow you to restore from one partition twice.
Pavel
-- I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care." Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org - 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/
This archive was generated by hypermail 2b29 : Sun Sep 30 2001 - 21:01:13 EST