[ltp] AE_TIME: T41 crashed after resuming from suspend to RAM

[Felix E. Klee]

This morning, when resuming my T41 (2373-3kg) from suspend to RAM, I saw
the following message on screen.  The machine did not respond to any key
presses and I couldn't even turn it off by pressing the power button for
more than five seconds - I had to take out the battery.

hub 3-0:1-0: over-current change on port 1
Thawing hda7.
Thawing hfa5.
ACPI-0412: *** Error: Handler for [EmbeddedControl] returned AE_TIME
ACPI-0508: *** Error: Method execution failed [\_TZ_.THMO._TMP] (Mode
c18fea0),
AE_TIME
Thawing hda6.
hub 3-0:1.0: over-current change on port 2
Password:

Beware that the above message may contain mistakes since I copied it
from paper notes that I made this morning.

Some notes:

* I don't recall ever having seen the above message before.  Suspend to
  RAM *most* of the time works fine.

* My current kernel has been in use for, maybe, a month or so.

* Yesterday or before yesterday, I installed VMware player (replacing
  VMware Workstation Demo), and in fact VMware player was running while
  the machine was in suspend.  I doubt, though, that the problem is
  related since I've sucessfully resumed the machine from suspend to RAM
  several times after the installation of VMware player, and while
  VMware player was running.

* Note the password prompt: vlock is called right after resuming from
  suspend to RAM.  So, as it looks, the machine was alive for a very
  short period of time before the crash happened.

* My suspend to RAM script currently doesn't remove the USB modules
  before suspending the machine, although that would be advisable since
  USB doesn't work after resuming (over-current change ...)

About my system:

* T41 (2373-3kg) with pretty new BIOS and Embedded Controller firmware
  (updated it one or two months ago).

* Slackware 10.2

* xorg 6.8 with ATI's latest proprietary drivers for the Radeon 9000
  (before suspending the machine switches to vt01)

* Kernel 2.6.14.4 with Swsusp 2 patches (Swsusp doesn't work)

I hope that the problem doesn't reappear since it took my quite some
time to reboot the machine, and, furthermore, e2fsck wasn't able to
clean up the file system without my help.

Any idea what may have caused the problem?
-- 
Felix E. Klee