From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: ACPI failures on non-Intel hardware
Date: Sat, 11 Dec 2004 22:47:59 +0000 [thread overview]
Message-ID: <1102805280.5984.30.camel@tyrosine> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=3691 describes a fairly
serious ACPI failure. Attempting to wake up from S3 suspend seems to
result in the system rebooting without any wakeup code being run. I've
seen this behaviour on two machines, and had it described to me on a
third. Interestingly, all the machines in question were non-Intel
hardware - one is a VIA C3, and the other two are Athlon XPs (not
Athlon64s). On the test machine I have here, FreeBSD behaves identically
to Linux (seemingly successful suspend, reboot on wake) and Windows
suspends and resumes correctly.
The fact that I've only seen this on systems that didn't have Intel
motherboard chipsets makes me wonder whether there's something going
wrong during the suspend code that happens to work by chance on Intel
(and a few other) chipsets, or alternatively whether these chipsets
manage to fall outside the specs slightly. Any ideas?
--
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 reply other threads:[~2004-12-11 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-11 22:47 Matthew Garrett [this message]
2004-12-11 23:32 ` ACPI failures on non-Intel hardware 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
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=1102805280.5984.30.camel@tyrosine \
--to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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