From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: 2.6.21-mm2: ACPI exception on resume
Date: Sat, 19 May 2007 17:45:04 -0300 [thread overview]
Message-ID: <20070519204504.GA24704@khazad-dum.debian.net> (raw)
In-Reply-To: <20070519165738.GK11115@waste.org>
On Sat, 19 May 2007, Matt Mackall wrote:
> usually does, then go black and the machine will become totally
> unresponsive, even to holding down the power button for 30+ seconds.
Now, that means either the BIOS or EC have been thrown out of whack,
otherwise one of the two would have force-powered-off the machine a bit
after 10s.
Are you using the latest BIOS and EC firmware available?
If you are at the latest BIOS and EC releases, does ec_intr=0 fix the issue?
> 08:57:27 [drm] Loading R200 Microcode
> 08:57:27 ACPI: EC: acpi_ec_wait timeout, status = 10, expect_event = 2
> 08:57:27 ACPI: EC: input buffer is not empty, aborting transaction
> 08:57:28 ACPI: EC: acpi_ec_wait timeout, status = 10, expect_event = 2
Yep, EC is confused. Not Good!
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2007-05-19 20:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 16:57 2.6.21-mm2: ACPI exception on resume Matt Mackall
2007-05-19 18:24 ` Rafael J. Wysocki
2007-05-19 22:40 ` Matt Mackall
2007-05-19 23:05 ` Rafael J. Wysocki
2007-05-19 20:45 ` Henrique de Moraes Holschuh [this message]
2007-05-19 22:38 ` Matt Mackall
2007-05-20 3:52 ` Henrique de Moraes Holschuh
2007-05-21 22:23 ` Matt Mackall
2007-05-21 23:03 ` Henrique de Moraes Holschuh
2007-05-22 22:45 ` Matt Mackall
2007-05-23 0:19 ` Henrique de Moraes Holschuh
2007-05-23 1:48 ` Matt Mackall
2007-05-23 4:19 ` Henrique de Moraes Holschuh
2007-05-23 4:41 ` Ray Lee
2007-05-23 12:51 ` Henrique de Moraes Holschuh
2007-05-23 22:50 ` Ray Lee
2007-05-24 0:28 ` Henrique de Moraes Holschuh
2007-05-24 1:37 ` Ray Lee
2007-05-27 21:02 ` Pavel Machek
2007-05-23 8:57 ` Rafael J. Wysocki
2007-05-23 17:13 ` Henrique de Moraes Holschuh
2007-05-23 17:48 ` Matt Mackall
2007-05-23 20:56 ` Rafael J. Wysocki
2007-05-23 21:15 ` Matt Mackall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070519204504.GA24704@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=akpm@linux-foundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox