| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <200610191811.49243.ak@suse.de> Date: Thu, 19 Oct 2006 18:11:49 +0200 From: Andi Kleen <ak@...e.de> To: "Allen Martin" <AMartin@...dia.com> Cc: "Robert Hancock" <hancockr@...w.ca>, "Len Brown" <lenb@...nel.org>, "linux-kernel" <linux-kernel@...r.kernel.org>, "Daniel Mierswa" <impulze@...ulze.org>, "Andy Currid" <ACurrid@...dia.com> Subject: Re: ASUS M2NPV-VM APIC/ACPI Bug (patched) > 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists