All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Cordes <peter@cordes.ca>
To: Andi Kleen <ak@suse.de>
Cc: Mikael Pettersson <mikpe@csd.uu.se>,
	discuss@x86-64.org, linux-kernel@vger.kernel.org,
	len.brown@intel.com
Subject: Re: x86-64: double timer interrupts in recent 2.4.x
Date: Fri, 18 Jun 2004 04:41:32 -0300	[thread overview]
Message-ID: <20040618074132.GA17508@cordes.ca> (raw)
In-Reply-To: <20040617122645.5d1b5ec1.ak@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]

On Thu, Jun 17, 2004 at 12:26:45PM +0200, Andi Kleen wrote:
> On Thu, 17 Jun 2004 10:54:00 +0200 (MEST)
> Mikael Pettersson <mikpe@csd.uu.se> wrote:
> 
> > On Wed, 16 Jun 2004 16:28:26 -0300, Peter Cordes wrote:
> > > I just noticed that on my Opteron cluster, the nodes that are running 64bit
> > >kernels have their clocks ticking at double speed.  This happens with
> > >Linux 2.4.26, and 2.4.27-pre2
> > 
> > I had the same problem: 2.4 x86-64 kernels ticking the clock
> > twice its normal speed, unless I booted with pci=noacpi.
> > 
> > This got fixed very recently I believe, in a 2.4.27-pre kernel.
> 
> In which one exactly? Most likely it was an ACPI problem/fix.
> Len, do you remember fixing such an issue?

 It's fixed in 2.4.27-pre3 and later.  Coincidentally or not, it was
released only 4 days after I mentioned the bug on debian-amd64 and
discuss@x86-64.  I'd narrow it down further, but kernel.org doesn't have -bk
patches for 2.4, and I don't know where to download more fine-grained patch
versions.

 (BTW, 2.4.27-pre6 doesn't compile without declaring 
struct task_struct *tsk;  in rwsem-spinlock.c:__rwsem_wake_one_writer.)

 Thanks for the help.

-- 
#define X(x,y) x##y
Peter Cordes ;  e-mail: X(peter@cor , des.ca)

"The gods confound the man who first found out how to distinguish the hours!
 Confound him, too, who in this place set up a sundial, to cut and hack
 my day so wretchedly into small pieces!" -- Plautus, 200 BC

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 351 bytes --]

  parent reply	other threads:[~2004-06-18  7:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17  8:54 x86-64: double timer interrupts in recent 2.4.x Mikael Pettersson
2004-06-17 10:26 ` Andi Kleen
2004-06-17 10:49   ` Mikael Pettersson
2004-06-17 14:26   ` Len Brown
2004-06-18  7:41   ` Peter Cordes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-19 12:39 Mikael Pettersson
2004-06-19 13:55 ` Len Brown
2004-06-16 19:28 Peter Cordes
2004-06-16 19:42 ` Andi Kleen

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=20040618074132.GA17508@cordes.ca \
    --to=peter@cordes.ca \
    --cc=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    /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.