mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tony Breeds <tony@bakeyournoodle.com>
To: Chris Largret <largret@gmail.com>
Cc: jstipins@umich.edu, linux-kernel@vger.kernel.org
Subject: Re: AMD 64 system clock speed
Date: Sun, 20 Nov 2005 10:47:08 +1100	[thread overview]
Message-ID: <20051119234708.GH25348@bakeyournoodle.com> (raw)
In-Reply-To: <1132434746.18950.9.camel@shogun.daga.dyndns.org>

On Sat, Nov 19, 2005 at 01:12:26PM -0800, Chris Largret wrote:
> On Fri, 2005-11-18 at 20:01 -0500, jstipins@umich.edu wrote:
> > Hi there,
> > 
> > My earlier question regarding the glibc "make check" nptl/tst-clock2.c
> > failure turns out to be due to my system clock running 3x normal speed.
> > 
> > Evidently, this is a known issue with 2.6.x kernels running on AMD 64
> > processors.  The "noapic" boot option fixes the clock problem, but disrupts
> > other things... ethernet does work, etc.  The solution seems to be using
> > "apci=noirq noapic" as boot options.
> > 
> > I am using the 2.6.14.2 kernel, and still need to use those boot parameters.
> > What is the current state of this bug?
> 
> Interestingly, I found out last night that the 2.4.26 kernel can
> recognize both processors in my X2. Unfortunately, it had the same time
> synchronization issues as the newer 2.6.12+ kernels that I have been
> running. It isn't solely related to the new kernel series.

You could also be seeing the same problem outlined in.
	http://marc.theaimsgroup.com/?t=113097284500003&r=2&w=2

Try booting with: acpi_skip_timer_override instead of the other command
line parameters.

Yours Tony

   linux.conf.au       http://linux.conf.au/ || http://lca2006.linux.org.au/
   Jan 23-28 2006      The Australian Linux Technical Conference!


  reply	other threads:[~2005-11-19 23:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-19  1:01 jstipins
2005-11-19 21:12 ` Chris Largret
2005-11-19 23:47   ` Tony Breeds [this message]
2005-11-20 17:54     ` Akira Tsukamoto

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=20051119234708.GH25348@bakeyournoodle.com \
    --to=tony@bakeyournoodle.com \
    --cc=jstipins@umich.edu \
    --cc=largret@gmail.com \
    --cc=linux-kernel@vger.kernel.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 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®