From: Daniel Walker <dwalker@mvista.com>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: BUG in check_monotonic_clock()
Date: Fri, 20 Jan 2006 09:51:54 -0800 [thread overview]
Message-ID: <1137779515.3202.3.camel@localhost.localdomain> (raw)
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)
next reply other threads:[~2006-01-20 17:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 17:51 Daniel Walker [this message]
2006-01-20 18:07 ` BUG in check_monotonic_clock() 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
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=1137779515.3202.3.camel@localhost.localdomain \
--to=dwalker@mvista.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.