From: Clark Williams <williams@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>, john stultz <johnstul@us.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: hrtimers bug message on 2.6.18-rt4
Date: Mon, 02 Oct 2006 12:39:40 -0500 [thread overview]
Message-ID: <45214EDC.6060706@redhat.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thomas, et al,
I was debugging a PI mutex stress test when I got the following message
on my Athlon64x2 (running 2.6.18-rt4):
BUG: time warp detected!
prev > now, 101878c199393108 > 101878c081eaca2b:
= 4685981405 delta, on CPU#0
[<c0104c3c>] show_trace+0x2c/0x30
[<c0104dcb>] dump_stack+0x2b/0x30
[<c012ec89>] getnstimeofday+0x249/0x270
[<c013e893>] ktime_get_ts+0x23/0x60
[<c013e8ef>] ktime_get+0x1f/0x60
[<c013f042>] hrtimer_interrupt+0x62/0x310
[<c0114557>] smp_apic_timer_interrupt+0x77/0x90
[<c0103f33>] apic_timer_interrupt+0x1f/0x24
[<c0101bc4>] cpu_idle+0x84/0xe0
[<c01007a4>] rest_init+0x54/0x60
[<c06258f6>] start_kernel+0x396/0x460
[<00000000>] 0x0
skipping trace printing on CPU#0 != -1
I've seen this at least three times on -rt4. I'm building -rt5 as I
write this, so I'll run the test again on the new kernel and see what
(if anything) changes.
If you want my test, grab:
http://people.redhat.com/williams/tests/pi_tests.tar.gz
and build pi_stress.
Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFFIU7cHyuj/+TTEp0RAkfdAJ9KLtBlfgYljBYhBatL+/BatsdygwCZAYkz
9d2C/aSysAX5OppUlqbpSzQ=
=kcN9
-----END PGP SIGNATURE-----
next reply other threads:[~2006-10-02 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 17:39 Clark Williams [this message]
2006-10-02 17:45 ` hrtimers bug message on 2.6.18-rt4 john stultz
2006-10-02 17:50 ` Clark Williams
2006-10-04 0:30 ` Daniel Walker
2006-10-04 0:38 ` john stultz
2006-10-04 0:42 ` Daniel Walker
2006-10-18 7:56 ` Ingo Molnar
2006-10-18 8:05 ` Ingo Molnar
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=45214EDC.6060706@redhat.com \
--to=williams@redhat.com \
--cc=johnstul@us.ibm.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.