linux-kernel - Re: AMD X2 unsynced TSC fix?

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] [day] [month] [year] [list]

Date:	Wed, 15 Nov 2006 01:51:54 +0000
From:	Sergio Monteiro Basto <sergio@...giomb.no-ip.org>
To:	john stultz <johnstul@...ibm.com>
Cc:	tglx@...utronix.de, "Siddha, Suresh B" <suresh.b.siddha@...el.com>,
	Andi Kleen <ak@...e.de>, Lee Revell <rlrevell@...-job.com>,
	Chris Friesen <cfriesen@...tel.com>,
	linux-kernel <linux-kernel@...r.kernel.org>, len.brown@...el.com,
	Ingo Molnar <mingo@...e.hu>,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: AMD X2 unsynced TSC fix?

On Wed, 2006-11-08 at 17:13 -0800, john stultz wrote:
> On Thu, 2006-11-09 at 00:39 +0000, Sergio Monteiro Basto wrote:
> > On Wed, 2006-11-08 at 20:53 +0100, Thomas Gleixner wrote:
> > > This one is a lock dependency problem, which is fixed in -rc5-mm1
> > 
> > yes, oops fixed w/ and w/o notsc option.
> > Other question, hrtimer in 2.6.18 found acpi_pm clocksource and use it.
> > With 2.6.19-rcx can't get acpi_pm clocksource even trying force at boot
> > kernel with clocksource=acpi_pm, any idea ?
> > because with this clocksource my lost ticket disappears 
> 
> Looking at the dmesg in the bugzilla:
> http://bugzilla.kernel.org/show_bug.cgi?id=6419
> 
> I noticed you're using x86_64. 

yes, I _just_ use x86_64 never test it on i386.

> x86_64 doesn't yet support clocksource
> overrides in mainline,

petty , can I have a experimental patch to test it?

>  as it is not converted to GENERIC_TIME. (Probably
> printing out such a warning if an override is used would be nice. I'll
> try to get to that soon.)
> 
> Now, the code to convert x86_64 is in tglx's hrtimer patch set, so I'm
> glad to hear its working for you, however I'm not sure if it really is
> solving the issue or just hiding it (as lost ticks won't affect
> timekeeping when you use continuous clocksources and GENERIC_TIME).

Well, the only kernel where I can work (yes I use computer to work) is
2.6.18 + dyntick. I think don't hid neither solve the issue, is just use
other resource (clocksource) that works better ! .

> 
> To use the ACPI PM w/ a 2.6.19-rcX kernel, use "notsc", and you'll see
> the line:
>  time.c: Using 3.579545 MHz WALL PM GTOD PM timer.
> 
> Using the "notsc" option, do you continue to see lost tick messages
> after bootup?

I just test 2.6.19-RC5-mm2 and still very unstable even with notsc. 
And after bootup, yes appears some lost tick messages.
Just trying rebuild other kernel and use command yum to update others
things, at same time, have lock up my computer.
So I back to kernel 2.6.18 + dyntick  

Thanks,

> 
> thanks
> -john
> 
> 
-- 
Sérgio M.B.

Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (2166 bytes)