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  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]
Date:	Mon, 10 Mar 2014 18:04:03 +0100 (CET)
From:	Thomas Gleixner <>
To:	Paul Bolle <>
cc:	Julian Wollrath <>,,
Subject: Re: [RESEND] Fast TSC calibration fails with v3.14-rc1 and later

On Mon, 10 Mar 2014, Paul Bolle wrote:

> On Mon, 2014-03-10 at 15:06 +0100, Thomas Gleixner wrote:
> > And how is this related to Julians observation, that fast calibration
> > works in 3.13, but stopped to work in 3.14-rc ?
> In the rest of my message - which you didn't quote - I stated that "the
> error need not be v3.14-rc1 specific. But perhaps something changed in
> v3.14-rc1 that makes it easier to trigger that error. I haven't
> checked". (I didn't add that, in my experience, this message is not seen
> at every boot.) So I'm basically advising Julian to double check whether
> this is really a change in behavior between v3.13 and v3.14-rc1. But
> perhaps Julian already did.

Oh, yes.

> > on a Thinkpad x121e (AMD E-450 APU) with version 3.13.5 and earlier of
> > the kernel I get:
> > [...]
> > but starting with v3.14-rc1 the fast TSC calibration fails:

> And I'm also telling Julian that, as far as I can tell, there's no
> reason to print this message at KERN_ERR level because what subsequently
> will happen is that an alternative calibration strategy is tried. So a
> failure of fast TSC calibration is apparently not so severe. See

And that does exactly make the regression he's observing go

We want to know why stuff which worked and actually should still work
suddenly fails. Sure, the machine boots and nothing explodes, but it's
still a regression.

> . Is that analysis incorrect?

Kinda. But there is no reason for the fast calibration to fail except
BIOS induced SMI nonsense.



To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists