Re: resuming swsusp twice

[Andy Isaacson <adi@hexapodia.org>]

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 overwritten before the pages are read back in, that
implies that the overwriting IO did not get to disk in my failing case.
Since pleny of other IO did end up on disk (scribbling on my ext3 in the
process), I wonder what could be different there...

> But i have no idea what went wrong for you, i'll have a look at the code
> but i doubt that i'll find much of interest.
> 
> One thing which would be interesting:
> You don't eventually have multiple swap partitions?

One root partition, one swap partition, no swap files or anything.

The only interesting thing I can think of is that my swap partition is
only 512MB while the machine has 1.25GB RAM.  (Installed Ubuntu and took
the defaults before installing the SODIMM.)

FWIW, I have suspended and resumed a few times since the failure and
haven't seen a repeat of the problem.  I am seeing some other problems
with 2.6.13-rc2-mm1 that I didn't see before - DRM/i830 lockups after
swsusp - that might be masking the problem, but I have done the
boot-swsusp-resume-swsusp-resume successfully.

I'm at a loss as to what I might have done to trigger the problem.

-andy
-
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/