| 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
| ||
|
Date: Thu, 19 Oct 2006 14:44:53 +0200 From: Andi Kleen <ak@...e.de> To: Robert Hancock <hancockr@...w.ca> Cc: 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) > I think the intent of the HPET check was that the quirk wasn't needed on > chipsets new enough to have an HPET. Yes. > Unfortunately, even if the chipset > has an HPET it isn't always enabled by the BIOS. It was supposed to be correct in the NF5 reference BIOS, but somehow Asus must have managed to break the reference BIOS. > Clearly this quirk is too broad, it should likely be only triggering on > known chipset revisions with the bad timer overrides and not on all > NVIDIA chipsets. That was impossible at the point where it was implemented. > What I am wondering is how these boards manage to work > fine in Windows, (presumably) without any such chipset-specific tweaks.. They use the RTC interrupt for timing instead AFAIK so a broken interrupt 0 won't affect them. That's probably why we have so many problems with interrupt 0 on cheap systems. I tried it once to use in Linux too BTW, but it unfortunately cannot generate any of the standard Linux timer frequencies. -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