All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: thockin@hockin.org
Cc: Andi Kleen <ak@suse.de>, Lee Revell <rlrevell@joe-job.com>,
	Luca Tettamanti <kronos.it@gmail.com>,
	linux-kernel@vger.kernel.org, john stultz <johnstul@us.ibm.com>
Subject: Re: AMD X2 unsynced TSC fix?
Date: Sat, 28 Oct 2006 22:16:29 +0200	[thread overview]
Message-ID: <20061028201628.GC1603@1wt.eu> (raw)
In-Reply-To: <20061028194245.GA24083@hockin.org>

On Sat, Oct 28, 2006 at 12:42:45PM -0700, thockin@hockin.org wrote:
> On Sat, Oct 28, 2006 at 09:32:18PM +0200, Willy Tarreau wrote:
> > > Was the problem that they were not synced at poweron or that they would
> > > drift due to power-states?
> > 
> > They resynced at power up, but would constantly drift. I don't even know
> > if it was caused by power states. When the machine was loaded, a single
> > task moving across the cores could see its time jump back and forth 
> > several times a second by an offset sometimes close to +2/-2s.
> 
> That sounds like C1, to me.

OK.

> > > Did you try running with idle=poll, to avoid ever entering C1 state (hlt)?
> > 
> > Yes, I remember trying such things. I also tried 'nohlt', completely
> > disabling power management, including ACPI, etc... I also tried vanilla
> > kernels as well as severely patched ones, but the problem remained the
> > same in all circumstances, that only 'notsc' could solve.
> 
> That's exceedingly strange.  On my dual-socket dual-core, I can get
> roughly synced TSCs (no appreciable drift) by just using idle=poll.

As I said in another mail, I thought I won by running several busy loops
in parallel to the load, which prevented the system from either halting
or slowing down. But it was OK for a few minutes only and started going
mad again.

> If that did not work for you, I'd really want to poke at the system more.

The machine was returned to the supplier and for other reasons, we switched
to a different maker for the about 20 machines (and all single-core). I've
read somewhere that there's already a second version of the sun x2100, I
don't know if it still exhibits the problem. Maybe at least they've fixed
the BIOS to report the HPET.

> > BTW, I've just found a remain of dmesg capture after boot in case you'd
> > like to look for anything in it.
> 
> A dmesg won't be that useful, I'd actually have to poke at the system.

OK. I don't know if anyone there has one at hand, as I don't have it
anymore.

Regards,
Willy


  reply	other threads:[~2006-10-28 20:16 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-27 17:15 AMD X2 unsynced TSC fix? Lee Revell
2006-10-27 20:18 ` Luca Tettamanti
2006-10-27 23:04   ` thockin
2006-10-28  0:00     ` Luca Tettamanti
2006-10-28  0:17       ` Lee Revell
2006-10-28  2:46       ` thockin
2006-10-28  3:59         ` Andi Kleen
2006-10-28  6:32           ` thockin
2006-10-28  9:14           ` Vojtech Pavlik
2006-10-28 18:22           ` Lee Revell
2006-10-28 19:57             ` Vojtech Pavlik
2006-10-28 22:54               ` thockin
2006-10-28  1:04     ` Andi Kleen
2006-10-28  3:28       ` Lee Revell
2006-10-28  5:28         ` Willy Tarreau
2006-10-28 18:08           ` Lee Revell
2006-10-28 19:14             ` thockin
2006-10-30 17:22             ` Langsdorf, Mark
2006-10-28 18:37           ` Andi Kleen
2006-10-28 19:15             ` Willy Tarreau
2006-10-28 19:18               ` thockin
2006-10-28 19:32                 ` Willy Tarreau
2006-10-28 19:42                   ` thockin
2006-10-28 20:16                     ` Willy Tarreau [this message]
2006-10-28 19:33               ` Andi Kleen
2006-10-28 20:04                 ` Willy Tarreau
2006-10-28 20:11                   ` Andi Kleen
2006-10-28 20:36                     ` Willy Tarreau
2006-10-29  1:28                 ` Lee Revell
2006-10-28 21:00               ` Lee Revell
2006-10-31 11:12           ` Pádraig Brady
2006-10-31 15:31             ` Willy Tarreau
2006-10-30 20:30     ` Christoph Lameter
2006-10-27 20:35 ` Andi Kleen
2006-10-27 20:41   ` Lee Revell
2006-10-27 21:48     ` Chris Friesen
2006-10-27 22:08       ` Lee Revell
2006-10-28  3:58         ` Sergio Monteiro Basto
2006-10-28  4:06           ` Andi Kleen
2006-10-28  4:22             ` Sergio Monteiro Basto
2006-10-30  3:10               ` Sergio Monteiro Basto
2006-10-30 15:23                 ` Andi Kleen
     [not found]                   ` <1162253008.2999.9.camel@localhost.portugal>
2006-10-31  0:14                     ` Lee Revell
2006-10-31  0:25                       ` john stultz
2006-10-31  2:41                     ` Siddha, Suresh B
2006-10-31 15:05                       ` Sergio Monteiro Basto
2006-11-01  1:46                       ` Sergio Monteiro Basto
2006-11-01  2:44                         ` Siddha, Suresh B
2006-11-08  0:22                           ` Sergio Monteiro Basto
2006-11-08 19:53                             ` Thomas Gleixner
2006-11-09  0:39                               ` Sergio Monteiro Basto
2006-11-09  1:13                                 ` john stultz
2006-11-09  1:27                                   ` Sergio Monteiro Basto
2006-11-15  1:51                                   ` Sergio Monteiro Basto
     [not found]                                     ` <20061115193514.41C01102C011@mail.goron.de>
2006-11-16  1:38                                       ` Sergio Monteiro Basto
2006-11-16  1:45                                         ` Sergio Monteiro Basto
2006-10-28  6:35             ` thockin
2006-10-28  6:46               ` Andrew Morton
2006-10-28  6:49                 ` thockin
2006-10-28  7:13                   ` Andrew Morton
2006-10-28  7:25                     ` thockin
2006-10-28  9:46                   ` Andi Kleen
2006-10-28  9:45                 ` Andi Kleen
2006-10-28  9:48               ` Andi Kleen
2006-10-27 21:58 ` Friedrich Göpel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061028201628.GC1603@1wt.eu \
    --to=w@1wt.eu \
    --cc=ak@suse.de \
    --cc=johnstul@us.ibm.com \
    --cc=kronos.it@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    --cc=thockin@hockin.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.