Messages in this thread | | | Subject | Re: BUG in check_monotonic_clock() | From | john stultz <> | Date | Fri, 20 Jan 2006 11:09:37 -0800 |
| |
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/
| |