From: Andreas Haumer <andreas@xss.co.at>
To: "Yu, Luming" <luming.yu@intel.com>
Cc: Stephan von Krawczynski <skraw@ithnet.com>,
marcelo.tosatti@cyclades.com, andrew@walrond.org,
linux-kernel@vger.kernel.org
Subject: Re: ACPI: problem on ASUS PR-DLS533
Date: Sun, 18 Jan 2004 12:42:17 +0100 [thread overview]
Message-ID: <400A7119.7000803@xss.co.at> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8401720CE9@PDSMSX403.ccr.corp.intel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
Yu, Luming wrote:
> I missed this thread for a few days, What's the conclusion?
>
Good question! :-)
It seems clear, the problem stems from a broken BIOS which
does not correctly initialize some ACPI data structures.
It seems, the specific problem occurs on several different
motherboards, but they are all from the same vendor (ASUS).
So IMHO there are the following possibilities:
a) Find a workaround for this class of broken BIOS behaviour
in the Linux ACPI code.
I do not know if this is A Good Thing(tm) though (and if
it's even possible). This should be decided by the Linux
ACPI driver maintainers. Several bug reports are filed in
the OSDL Bugzilla system already (for example, see
<http://bugme.osdl.org/show_bug.cgi?id=1662> and
<http://bugme.osdl.org/show_bug.cgi?id=1741>)
b) Wait for the vendor to fix the problem in the BIOS.
This requires to file a bug report with the vendor first,
of course. For this it would be necessary to describe the
issue in detail and make clear that it's a BIOS problem
and not a Linux problem. And it would be necessary the
vendor acknowledges the problem.
Alas, in my experience chances are high that any bug report
of this kind vanishes in the dungeons of a vendors internal
bug report escalation strategy... (Does anyone know a direct
technical contact at ASUS?)
c) Ignore it and disable Linux ACPI support on these motherboards
Any comments?
- - andreas
- --
Andreas Haumer | mailto:andreas@xss.co.at
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFACnEPxJmyeGcXPhERAmKEAKC6ED8nghvXV4ti2DLEOOcnhKnLIACfdupb
RNztxbT71WtLMF51siS6cKk=
=BZZ6
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-01-18 11:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 4:23 ACPI: problem on ASUS PR-DLS533 Yu, Luming
2004-01-18 11:42 ` Andreas Haumer [this message]
2004-01-18 16:01 ` Andrew Walrond
2004-01-18 17:00 ` Stephan von Krawczynski
[not found] <BF1FE1855350A0479097B3A0D2A80EE0020ADE84@hdsmsx402.hd.intel.com>
2004-01-18 18:19 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2004-01-18 4:18 Yu, Luming
2004-01-18 9:01 ` Andrew Walrond
2004-01-12 5:14 Yu, Luming
2004-01-15 18:14 ` Andrew Walrond
2004-01-16 10:30 ` Marcelo Tosatti
2004-01-16 11:25 ` Stephan von Krawczynski
2004-01-16 13:14 ` Andreas Haumer
2004-01-16 13:22 ` Stephan von Krawczynski
2004-01-16 12:07 ` Andrew Walrond
2004-01-07 10:50 Yu, Luming
2004-01-07 12:35 ` Stephan von Krawczynski
2004-01-07 22:58 ` Marcelo Tosatti
2003-12-23 12:04 Andreas Haumer
2003-12-23 14:48 ` Andrew Walrond
2003-12-23 15:21 ` Andreas Haumer
2004-01-07 10:37 ` Stephan von Krawczynski
2004-01-07 14:30 ` Andrew Walrond
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=400A7119.7000803@xss.co.at \
--to=andreas@xss.co.at \
--cc=andrew@walrond.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@intel.com \
--cc=marcelo.tosatti@cyclades.com \
--cc=skraw@ithnet.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