System freeze when leaving stand by on battery (Solved)

[kgha]

When I want to resume from stand by (suspend to disc) and hit a key the system freezes. I just get a blinking cursor on the fluxflux boot screen and the only way out is a cold start.

This only happens when running on battery power! With the AC adapter plugged in it works fine.

Annoying, since it's when you're on battery power you really need the stand by function (power saving)

Oh, and it's an eee900 pc...

EDIT: I wondered if CPU frequency could be the cause (lower frequency while on battery). So I used the config script and set CPU freqency to 900 MHz (static). Now I got an error message when trying to leave standby:

Code: [Auswählen]

CPU 0: Machine Check Exception: 0000000000000004
CPU 0: Bank 1: 3200000000000125
Kernel Panic - not syncing: CPU context corrupt
EDIT 2: ...and if i set CPU frequency to 675 MHz (static) and run on AC standby still works! So CPU frequency is probably not the cause. Could it have something to do with voltage? Battery gives 7.4 V, adapter gives 12 V

EDIT 3: I tried booting from my SD card (with full install) with the same result, so it shouldn't be something wrong with the install or config.

[Manfred]

Hi Kgha,

...it's an eee900 pc...

As I own no eee900, I'm sorry we have to wait until flux has finished his holidays :(

Regards, Quax

[kgha]

Sounds great  

Some food for thought for flux when he returns, I hope he comes back from holidays full of energy

After experimenting a bit my suspicions that low voltage can be the cause have been strengthened:

Suspending on AC, resuming on AC = OK
Suspending on AC, resuming on battery = Fail
Suspending on battery, resuming on battery = Fail
Suspending on battery, resuming on AC = OK

Fully loaded battery doesn't help (and I've tried two different batteries)

I have no problems starting from Power Off status on battery.

EDIT: More experimenting that hopefully can be helpful when flux tries to find an explanation : I booted from my USB Live install (the same that I have used for my full install, it's the 20090720 iso).
When I run on battery, resuming from suspend does not cause a freeze but a complete reboot.
On AC i have no problems with suspend/resume.

EDIT2: Progress! Well, kind of...

There are two 'suspend' shell scripts on my SSD: /etc/acpi/suspend (the one that fails) and another one named /etc/acpi/actions/suspend.sh

When I tried to run the latter I got the following error message in the terminal:

Code: [Auswählen]

root@ff-sl: /home/kgha # bash /etc/acpi/actions/suspend.sh
/etc/acpi/actions/suspend.sh: line 7: /etc/default/eeepc-acpi-scripts: No such file or directory
which: no  in (/usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin)
But the pc went into suspend state and I could resume when running on battery!

Maybe flux can edit this script or use it as a starting point for a new one so that it works without error messages?

[kgha]

Continued experimenting:

At the office, running on AC, noticed that after suspend/resume I cannot reconnect to the wifi. The wicd log contains the following:

Code: [Auswählen]

Attempting to authenticate...
2009/08/17 11:32:32 :: Ignoring template line: '        ca_cert="$_CA_CERT"
2009/08/17 11:32:32 :: '
2009/08/17 11:33:08 :: wpa_supplicant authentication may have failed.
2009/08/17 11:33:08 :: Running DHCP
2009/08/17 11:34:08 :: Broadcasting DHCP_DISCOVER
2009/08/17 11:34:08 ::
2009/08/17 11:34:08 :: timed out waiting for a valid DHCP server response
2009/08/17 11:34:08 ::
2009/08/17 11:34:08 :: DHCP connection failedAfter rebooting connecting runs as normal, giving the following entry in the wicd.log file:

Code: [Auswählen]

Attempting to authenticate...
2009/08/17 11:25:13 :: Ignoring template line: '        ca_cert="$_CA_CERT"
2009/08/17 11:25:13 :: '
2009/08/17 11:25:17 :: Running DHCP
2009/08/17 11:25:18 :: Broadcasting DHCP_DISCOVER
2009/08/17 11:25:18 ::
2009/08/17 11:25:18 :: dhcpIPaddrLeaseTime=86400 in DHCP server response....and so on.

However, if I first turn off the wifi card and then turn it on again I can connect.

And once again I tried the other suspend script: /etc/acpi/actions/suspend.sh and then I had no problems reconnecting after resume.

[kgha]

Update:

For a few days I've used my eee on battery at conferences, and in order to save battery I've run the /etc/acpi/actions/suspend.sh script from terminal as root and it has worked flawlessly.

So tonight I decided to try the following:

I renamed /etc/acpi/suspend to /etc/acpi/suspend.bak

I copied /etc/acpi/actions/suspend.sh to the folder /etc/acpi/ and deleted the suffix .sh

Now i can go into suspend mode via Fn+F1 or via the 'abmelden' script and resume without any trouble.

I would appreciate flux's comments on this when he can find the time - no hurry since everything seems to work! Maybe there are better solutions?

[flux]

You have more possibilities ...

Suspend-to-RAM: you can use as root

Code: [Auswählen]

/usr/bin/pmsuspend # or
/etc/acpi/actions/suspend.sh # or
/etc/acpi/suspend
Suspend-to-Disk: you can use the script /etc/acpi/suspend, if you change the line

Code: [Auswählen]

echo -n mem > /sys/power/stateto

Code: [Auswählen]

echo -n disk > /sys/power/stateand add a

Code: [Auswählen]

resume=/dev/<swappartition>to the append-line of grub's configuration.

flux.

[kgha]

Thank you, I consider the problem solved, then  and my home-made solution copying and renaming /etc/acpi/actions/suspend.sh to etc/acpi/suspend seems to work fine.

So far I haven't missed a suspend-to-disk function, but it's good to know that it can be done easily.