From: Len Brown <len.brown@intel.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: Andrew Walrond <andrew@walrond.org>,
andreas@xss.co.at, Luming Yu <luming.yu@intel.com>,
marcelo.tosatti@cyclades.com, linux-kernel@vger.kernel.org
Subject: Re: ACPI: problem on ASUS PR-DLS533
Date: 18 Jan 2004 13:19:39 -0500 [thread overview]
Message-ID: <1074449979.2387.41.camel@dhcppc4> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE0020ADE84@hdsmsx402.hd.intel.com>
Yes, bugzilla 1662 (1127, 1741) appears to be a BIOS bug -- _BBN returns
0. I believe that this is not a Linux regression, but would break any
version of Linux/ACPI shipped to date.
I've no idea how Windows would cope with this -- unless they're using a
workaround outside the ACPI spec. It appears that the failing systems
all have serverworks chip-sets -- so there may be a chip-set dependent
issue we don't know about.
Thanks for making sure that you're running the latest BIOS.
I do think we should contact Asus to request them to fix it. However,
my experience is that vendors are very good about fixing bugs that are
found whey they're validating their new systems, but much less
responsive for systems that have already shipped -- more so as the
systems age. This is why it is important that passing some Linux distro
validation suite become a prerequisite for OEMs to start shipping
systems.
I do think we should investigate how to make Linux more robust in the
face of this issue. Lets work it here:
http://bugzilla.kernel.org/show_bug.cgi?id=1662
thanks,
-Len
next parent reply other threads:[~2004-01-18 18:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BF1FE1855350A0479097B3A0D2A80EE0020ADE84@hdsmsx402.hd.intel.com>
2004-01-18 18:19 ` Len Brown [this message]
2004-01-18 4:23 ACPI: problem on ASUS PR-DLS533 Yu, Luming
2004-01-18 11:42 ` Andreas Haumer
2004-01-18 16:01 ` Andrew Walrond
2004-01-18 17:00 ` Stephan von Krawczynski
-- 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=1074449979.2387.41.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=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