Re: suspending to disk on FC6 not working

["Rafael J. Wysocki" <rjw@sisk.pl>]

On Monday, 25 September 2006 21:34, Louis Garcia wrote:
> On Mon, 2006-09-25 at 20:43 +0200, Rafael J. Wysocki wrote:
> > On Monday, 25 September 2006 19:10, Louis Garcia wrote:
> > > On Mon, 2006-09-25 at 09:16 +0200, Rafael J. Wysocki wrote:
> > > > On Monday, 25 September 2006 00:55, Louis Garcia wrote:
> > > > > When I first installed FC6 test 2 suspend to disk worked on my box which
> > > > > is a Dell dimension 8200 (P4). During the kernel-2.6.17-xxx updates this
> > > > > has stopped working. Now kernel-2.6.18 has come out and I'm having the
> > > > > same problems. I have tried to get this resolved on there mailing list
> > > > > but it's not high on there things todo. I would like to debug suspend to
> > > > > see what is happening. What is the proper way to do this? Has this been
> > > > > discussed before? Is there a separate mailing-list for suspend?
> > > > 
> > > > Generally you're not giving enough information to trace the problem.
> > > > 
> > > > First, what doesn't work, the suspend to disk or the resume?
> > > > 
> > > > Rafael
> > > > 
> > > > 
> > > 
> > > Suspend to disk does not work. When trying to suspend, from gnome, it
> > > goes normally. The power button blinks and then restarts. I'm back to
> > > the screensaver lock screen but the mouse and keyboard are dead.
> > 
> > Can you please try booting the kernel with init=/bin/bash, mount /proc,
> > mount /sys, do "/sbin/swapon -a" and "echo disk > /sys/power/state"?
> > 
> > Rafael
> > 
> > 
> After the echo command the box turned off. The power button was not
> blinking. I restarted it and went into grub,

Did you append init=/bin/bash to the kernel command line after it had gone
into GRUB?

> linux booted into bash.

Had it been displaying a progress meter before the bash came up?

> When suspend was working the power button flashed and when I pressed it
> the box booted right into linux and the screensaver lock screen
> bypassing grub altogether.

That's because if you suspend "normally", some scripts run before the suspend
that change your GRUB configuration and use the "platform" suspend method.
However, the problem seems to be on much lower level and to debug it we need
to bypass these things.

Greetings,
Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller