Re: suspend to RAM failure on t61p

[Andrew Morton <akpm@linux-foundation.org>]

On Mon, 10 Dec 2007 22:21:56 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:

> However reverting 9cd9a0058dd35268b24fa16795a92c800f4086d4 does not fix the
> machine-reboots-after-resume-from-disk regression.
> 
> It gets to here:
> 
> Attempting manual resume
> swsusp: Marking nosave pages: 000000000009d000 - 0000000000100000
> swsusp: Basic memory bitmaps created
> Freezing user space processes ... (elapsed 0.00 seconds) done.
> Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
> Loading image data pages (52207 pages) ... done
> Read 208828 kbytes in 5.40 seconds (38.67 MB/s)
> Suspending console(s)
> 
> then everything stops for five seconds then wham.
> 
> This bug is present in 2.6.24-rc1 but I'm basically unable to bisect it
> because every bisection point (tried about four so far) hits fatal runtime
> errors: cant-find-/dev/root, an oops in ipv6, an oops in netfilter, etc.
> 
> This is just a basic boot-it-on-fc8 test with RH's config and nothing
> works.  The quality of code which people have been checking into the tree
> is just appalling and here we see the costs of that.
> 
> I think I'll see if it's present in the last 2.6.23 -mm lineup: I know I
> can bisect that.  Probably it won't be, given the way in which people like
> to jam vast amounts of new code into the merge window.
> 

Under 2.6.23-mm1 on the t61p,

	echo disk >/sys/power/state

makes the screen go black then nothing at all happens for ten seconds and
then the display comes back and it says:

t61p:/home/akpm# echo disk >/sys/power/state
echo: write error: device or resource busy

So I have to bisect that first.

This really sucks.