All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@wildturkeyranch.net>
To: Daniel Walker <dwalker@mvista.com>
Cc: john stultz <johnstul@us.ibm.com>,
	mingo@elte.hu, linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: BUG in check_monotonic_clock()
Date: Fri, 20 Jan 2006 13:29:49 -0800	[thread overview]
Message-ID: <43D1564D.2000303@wildturkeyranch.net> (raw)
In-Reply-To: <1137784987.3202.14.camel@localhost.localdomain>

Daniel Walker wrote:
> On Fri, 2006-01-20 at 11:09 -0800, john stultz wrote:
> 
> 
>>That's what I was guessing. So there aren't any TSC inconsistency
>>messages in the dmesg? Odd.
> 
> 
> I didn't see any ..
> 
> 
>>>Isn't there a handy proc entry for this? 
>>
>>Yep, there's a sysfs entry:
>>
>>	/sys/devices/system/clocksource/clocksource0/current_clocksource 
> 
> 
> Great! The patch that George sent me fixed it .. Thanks George !

By the way, this means you are using a 64-bit ktime and not the dual 32-bit 
ktime.  This _may_ not be what you want on a 32-bit kernel.  There is a 
config option to change this....

-- 
George Anzinger   george@wildturkeyranch.net
HRT (High-res-timers):  http://sourceforge.net/projects/high-res-timers/

      parent reply	other threads:[~2006-01-20 21:31 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
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 [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=43D1564D.2000303@wildturkeyranch.net \
    --to=george@wildturkeyranch.net \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.