linux-kernel - Re: [GIT pull] x86/timers for 4.10

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]

Date:   Thu, 09 Feb 2017 16:25:46 +0100
From:   Mike Galbraith <efault@....de>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     Olof Johansson <olof@...om.net>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Ingo Molnar <mingo@...nel.org>,
        "H. Peter Anvin" <hpa@...or.com>,
        Peter Zijlstra <peterz@...radead.org>
Subject: Re: [GIT pull] x86/timers for 4.10

On Thu, 2017-02-09 at 16:21 +0100, Thomas Gleixner wrote:
> On Thu, 9 Feb 2017, Mike Galbraith wrote:
> 
> > On Thu, 2017-02-09 at 16:07 +0100, Thomas Gleixner wrote:
> > > On Wed, 8 Feb 2017, Mike Galbraith wrote:
> > > > On Wed, 2017-02-08 at 12:44 +0100, Thomas Gleixner wrote:
> > > > > On Mon, 6 Feb 2017, Olof Johansson wrote:
> > > > > > [    0.177102] [Firmware Bug]: TSC ADJUST differs: Reference CPU0:
> > > > > > -6495898515190607 CPU1: -6495898517158354
> > > > > 
> > > > > Yay, another "clever" BIOS ....
> > > > 
> > > > Oh yeah, that reminds me...
> > > > 
> > > > I met one such box, and the adjustment code did salvage it, but I had
> > > > to cheat a little for it to do so reliably, as it would sometimes still
> > > > see a delta of 1 or 2 whole cycles, and hand me a useless wreck instead
> > > > quick like bunny big box.
> > > 
> > > Can you share your cheatery ?
> > 
> > I didn't keep it, it was just a bandaid for a fleeting use, dirt simple
> > ignore microscopic delta.
> 
> Can you send me the dmesg output of that box for a good and a bad case or
> don't you have access to it anymore?

I don't even remember which box it was, but I can try to find it again
during idle moments.

	-Mike