From: john stultz <johnstul@us.ibm.com>
To: tglx@linutronix.de
Cc: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: False positive (well not really) on RT backward clock check
Date: Fri, 21 Oct 2005 10:59:48 -0700 [thread overview]
Message-ID: <1129917588.27168.215.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <1129909935.15748.12.camel@tglx.tec.linutronix.de>
On Fri, 2005-10-21 at 17:52 +0200, Thomas Gleixner wrote:
> On Fri, 2005-10-21 at 11:46 -0400, Steven Rostedt wrote:
> >
> > I think you're right about that. Here it is.
> >
> > Sorry for the late reply. The original was from my custom kernel and I
> > wanted to get an output from Ingo's. This is rc5-rt1.
> >
> > -- Steve
> >
> > isapnp: Scanning for PnP cards...
> > Time: tsc clocksource has been installed.
> > WARNING: non-monotonic time!
> > Ktimers: Switched to high resolution mode CPU 0
> > softirq-timer/1/14[CPU#1]: BUG in ktime_get at kernel/ktimers.c:101
> > [<c0104433>] dump_stack+0x23/0x30 (20)
> > [<c0121427>] __WARN_ON+0x67/0x80 (44)
> > [<c013ad82>] ktime_get+0xd2/0x100 (48)
> > [<c013c2b6>] ktimer_run_queues+0x56/0x130 (60)
> > [<c012abbe>] run_timer_softirq+0x12e/0x450 (56)
> > [<c01268b0>] ksoftirqd+0x120/0x1a0 (40)
> > [<c01376eb>] kthread+0xbb/0xc0 (48)
> > [<c01014a5>] kernel_thread_helper+0x5/0x10 (538427420)
> > ---------------------------
> > | preempt count: 00000001 ]
> > | 1-level deep critical section nesting:
> > ----------------------------------------
> > .. [<c0143edc>] .... add_preempt_count+0x1c/0x20
> > .....[<c01213db>] .. ( <= __WARN_ON+0x1b/0x80)
> >
> > Ktimers: Switched to high resolution mode CPU 1
>
> This is at the moment where the clock source is switched over. I check
> what might be the reason.
>
> John, any idea ?
This is using the B7 tod code, correct? If so, B8 corrected a problem
specifically with changing clocksources (most easily seen while changing
to the TSC based clocksource), so I would not be surprised if this is
the same bug.
thanks
-john
next prev parent reply other threads:[~2005-10-21 17:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 13:45 Steven Rostedt
2005-10-21 13:52 ` Thomas Gleixner
2005-10-21 15:46 ` Steven Rostedt
2005-10-21 15:52 ` Thomas Gleixner
2005-10-21 17:59 ` john stultz [this message]
2005-10-21 18:13 ` Thomas Gleixner
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=1129917588.27168.215.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--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
all inboxes | Powered by JetHome®