From: Daniel Walker <dwalker@mvista.com>
To: john stultz <johnstul@us.ibm.com>
Cc: Clark Williams <williams@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: hrtimers bug message on 2.6.18-rt4
Date: Tue, 03 Oct 2006 17:30:45 -0700 [thread overview]
Message-ID: <1159921845.1979.9.camel@dwalker1.mvista.com> (raw)
In-Reply-To: <1159811130.5873.5.camel@localhost.localdomain>
On Mon, 2006-10-02 at 10:45 -0700, john stultz wrote:
> On Mon, 2006-10-02 at 12:39 -0500, Clark Williams wrote:
> > 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
>
> Could you send me your dmesg and .config?
>
This is likely a different issue but, I can generate this messages, like
the following,
BUG: time warp detected!
prev > now, 1018dd8f5e9e5c1f > 0000001748787c3e:
= 1159920411885297633 delta, on CPU#1
[<c010473b>] show_trace_log_lvl+0x1eb/0x1f0
[<c0104efb>] show_trace+0x1b/0x20
[<c0105004>] dump_stack+0x24/0x30
[<c012b030>] do_gettimeofday+0x1a0/0x1d0
[<c0125024>] sys_gettimeofday+0x24/0x90
[<c0103567>] syscall_call+0x7/0xb
[<b7f9b410>] 0xb7f9b410
With ltpstess . It has a settimeofday test which can trigger it. It gets
called with wild values.
Daniel
next prev parent reply other threads:[~2006-10-04 0:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 17:39 Clark Williams
2006-10-02 17:45 ` john stultz
2006-10-02 17:50 ` Clark Williams
2006-10-04 0:30 ` Daniel Walker [this message]
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=1159921845.1979.9.camel@dwalker1.mvista.com \
--to=dwalker@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
/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
Powered by JetHome