Hi!
> > I of course won't say that this cannot happen, but by design, the
> > swsusp
> > signature is invalidated even before reading the image, so
> > theoretically
> > it should not happen.
>
> Yes, I'd seen that happen on earlier swsusps, so I was quite suprised
> when it blew up like this.
>
Hi!
> > I of course won't say that this cannot happen, but by design, the
> > swsusp
> > signature is invalidated even before reading the image, so
> > theoretically
> > it should not happen.
>
> Yes, I'd seen that happen on earlier swsusps, so I was quite suprised
> when it blew up like this.
>
Hi!
> Yesterday I booted my laptop to 2.6.13-rc2-mm1, suspended to swsusp, and
> then resumed. It ran fine overnight, including a fair amount of IO
> (running firefox, rsyncing ~/Mail/archive from my mail server, hg pull,
> etc). This morning I did a swsusp:
>
> echo shutdown > /sys/power
On Thu, Jul 14, 2005 at 08:36:15PM +0200, Stefan Seyfried wrote:
> But the failure you have seen now - failure to invalidate the resume
> header - could also happen as long as we do not fix the reason for your
> failure. If we fix it, we don't need additional security nets ;-)
So if the header is
Andy Isaacson wrote:
> Perhaps the image should be more rigorously checked? I'm wishing that
> it would verify that the header and the image matched, after it finishes
in your case, the header and the image matched. There was no new image
on disk. And no new header.
> reading the image. For ex
On Thu, Jul 14, 2005 at 04:58:12PM +0200, Stefan Seyfried wrote:
> Andy Isaacson wrote:
> > Yesterday I booted my laptop to 2.6.13-rc2-mm1, suspended to swsusp,
> > and
[snip]
> > and got a panic along the lines of "Unable to find swap space, try
>
> a panic? it should only be an error message, but
Andy Isaacson wrote:
> Yesterday I booted my laptop to 2.6.13-rc2-mm1, suspended to swsusp, and
> then resumed. It ran fine overnight, including a fair amount of IO
> (running firefox, rsyncing ~/Mail/archive from my mail server, hg pull,
> etc). This morning I did a swsusp:
>
> echo shutd
Yesterday I booted my laptop to 2.6.13-rc2-mm1, suspended to swsusp, and
then resumed. It ran fine overnight, including a fair amount of IO
(running firefox, rsyncing ~/Mail/archive from my mail server, hg pull,
etc). This morning I did a swsusp:
echo shutdown > /sys/power/disk
e
8 matches
Mail list logo