From: Mike Galbraith <efault@gmx.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [2.6.15-rc7-rt1] check_monotonic_clock: monotonic inconsistency detected!
Date: Sat, 31 Dec 2005 16:00:11 +0100 [thread overview]
Message-ID: <5.2.1.1.2.20051231152916.00bd5fd0@pop.gmx.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 327 bytes --]
Greetings,
After running just fine for most of the day, my PIII/500 coughed up
attached fur-ball as I tried to start my ancient (au) sound
server. Subsequent repeated starting and stopping of same did not induce a
repeat (but then all zillion sound modules were loaded). If any other info
is needed, just holler.
-Mike
[-- Attachment #2: xx --]
[-- Type: application/octet-stream, Size: 803 bytes --]
check_monotonic_clock: monotonic inconsistency detected!
from 191c7872fef6 (27610070580982) to 191c7872dd13 (27610070572307).
softirq-hrtimer/8[CPU#0]: BUG in check_monotonic_clock at kernel/time/timeofday.c:160
[<c0104063>] dump_stack+0x23/0x30 (20)
[<c011db1a>] __WARN_ON+0x6a/0xa0 (44)
[<c013c8d2>] check_monotonic_clock+0xe2/0x100 (52)
[<c013cd85>] get_monotonic_clock+0xe5/0x120 (80)
[<c0135b16>] hrtimer_forward+0x36/0xf0 (80)
[<c0120cbb>] it_real_fn+0x6b/0x80 (28)
[<c0136345>] run_hrtimer_softirq+0x65/0x150 (52)
[<c0122826>] ksoftirqd+0x116/0x1c0 (60)
[<c01325b9>] kthread+0xa9/0xf0 (52)
[<c0101245>] kernel_thread_helper+0x5/0x10 (671293468)
------------------------------
| showing all locks held by: | (softirq-hrtimer/8 [d7fcabb0, 98]):
------------------------------
next reply other threads:[~2005-12-31 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-31 15:00 Mike Galbraith [this message]
2005-12-31 15:49 ` Steven Rostedt
2005-12-31 16:36 ` Mike Galbraith
2005-12-31 17:10 ` [2.6.15-rc7-rt1] explosions in nptl mutex tests Mike Galbraith
2006-01-02 4:46 ` Mike Galbraith
2006-01-04 20:49 ` [2.6.15-rc7-rt1] check_monotonic_clock: monotonic inconsistency detected! john stultz
2006-01-04 20:53 ` Steven Rostedt
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=5.2.1.1.2.20051231152916.00bd5fd0@pop.gmx.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®