mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: "Vladimir B. Savkin" <master@sectorb.msk.ru>
Cc: Andi Kleen <ak@suse.de>, lkml <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	discuss@x86-64.org
Subject: Re: [PATCH] x86-64: Fix bad assumption that dualcore cpus have synced TSCs
Date: Mon, 10 Oct 2005 11:03:24 -0700	[thread overview]
Message-ID: <1128967404.8195.419.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <20051008101153.GA1541@tentacle.sectorb.msk.ru>

On Sat, 2005-10-08 at 14:11 +0400, Vladimir B. Savkin wrote:
> On Fri, Oct 07, 2005 at 02:31:46PM +0200, Andi Kleen wrote:
> > On Friday 07 October 2005 14:26, Vladimir B. Savkin wrote:
> > > On Mon, Sep 19, 2005 at 12:16:43PM -0700, john stultz wrote:
> > > > Andrew,
> > > > 	This patch should resolve the issue seen in bugme bug #5105, where it
> > > > is assumed that dualcore x86_64 systems have synced TSCs. This is not
> > > > the case, and alternate timesources should be used instead.
> > > >
> > > > For more details, see:
> > > > http://bugzilla.kernel.org/show_bug.cgi?id=5105
> > >
> > > I too have a box that shows the symptoms from bugzilla entry above.
> > > The system is Asus A8V Deluxe MB with
> > > "AMD Athlon(tm) 64 X2 Dual Core Processor 3800+".
> > >
> > > The patch below did not fix the problem, while "idle=poll" did.
> > > Hope this helps, dmesg attached.
> > 
> > Are you running the latest BIOS?
> 
> Just upgraded to the lastest BIOS (revision 1014), nothing changed.
> Only with "idle=poll" timers run normally.

>From your dmesg, it appears that there are no other timesources other
then the TSC available on your hardware. So I'm guessing idle=poll is
keeping the CPUs from halting the TSC and keeping them synched. 


I would think that the ACPI PM timer would be supported, but I don't see
anything about it in your dmesg. Could you make sure it is properly
configured in?

thanks
-john



  reply	other threads:[~2005-10-10 18:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-19 19:16 john stultz
2005-09-19 19:31 ` Andi Kleen
2005-09-19 19:42   ` john stultz
2005-09-19 19:49     ` [discuss] " Andi Kleen
2005-09-20 18:59       ` john stultz
2005-09-21  4:03         ` Daniel Jacobowitz
2005-09-21 15:15           ` Ray Bryant
2005-09-21 15:04             ` Andi Kleen
2005-09-21 15:46               ` Ray Bryant
2005-09-22  8:00                 ` Jonas Oreland
2005-09-21 20:17               ` Andrew Morton
2005-10-07 12:26 ` Vladimir B. Savkin
2005-10-07 12:31   ` Andi Kleen
2005-10-07 14:15     ` Vladimir B. Savkin
2005-10-07 14:21       ` [discuss] " Velu Erwan
2005-10-08 10:11     ` Vladimir B. Savkin
2005-10-10 18:03       ` john stultz [this message]
2005-10-10 18:12         ` Vladimir B. Savkin
2005-10-10 18:19           ` Jonas Oreland
2005-10-11  7:35             ` Vladimir B. Savkin
2005-10-11  8:06               ` Andi Kleen
2005-10-11 16:27               ` Jonas Oreland
2005-10-25  7:35                 ` x86-64: Syncing dualcore cpus TSCs Jonas Oreland
2005-10-25  7:42                   ` Andi Kleen
2005-10-26  0:05                     ` David Lang

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=1128967404.8195.419.camel@cog.beaverton.ibm.com \
    --to=johnstul@us.ibm.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=master@sectorb.msk.ru \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®