linux-kernel - Re: REGRESSION: the new i386 timer code fails to sync CPUs

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:	Mon, 31 Jul 2006 18:47:01 -0700
From:	"Siddha, Suresh B" <suresh.b.siddha@...el.com>
To:	Matthias Urlichs <smurf@...rf.noris.de>
Cc:	Arjan van de Ven <arjan@...radead.org>, Andi Kleen <ak@....de>,
	Andrew Morton <akpm@...l.org>,
	john stultz <johnstul@...ibm.com>,
	linux-kernel@...r.kernel.org, torvalds@...l.org, bunk@...sta.de,
	lethal@...ux-sh.org, hirofumi@...l.parknet.co.jp,
	asit.k.mallick@...el.com
Subject: Re: REGRESSION: the new i386 timer code fails to sync CPUs

On Sun, Jul 30, 2006 at 11:55:09PM +0200, Matthias Urlichs wrote:
> Hi,
> 
> Arjan van de Ven:
> > if the hardware side is different *speed*.. then a tsc sync ain't going
> > to work... sure we write to it but it's immediately out of sync again
> > 
> No, it's in fact the same speed -- the BIOS just reads it wrongly.

It sounds to me as a BIOS issue. From the boot log, it is quite clear that
TSCs are running at different speeds(different bogomips show this).
This CPU stepping has constant TSC behavior. So this is most probably happening
because of bios setting different core to bus clock ratios for each package.
Different CPU speed BIOS issue that you mention also points to this.

Can you check if your BIOS settings are set to max ratio(15?) available?
or try an updated BIOS?

> 
> I checked: the two date values do advance at the same rate.

Perhaps data overflow(because of unsync TSC's) in timer code calculations
may be causing this?

thanks,
suresh
-
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/