Re: BUG in check_monotonic_clock()

[john stultz <johnstul@us.ibm.com>]

On Fri, 2006-01-20 at 09:51 -0800, Daniel Walker wrote:
> 
> This is off a dual P3 during boot with 2.6.15-rt6. I'll send the .config
> privately . I had a fair amount of debugging on.
> 
> 
> check_monotonic_clock: monotonic inconsistency detected!
>         from        1a27e7384 (7021163396) to        19f92d748 (6972168008).
> udev/238[CPU#1]: BUG in check_monotonic_clock at kernel/time/timeofday.c:160
>  [<c0105b03>] dump_stack+0x23/0x30 (20)
>  [<c0129e43>] __WARN_ON+0x63/0x80 (40)
>  [<c0148584>] check_monotonic_clock+0xd4/0xe0 (52)
>  [<c01489b8>] get_monotonic_clock+0xc8/0x100 (56)
>  [<c014475d>] __hrtimer_start+0xdd/0x100 (40)
>  [<c0400046>] schedule_hrtimer+0x46/0xd0 (48)
>  [<c0144f0f>] hrtimer_nanosleep+0x5f/0x130 (104)
>  [<c0145053>] sys_nanosleep+0x73/0x80 (36)
>  [<c0104b2a>] syscall_call+0x7/0xb (-4020)
> ---------------------------
> | preempt count: 00000002 ]
> | 2-level deep critical section nesting:
> ----------------------------------------
> .. [<c014cf1c>] .... add_preempt_count+0x1c/0x20
> .....[<c0143e2a>] ..   ( <= lock_hrtimer_base+0x2a/0x60)
> .. [<c014cf1c>] .... add_preempt_count+0x1c/0x20
> .....[<c0129df6>] ..   ( <= __WARN_ON+0x16/0x80)

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


-
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/