From: john stultz <johnstul@us.ibm.com>
To: Philippe Troin <phil@fifi.org>
Cc: linux-kernel@vger.kernel.org, macro@linux-mips.org
Subject: Re: 2.6.25.9: system clocks works normally then speeds up 4x...
Date: Wed, 09 Jul 2008 13:08:45 -0700 [thread overview]
Message-ID: <1215634125.6149.8.camel@localhost.localdomain> (raw)
In-Reply-To: <874p6y25es.fsf@old-tantale.fifi.org>
On Wed, 2008-07-09 at 13:01 -0700, Philippe Troin wrote:
> "john stultz" <johnstul@us.ibm.com> writes:
>
> > On Wed, Jul 9, 2008 at 12:21 PM, Philippe Troin <phil@fifi.org> wrote:
> > >
> > > Symptoms:
> > >
> > > The system boots fine. Clock seems to run normally.
> > >
> > > Then after a random amount of time (on the current boot, 3 days),
> > > clock starts to be running 2-4x faster (on the current boot, 4x).
> > >
> > > I have tried booting with "nohz=off highres=off" but it does not
> > > help.
> >
> > Could you provide the output from the following:
> > sudo cat /sys/devices/system/clocksource/clocksource0/*
>
> Sure.
>
> It is:
> available: jiffies tsc
> current: jiffies
>
> > Did this issue occur with 2.6.24 or earlier kernels?
>
> No. It started with 2.6.25.
>
> Interestingly:
>
> I've just modified the current clocksource to tsc and the clock went
> back to its normal speed.
>
> Then I reset the current clocksource to jiffies, and the clock went
> back to its (wrong) 4x speed.
>
> So it looks like the kernel is counting jiffies 4x too fast.
When you're seeing the issue, can you do the following:
cat /proc/interrupts > interrupts
<wait 10 seconds by your wristwatch>
cat /proc/interrupts >> interrupts
And send the results?
Could you also try booting with noapic to see if that changes anything?
Maciej: Does this sound related to the recent APIC setup changes?
thanks
-john
next prev parent reply other threads:[~2008-07-09 20:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 19:21 Philippe Troin
2008-07-09 19:55 ` john stultz
2008-07-09 20:01 ` Philippe Troin
2008-07-09 20:08 ` john stultz [this message]
2008-07-09 20:53 ` Philippe Troin
2008-07-09 21:21 ` john stultz
2008-07-09 22:50 ` Philippe Troin
2008-07-11 19:53 ` Philippe Troin
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=1215634125.6149.8.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=phil@fifi.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
Powered by JetHome