From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: suspending to disk on FC6 not working Date: Tue, 26 Sep 2006 12:00:28 +0200 Message-ID: <200609261200.28635.rjw@sisk.pl> References: <1159138520.19021.11.camel@soncomputer> <200609252215.19257.rjw@sisk.pl> <1159225475.3014.6.camel@soncomputer> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1159225475.3014.6.camel@soncomputer> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: Louis Garcia Cc: linux-pm@lists.osdl.org List-Id: linux-pm@vger.kernel.org On Tuesday, 26 September 2006 01:04, Louis Garcia wrote: > On Mon, 2006-09-25 at 22:15 +0200, Rafael J. Wysocki wrote: > > 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 m= y box which > > > > > > > is a Dell dimension 8200 (P4). During the kernel-2.6.17-xxx u= pdates this > > > > > > > has stopped working. Now kernel-2.6.18 has come out and I'm h= aving the > > > > > > > same problems. I have tried to get this resolved on there mai= ling 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 suspen= d? > > > > > > = > > > > > > Generally you're not giving enough information to trace the pro= blem. > > > > > > = > > > > > > 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 bac= k to > > > > > the screensaver lock screen but the mouse and keyboard are dead. > > > > = > > > > Can you please try booting the kernel with init=3D/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=3D/bin/bash to the kernel command line after it had= gone > > into GRUB? > = > No, first I booted with init=3D/bin/bash. Then I did the things you said, > When the box was off I booted normally. You saying I should append > init=3D/bin/bash before and after trying to suspend. Well, it shouldn't matter if you append init=3D/bin/bash after trying to suspend, but if the shell appears without it, this means the system actually suspended and resumed. > > > linux booted into bash. > > = > > Had it been displaying a progress meter before the bash came up? > = > Never saw a meter before. > = > > > 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 s= uspend > > that change your GRUB configuration and use the "platform" suspend meth= od. > > However, the problem seems to be on much lower level and to debug it we= need > > to bypass these things. > = > Yes, something in the kernel I assume. How do I debug this further? = Please boot the kernel with "2" appended to the command line, so the system goes to the 2nd runlevel (ie. without network servers and X). Then log in as root, do "echo 8 > /proc/sys/kernel/printk" and "echo disk > /sys/power/state". The system should suspend to disk and power off the machine. If it doesn't do that (ie. if it returns to the shell immediately), please do "dmesg > dmesg.log" and send the dmesg.log file to me. Greetings, Rafael -- = You never change things by fighting the existing reality. R. Buckminster Fuller