Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932073AbWATTKF (ORCPT ); Fri, 20 Jan 2006 14:10:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932098AbWATTKE (ORCPT ); Fri, 20 Jan 2006 14:10:04 -0500 Received: from e34.co.us.ibm.com ([32.97.110.152]:57249 "EHLO e34.co.us.ibm.com") by vger.kernel.org with ESMTP id S932074AbWATTJp (ORCPT ); Fri, 20 Jan 2006 14:09:45 -0500 Subject: Re: BUG in check_monotonic_clock() From: john stultz To: Daniel Walker Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, tglx@linutronix.de In-Reply-To: <1137783751.3202.11.camel@localhost.localdomain> References: <1137779515.3202.3.camel@localhost.localdomain> <1137782296.27699.253.camel@cog.beaverton.ibm.com> <1137782896.3202.9.camel@localhost.localdomain> <1137783149.27699.256.camel@cog.beaverton.ibm.com> <1137783751.3202.11.camel@localhost.localdomain> Content-Type: text/plain Date: Fri, 20 Jan 2006 11:09:37 -0800 Message-Id: <1137784177.27699.260.camel@cog.beaverton.ibm.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1281 Lines: 41 On Fri, 2006-01-20 at 11:02 -0800, Daniel Walker wrote: > 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. That's what I was guessing. So there aren't any TSC inconsistency messages in the dmesg? Odd. > Isn't there a handy proc entry for this? Yep, there's a sysfs entry: /sys/devices/system/clocksource/clocksource0/current_clocksource thanks -john - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/