[ltp] Re: T20 with Debian 2.6.24: Won't return from suspend

Michael Karcher linux-thinkpad@linux-thinkpad.org
Sun, 14 Sep 2008 20:40:59 +0200


--=-Fao6ux9r/bcJQlogrtmD
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Am Sonntag, den 14.09.2008, 12:53 -0500 schrieb Frank Huddleston:
> > What do you mean by "it does not return"?
> Of the six lights at the left of the power button, I think it's just
> the disk access light that flashes briefly, but nothing more. The only
> light on at that point is the battery light, over to the lower right
> of the screen.
Sounds like BOD, indeed.

> I just suspended to disk yesterday, and had a failure to return, so I
> pulled the power cord. This morning it booted again, and resumed the
> session: in other words, it restored the system successfully and did
> not boot completely from scratch.
Linux does not care on reboot after suspend-to-disk what happened to the
machine inbetween. So *if* the machine boots after suspend-to-disk via
ACPI, it will always resume. Have you tried another start directly after
the failure?

> - What's "userspace configuration", and where would I fix this?
> lsmod shows thinkpad_acpi loaded, and it produces some output at boot tim=
e:
> thinkpad_acpi: ThinkPad ACPI Extras v0.17
> thinkpad_acpi: ThinkPad BIOS IYET61WW (1.22), EC unknown
> input: /usr/sbin/thinkpad-keys as /class/input/input8
thinkpad_acpi tells the BIOS that it knows how to handle the special
keys, if the hotkeys subdriver is enabled. In that case, it does not
generate the sleep-button event on Fn-F4 anymore, but creates special
thinkpad events. Do not mind anything about hotkey mask, though.
thinkpad_acpi is not able to set or change them on a T20. Newer
thinkpad_acpi can be told to report the events either as thinkpad
specific ACPI events or via the input device (input8 in your case). Read
thinkpad-acpi documentation on that. If reporting is done via Thinkpad
ACPI events, you need a file like this in /etc/acpi/events:

event=3Dibm/hotkey.*1004
action=3Dhibernate-ram

event=3Dibm/hotkey.*100c
action=3Dhibernate

(or use s2ram and s2disk or whatever suspend solution you prefer)

> - Yes the symptoms sound like what you describe for Blink-of-Death.
> Only the battery light stays on, and goes off when I pull the power
> cord.
On my Thinkpad, the Blink-of-Death includes a reboot of the embedded
controller, that means, the battery light goes off for a short moment,
and, if the battery is low, turns green afterwards for a second and then
turns yellow again. But it might look a bit different without an
ultrabay battery (my main battery is dead).

> - I guess I could try APM.
If it is BOD, it won't help, but you can try.

> One day it stopped returning from sleep, regularly, and I began
> researching the problem. It sounded like BOD, but I decided to update
> the BIOS, why not, and that seemed to help. About all I can say now is
> that it appears that s2ram does not work: ever. In an earlier Debian
> version, it worked but if I left it asleep for some time, like
> overnight or a few days, it wouldn't come back.
Similar symptoms here. Resume chance were a bit higher, if no battery
was plugged (AC only) during s2ram, IIRC. There was some correlation
between resume chance and power source, definitely.

> On the other hand, when I thought I had the BOD problem, I had to
> leave the machine unplugged for days sometimes before it would
> restart. Now it seems that a few hours is enough.
Half an hour unplugged usually was enough on my system, too. And while
my system didn't even think about booting at all 7 months ago, now it
boots nicely. Might be the right point-in-time to sell it as "working"
on ebay (just kidding!).

> To enable APM, I just put "apm=3Don" after the kernel line
> in /boot/grub/menu.lst, right?
No, "acpi=3Doff".

Regards,
  Michael Karcher

--=-Fao6ux9r/bcJQlogrtmD
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Dies ist ein digital signierter Nachrichtenteil

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkjNWp0ACgkQzhek2R7EicrIlwCgm/cyxPByAif5jv/AbR9nQ5Qm
vsEAn1lGgjvLnl/aLtXx4wbSII77GILm
=kPcF
-----END PGP SIGNATURE-----

--=-Fao6ux9r/bcJQlogrtmD--