On Monday, 2 July 2007 18:36, David Greaves wrote:

Rafael J. Wysocki wrote:

quoted

On Monday, 2 July 2007 16:32, David Greaves wrote:

quoted

Rafael J. Wysocki wrote:

quoted

On Monday, 2 July 2007 12:56, Tejun Heo wrote:

quoted

David Greaves wrote:

quoted

quoted

Tejun Heo wrote:

quoted

It's really weird tho.  The PHY RDY status changed events are coming
from the device which is NOT used while resuming

There is an obvious problem there though Tejun (the errors even when sda
isn't involved in the OS boot) - can I start another thread about that
issue/bug later? I need to reshuffle partitions so I'd rather get the
hibernate working first and then go back to it if that's OK?

Yeah, sure.  The problem is that we don't know whether or how those two
are related.  It would be great if there's a way to verify memory image
read from hibernation is intact.  Rafael, any ideas?

Well, s2disk has an option to compute an MD5 checksum of the image during
the hibernation and verify it while reading the image.

(Assuming you mean the mainline version)

Sounds like a good think to try next...
Couldn't see anything on this in ../Documentation/power/*
How do I enable it?

Add 'compute checksum = y' to the s2disk's configuration file.

Ah, right - that's uswsusp isn't it? Which isn't what I'm having problems with 
AFAIK?

My suspend procedure is:

xfs_freeze -f /scratch
sync
echo platform > /sys/power/disk
echo disk > /sys/power/state
xfs_freeze -u /scratch

Which should work (actually it should work without the sync/xfs_freeze too).

So to debug the problem I'd like to minimally extend this process rather than 
replace it with another approach.

Well, this is not entirely "another approach".  Only the saving of the image is
done differently, the rest is the same.

I take it there isn't an 'echo y > /sys/power/do_image_checksum'?

No, there is not anything like that.

Greetings,
Rafael


-- 
"Premature optimization is the root of all evil." - Donald Knuth