From: Len Brown <len.brown@intel.com>
To: Andi Kleen <ak@suse.de>
Cc: Mikael Pettersson <mikpe@csd.uu.se>,
discuss@x86-64.org, linux-kernel@vger.kernel.org,
peter@cordes.ca
Subject: Re: x86-64: double timer interrupts in recent 2.4.x
Date: 17 Jun 2004 10:26:44 -0400 [thread overview]
Message-ID: <1087482393.4487.56.camel@dhcppc4> (raw)
In-Reply-To: <20040617122645.5d1b5ec1.ak@suse.de>
On Thu, 2004-06-17 at 06:26, 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?
No, I don't remember this symptom.
-Len
next prev parent reply other threads:[~2004-06-17 14:27 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 [this message]
2004-06-18 7:41 ` Peter Cordes
-- 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=1087482393.4487.56.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=peter@cordes.ca \
/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