linux-kernel - Re: [RESEND] Fast TSC calibration fails with v3.14-rc1 and later

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: <1394476346.12752.43.camel@x220>
Date:	Mon, 10 Mar 2014 19:32:26 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Jerome Oufella <jerome.oufella@...oirfairelinux.com>,
	Julian Wollrath <jwollrath@....de>, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [RESEND] Fast TSC calibration fails with v3.14-rc1 and later

[Added Jerome, who submitted a patch similar to mine.]

On Mon, 2014-03-10 at 18:04 +0100, Thomas Gleixner wrote:
> On Mon, 10 Mar 2014, Paul Bolle wrote:
> > https://lkml.org/lkml/2012/9/24/221 . Is that analysis incorrect?
> 
> Kinda. But there is no reason for the fast calibration to fail except
> BIOS induced SMI nonsense.

What made me submit my patch, in 2012, is that this error is printed
very early, before boot animation kicks in. Ie, it looks rather scary.
And when I dug through the code I noticed that this condition seems
actually to be handled already: the kernel just tries an alternative
calibration method.

So I think this should be printed at (say) KERN_INFO level (so it will
be suppressed during boot). More so if the solution would be "upgrade
the BIOS". Upgrading the BIOS on a ThinkPad, for instance, can require
fiddling with quite a bit of low level programs. And how do we know an
upgraded BIOS actually helps?

Or is there a way to handle the "SMI nonsense" (whatever that may be)?

Paul Bolle

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