From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: sched_clock - cont'd
Date: Fri, 04 Jun 2004 16:51:32 +0000 [thread overview]
Message-ID: <16576.43156.627974.180637@napali.hpl.hp.com> (raw)
In-Reply-To: <40C08A29.A46DF067@nospam.org>
>>>>> On Fri, 04 Jun 2004 16:41:45 +0200, Zoltan Menyhart <Zoltan.Menyhart_AT_bull.net@nospam.org> said:
Zoltan> David, Since I applied your patch, I re-booted my Tiger-4
Zoltan> about 10 times and I got twice the following Oops:
Zoltan> CPU 3: base freq\x199.453MHz, ITC ratio\x13/2, ITC
Zoltan> freq\x1296.444MHz+/--1ppm Calibrating delay loop... 1943.56
Zoltan> BogoMIPS Oops: timer tick before it's due
Zoltan> (itc—c85f8eed,itm—c87b85d7) Oops: timer tick before it's
Zoltan> due (itc—c8d4a7c7,itm—c8dc1d93) Oops: timer tick before
Zoltan> it's due (itc—c949bc39,itm—c95006db)
Zoltan> Once it is over, everything seems to be correct. E.g. I can
Zoltan> stress the system by compiling the kernel with "make -j100".
Zoltan> It's a 2.6.5 kernel.
I forgot to mention: make sure you have Bjorn's patch in your
tree:
Stable cset id: davidm@tiger.hpl.hp.com|ChangeSet|20040513223146|25847
ChangeSet@1.1608.9.11, 2004-05-13 15:31:46-07:00, davidm@tiger.hpl.hp.com
ia64: fix spurious "timer tick before it's due" problem
Patch Bjorn Helgaas: Fix the "timer tick before it's due" complaint
from timer_interrupt(). The problem was that smp_callin() turned
on the periodic timer tick before syncing the ITC with the BP.
This went in _after_ 2.6.6 so it's likely that this will fix your
problem (I never saw the issue on a 4-way, though).
--david
prev parent reply other threads:[~2004-06-04 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 14:41 sched_clock - cont'd Zoltan Menyhart
2004-06-04 14:52 ` David Mosberger
2004-06-04 16:51 ` David Mosberger [this message]
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=16576.43156.627974.180637@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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