From: Daniel Walker <dwalker@mvista.com>
To: john stultz <johnstul@us.ibm.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: BUG in check_monotonic_clock()
Date: Fri, 20 Jan 2006 11:02:30 -0800 [thread overview]
Message-ID: <1137783751.3202.11.camel@localhost.localdomain> (raw)
In-Reply-To: <1137783149.27699.256.camel@cog.beaverton.ibm.com>
On Fri, 2006-01-20 at 10:52 -0800, john stultz wrote:
> On Fri, 2006-01-20 at 10:48 -0800, Daniel Walker wrote:
> > On Fri, 2006-01-20 at 10:38 -0800, john stultz wrote:
> >
> > > Hey Daniel,
> > > Thanks for the bug report. Could you tell me what clocksource was being
> > > used at the time? I'm guessing its the TSC, but usually we'll see
> > > separate TSC inconsistency messages in the log.
> > >
> > > thanks
> > > -john
> > >
> >
> > I had CONFIG_HPET_TIMER turned on. Also X86_TSC was on.
>
> So, booting up the box, what is the last message that looks like:
>
> Time: xyz clocksource has been installed.
Last one is,
kernel: Time: tsc clocksource has been installed.
Isn't there a handy proc entry for this?
Like /proc/sys/kernel/clocksource ?
Daniel
next prev parent reply other threads:[~2006-01-20 19:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 17:51 BUG in check_monotonic_clock() Daniel Walker
2006-01-20 18:07 ` George Anzinger
2006-01-20 18:20 ` Daniel Walker
2006-01-20 18:38 ` john stultz
2006-01-20 18:48 ` Daniel Walker
2006-01-20 18:52 ` john stultz
2006-01-20 19:02 ` Daniel Walker [this message]
2006-01-20 19:09 ` john stultz
2006-01-20 19:23 ` Daniel Walker
2006-01-20 20:20 ` john stultz
2006-01-20 21:29 ` George Anzinger
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=1137783751.3202.11.camel@localhost.localdomain \
--to=dwalker@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).