linux-kernel - Re: [bisected] Clocksource tsc unstable git

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: <20101029115438.GA15838@arch.trippelsdorf.de>
Date:	Fri, 29 Oct 2010 13:54:38 +0200
From:	Markus Trippelsdorf <markus@...ppelsdorf.de>
To:	Borislav Petkov <bp@...64.org>
Cc:	Borislav Petkov <bp@...en8.de>, john stultz <johnstul@...ibm.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"hpa@...ux.intel.com" <hpa@...ux.intel.com>,
	Ingo Molnar <mingo@...e.hu>,
	"Herrmann3, Andreas" <Andreas.Herrmann3@....com>,
	"heiko.carstens@...ibm.com" <heiko.carstens@...ibm.com>,
	"a.p.zijlstra@...llo.nl" <a.p.zijlstra@...llo.nl>,
	"avi@...hat.com" <avi@...hat.com>,
	"mtosatti@...hat.com" <mtosatti@...hat.com>
Subject: Re: [bisected] Clocksource tsc unstable git

On Fri, Oct 29, 2010 at 01:39:34PM +0200, Borislav Petkov wrote:
> On Fri, Oct 29, 2010 at 07:34:33AM -0400, Markus Trippelsdorf wrote:
> > > Markus, can you verify this on your system by compiling x86info from
> > > git://git.choralone.org/git/x86info and doing
> > > 
> > > ./lsmsr Int
> > 
> > 
> > x86info v1.28beta.  Dave Jones 2001-2010
> > Feedback to <davej@...hat.com>.
> > 
> > Found 4 CPUs
> > --------------------------------------------------------------------------
> > CPU #1
> > EFamily: 1 EModel: 0 Family: 15 Model: 4 Stepping: 2
> > CPU Model: Quad-Core Opteron/Phenom II (RB-C2)
> 
> well, x86info doesn't help - there's a lsmsr tool which is being built
> too but no need, I can infer the info from your revision: your CPU is
> RB-C2 which does SMI initiated C1E.

Sorry. Here is the correct output:

IntPendingMessage    = 0x0000000008c200b0

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