From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI failures on non-Intel hardware
Date: Sun, 12 Dec 2004 23:19:21 +0000 [thread overview]
Message-ID: <1102893561.5984.38.camel@tyrosine> (raw)
In-Reply-To: <20041212171554.GD6272-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
On Sun, 2004-12-12 at 18:15 +0100, Pavel Machek wrote:
> > I thought that case crashed /inside/ the wakeup code, rather than
> > rebooting before any of it was run?
>
> I saw some Acer (do not recall model #, sorry, and it was probably
> prototype, anyway) where it died before wakeup.
Do you remember whether it had an Intel motherboard chipset, or was an
Intel CPU on something like an ATI chipset?
--
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-12 23:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-11 22:47 ACPI failures on non-Intel hardware Matthew Garrett
2004-12-11 23:32 ` Nate Lawson
2004-12-12 16:41 ` Pavel Machek
[not found] ` <20041212164141.GC6286-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-12-12 16:59 ` Matthew Garrett
2004-12-12 17:15 ` Pavel Machek
[not found] ` <20041212171554.GD6272-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-12-12 23:19 ` Matthew Garrett [this message]
2004-12-13 10:39 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2004-12-13 2:36 Li, Shaohua
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=1102893561.5984.38.camel@tyrosine \
--to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=pavel-+ZI9xUNit7I@public.gmane.org \
/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