From: Steven Rostedt <rostedt@goodmis.org>
To: george@mvista.com
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
john stultz <johnstul@us.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.14-rc5-rt6 -- False NMI lockup detects
Date: Tue, 25 Oct 2005 16:10:50 -0400 [thread overview]
Message-ID: <1130271050.21118.30.camel@localhost.localdomain> (raw)
In-Reply-To: <435E8EDE.30306@mvista.com>
On Tue, 2005-10-25 at 13:00 -0700, George Anzinger wrote:
> Steven Rostedt wrote:
> >
> >
> > Isn't the jiffy tick implemented with the PIT when possible? So the apic
> > is only used when a timer is needed. Also note that this "lockup"
> > happens on boot up while things are being initialized, so not many
> > things may be using the timer.
>
> Somewhere in the not too distant past the NMI watchdog was moved from the PIT tick to the APIC
> timer. Might want to move it back, at least for now...
> >
Actually, I submitted a patch to Ingo, (and I guess it would also work
with Thomas' kthrt as well), that takes the nmi tick out of the timer
code completely (at least for x86) and moves it to the __do_IRQ. This
way, it would detect when something is locked up with interrupts
disabled, but you don't worry about having the right timer configured
for it.
If you want to detect the timer being screwed up, that can be done on a
timer by timer basis, and most likely the soft lockup would find that
out too.
-- Steve
next prev parent reply other threads:[~2005-10-25 20:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 14:23 2.6.14-rc5-rt6 -- False NMI lockup detects Steven Rostedt
2005-10-25 14:28 ` Ingo Molnar
2005-10-25 19:24 ` Steven Rostedt
2005-10-25 19:40 ` Thomas Gleixner
2005-10-25 20:00 ` George Anzinger
2005-10-25 20:10 ` Steven Rostedt [this message]
2005-10-26 11:27 ` Steven Rostedt
2005-11-01 11:33 ` Ingo Molnar
2005-11-01 17:41 ` 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=1130271050.21118.30.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=george@mvista.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.