public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.15-rc7-rt1] check_monotonic_clock: monotonic inconsistency detected!
Date: Wed, 04 Jan 2006 12:49:43 -0800	[thread overview]
Message-ID: <1136407813.2351.2.camel@leatherman> (raw)
In-Reply-To: <5.2.1.1.2.20051231171108.00bd9f40@pop.gmx.net>

On Sat, 2005-12-31 at 17:36 +0100, Mike Galbraith wrote:
> At 10:49 AM 12/31/2005 -0500, Steven Rostedt wrote:
> >   And John will
> >probably want to see your dmesg output.

Am I so predictable? :)

> I'll send that off-line upon request.  FWIW, it's not the original boot 
> dmesg output however, but one a freshly booted system...

Please do send a dmesg to me. I'm looking to find which clocksource
caused this warning. Its probably the TSC, which isn't surprising, but I
want to be sure.

thanks
-john



  parent reply	other threads:[~2006-01-04 20:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-31 15:00 [2.6.15-rc7-rt1] check_monotonic_clock: monotonic inconsistency detected! Mike Galbraith
2005-12-31 15:49 ` Steven Rostedt
2005-12-31 16:36   ` Mike Galbraith
2005-12-31 17:10     ` [2.6.15-rc7-rt1] explosions in nptl mutex tests Mike Galbraith
2006-01-02  4:46       ` Mike Galbraith
2006-01-04 20:49     ` john stultz [this message]
2006-01-04 20:53       ` [2.6.15-rc7-rt1] check_monotonic_clock: monotonic inconsistency detected! Steven Rostedt

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=1136407813.2351.2.camel@leatherman \
    --to=johnstul@us.ibm.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --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