--kvUQC+jR9YzypDnK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 27, 2005 at 07:28:22PM -0400, Jared D. McNeill wrote:
> On Fri, 2005-01-28 at 10:01 +1100, Daniel Carosone wrote:
> > So it seems the device or driver is quite confused, this time at least =
:)
>=20
> Can you try running powerhooks at S1 sleep?

No dice. With this change, the suspend part seems to go basically as
before.  The wi card was powered off, but I didn't actually notice
that until after I was powering back on.

On resume, the display blanked as before, but I didn't get it back
with VT switching.  After a few tries at that, I tried closing and
opening the lid, this restored the display to show me a console with:

  panic: trap

and the usual stuff about being unable to dump (to cgd) and a moment
later it was rebooting.

For all I know, this is the same problem as trying to come back from
S3, though I don't see these messages in that case. Otherwise, perhaps
it wasn't able to cope with the acpi lid events at that stage?

So, I have no idea what happened to esa in the process :)

--
Dan.

--kvUQC+jR9YzypDnK
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (NetBSD)

iD8DBQFB+YiXEAVxvV4N66cRAgFDAKCwbwpSIT3+BxBoIkE4AfFZHaYiKwCgwOIS
mG1mWh9v3yjuD7nzok+3Mko=
=RqAL
-----END PGP SIGNATURE-----

--kvUQC+jR9YzypDnK--