linux-kernel - RE: ASUS M2NPV-VM APIC/ACPI Bug (patched)

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <DBFABB80F7FD3143A911F9E6CFD477B00E48D31D@hqemmail02.nvidia.com>
Date:	Thu, 19 Oct 2006 18:08:12 -0700
From:	"Allen Martin" <AMartin@...dia.com>
To:	"Andi Kleen" <ak@...e.de>
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)

> 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.

Well that's the problem.  The issue only existed in the nForce2
reference BIOS (and maybe early in nForce3) but we still occasionally
see shipping customer BIOSes to this day that have this same bug for
nForce5 (like M2NPV referenced in this thread).

Probably what ASUS is doing in the M2NPV BIOS is copying the ACPI tables
from an earlier nForce2 product.

Probably what needs to happen is to make the HPET check more robust and
only return 1 if HPET is present and enabled.
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
-
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/