linux-kernel - Re: 2.6.23-rc4-mm1

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] [day] [month] [year] [list]

Message-Id: <200709041705.45670.alistair@devzero.co.uk>
Date:	Tue, 4 Sep 2007 17:05:45 +0100
From:	Alistair John Strachan <alistair@...zero.co.uk>
To:	Andi Kleen <ak@...e.de>
Cc:	Nicolas Mailhot <nicolas.mailhot@...oste.net>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.23-rc4-mm1

On Tuesday 04 September 2007 16:26:27 Andi Kleen wrote:
> > Seconded. It's been largely ignored which is annoying because the HPET
> > works perfectly on this board. I assume the reason is still that nobody
> > from NVIDIA verified hardward support for the hack.
>
> It's IMHO a bad idea to add any overrides without access to data sheets
> and errata sheets. The hardware might be broken and do bad
> (subtle) bad things with HPET.  That's not a theoretical case.
> There used to be at least one case where a chipset would occasionally
> destroy the BIOS flash when HPET was force enabled.

I haven't used any CK804 with an HPET which is BIOS enabled by default, so 
it's probably most likely that the reference BIOS didn't enable it.

As this technology is quite antiquated, the usual "well Vista uses HPET, so 
maybe vendors will enable it" probably won't apply. I know for my board, no 
BIOS has been released since early 2006.

> That means for Intel it's fine to do (because errata sheets are public);
> but for Nvidia and VIA it's dangerous and should not be done.

I don't disagree with you and I think you're right in the general case, but 
even if we could pin somebody down from NVIDIA (which is seeming unlikely, 
considering the right people have already been CCed), it would still be a 
BIOS override.

In this case,  there's a perfectly good HPET masked behind what I can only 
speculate is a BIOS misfeature (my kernel's behaved itself with Mikko's patch 
applied and Thomas's HRT patchset on x86-64).

What about an expert option which could force the HPET on (rather than "find" 
and enable it)? Are you opposed to this too?

-- 
Cheers,
Alistair.

137/1 Warrender Park Road, Edinburgh, UK.
-
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/