From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Mark Knecht <markknecht@gmail.com>,
john stultz <johnstul@us.ibm.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.14-rc5-rt5 - softirq-timer/0/3[CPU#0]: BUG in ktime_get at kernel/ktimers.c:103
Date: Mon, 24 Oct 2005 14:39:52 -0400 [thread overview]
Message-ID: <1130179192.7377.13.camel@localhost.localdomain> (raw)
In-Reply-To: <20051024181320.GA9736@elte.hu>
On Mon, 2005-10-24 at 20:13 +0200, Ingo Molnar wrote:
> * Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > Thomas, this hasn't been done yet, has it?
>
> not yet, but it's in progress. Meanwhile i increased the number of times
> the warning will be printed per bootup (from 1 to 3), so that if a time
> warp happens outside of that clock-switch case it should be printed too.
>
Unfortunately, the problem doesn't go away until the clocks are
eventually updated. So as Mark got, we see three outputs for every time
this happens until the now catches up with the prev.
Perhaps we should also add another update of prev?
-- Steve
Index: kernels/linux-2.6.14-rc5-rt5/kernel/ktimers.c
===================================================================
--- kernels.orig/linux-2.6.14-rc5-rt5/kernel/ktimers.c 2005-10-24 14:34:32.000000000 -0400
+++ kernels/linux-2.6.14-rc5-rt5/kernel/ktimers.c 2005-10-24 14:34:53.000000000 -0400
@@ -102,6 +102,7 @@
ktime_to_ns(prev), ktime_to_ns(now));
WARN_ON(1);
}
+ per_cpu(prev_mono_time, cpu) = now;
return prev;
}
per_cpu(prev_mono_time, cpu) = now;
prev parent reply other threads:[~2005-10-24 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 16:07 2.6.14-rc5-rt5 - softirq-timer/0/3[CPU#0]: BUG in ktime_get at kernel/ktimers.c:103 Mark Knecht
2005-10-24 17:05 ` Steven Rostedt
2005-10-24 18:13 ` Ingo Molnar
2005-10-24 18:39 ` Steven Rostedt [this message]
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=1130179192.7377.13.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markknecht@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox