From: Andi Kleen <ak@suse.de>
To: "Allen Martin" <AMartin@nvidia.com>
Cc: "Robert Hancock" <hancockr@shaw.ca>,
"Len Brown" <lenb@kernel.org>,
"linux-kernel" <linux-kernel@vger.kernel.org>,
"Daniel Mierswa" <impulze@impulze.org>,
"Andy Currid" <ACurrid@nvidia.com>
Subject: Re: ASUS M2NPV-VM APIC/ACPI Bug (patched)
Date: Thu, 19 Oct 2006 18:11:49 +0200 [thread overview]
Message-ID: <200610191811.49243.ak@suse.de> (raw)
In-Reply-To: <DBFABB80F7FD3143A911F9E6CFD477B0195D13E6@hqemmail02.nvidia.com>
> The problem is this workaround doesn't fix a chipset issue, it fixes
> incorrect entries in the BIOS ACPI tables. This bug existed in the
> NVIDIA reference BIOS for nForce2 and got copied to all customer BIOSes
> for nForce2. Even though our reference BIOSes and documentation for all
> chipsets since then have the correct interrupt overrides in the ACPI
> tables we still see customer BIOSes that get shipped with incorrect
> entries that were probably copied from their nForce2 BIOS code.
Ah my understanding was that it applied to NF3 and possible NF4 too. Does it
not?
> I believe the HPET check was because the workaround was causing problems
> when enabling HPET on systems that support it. Andy probably has more
> details on that.
Yes it was because NF5 needed it to be disabled. Anyways if I can
get a list of PCI-IDs of chipsets where the reference BIOS had this
issue it can be narrowed to those.
-Andi
next prev parent reply other threads:[~2006-10-19 16:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.09mXx81eXfIStK3wap/U1OZn+kg@ifi.uio.no>
[not found] ` <fa.1/QTOTFQC91cwKwinVDxrePnGHo@ifi.uio.no>
2006-10-19 0:42 ` ASUS M2NPV-VM APIC/ACPI Bug (patched) Robert Hancock
2006-10-19 12:44 ` Andi Kleen
2006-10-19 15:52 ` Allen Martin
2006-10-19 16:11 ` Andi Kleen [this message]
2006-10-20 1:08 ` Allen Martin
2006-10-20 13:04 ` Andi Kleen
2006-11-01 14:21 ` impulze
2006-11-01 14:27 ` Arjan van de Ven
2006-10-18 6:44 Daniel Mierswa
2006-10-18 7:30 ` Len Brown
2006-10-19 12:41 ` Andi Kleen
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=200610191811.49243.ak@suse.de \
--to=ak@suse.de \
--cc=ACurrid@nvidia.com \
--cc=AMartin@nvidia.com \
--cc=hancockr@shaw.ca \
--cc=impulze@impulze.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.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