Hello Rafael On Tue, 8 May 2007, Rafael J. Wysocki wrote:
> On Tuesday, 8 May 2007 22:02, Tomas Pospisek's Mailing Lists wrote: >> On Tue, 1 May 2007, Rafael J. Wysocki wrote: >> >>> On Tuesday, 1 May 2007 14:13, Tomas Pospisek's Mailing Lists wrote: >>>> On Tue, 1 May 2007, Rafael J. Wysocki wrote: >>>> >>>>> On Tuesday, 1 May 2007 10:13, Tomas Pospisek's Mailing Lists wrote: >>>>>> On the machine here: >>>>>> >>>>>> $ s2ram -i >>>>>> sys_vendor = "Fujitsu Siemens" >>>>>> sys_product = "P6VAP-AP" >>>>>> sys_version = " " >>>>>> bios_version = "6.00 PG" >>>>>> >>>>>> s2ram works just fine whether run from X or from the console. >>>>>> s2disk works also, *but only as long as X is not started*. >>>>> >>>>> Can you please check if you are able to reproduce the symptoms with the >>>>> built-in swsusp, ie.: >>>>> >>>>> # echo 8 > /proc/sys/kernel/printk >>>>> # echo disk > /sys/power/state >>>> >>>> This method doesn't work at all. What I can see is that the following >>>> line is displayed: >>>> >>>> swsusp: Cannot find swapdevice, try swapon -a >>>> >>>> "swapon -a" works just fine. "swapon -s" shows me that the swap partition >>>> is in use. >>>> >>>> The effect of the suggested commands is that the command just returns >>>> back to the console with the following message: >>>> >>>> # echo 8 > /proc/sys/kernel/printk >>>> # echo disk > /sys/power/state >>>> bash: echo: write error: No such device >>>> # >>> >>> For this to work you need to append resume=<path_to_your_resume_device> to >>> the kernel's command line and reboot (<path_to_your_resume_device> is the >>> same as in the s2disk's configuration file). >> >> Thanks. >> >> It would be nice if there was an error message suggesting this. That would >> help the user. >> >> Now, I did what you suggested and the result is the same as with s2disk: >> the system goes dead. That is, it is still on in the sense that the >> computer leds, fan etc. are on, but the video card signal goes off (as my >> monitor tells me) and the PC takes no more input nor gives it any output. >> >> After a reset the filesystem is a bit corrupted, thus I get an FS check >> and things seems to work fine again. > > Really strange. > > Can you please check if doing > > # echo shutdown > /sys/power/disk > > before the 'echo disk > /sys/power/state' changes anything? Yes, it does seem to change something (however to be certain, I'd need to get half a dozen samples/tries I'd say). Now when I execute 'echo disk > /sys/power/state' the system switches to console mode (that is to VGA resolution) as it did previously, but now I see some activity. The systems tells me it's suspending tasks and I see a progress bar of sorts. But after that, same as before, the machine goes dumb. This time I pinged the machine too after it went dumb: no reply. I guess it's only electrically alive but the system is crashed on some level (possibly far) below userspace. *t -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Suspend-devel mailing list Suspend-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/suspend-devel
