From: Ingo Molnar <mingo@elte.hu>
To: Mark_H_Johnson@raytheon.com
Cc: Thomas Gleixner <tglx@linutronix.de>,
Florian Schmidt <mista.tapas@gmx.net>,
Lee Revell <rlrevell@joe-job.com>,
Paul Davis <paul@linuxaudiosystems.com>,
LKML <linux-kernel@vger.kernel.org>, Bill Huey <bhuey@lnxw.com>,
Adam Heath <doogie@debian.org>,
Michal Schmidt <xschmi00@stud.feec.vutbr.cz>,
Fernando Pablo Lopez-Lezcano <nando@ccrma.stanford.edu>,
Karsten Wiese <annabellesgarden@yahoo.de>,
jackit-devel <jackit-devel@lists.sourceforge.net>,
Rui Nuno Capela <rncbc@rncbc.org>, "K.R. Foley" <kr@cybsft.com>
Subject: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8
Date: Tue, 2 Nov 2004 22:09:25 +0100 [thread overview]
Message-ID: <20041102210925.GA7029@elte.hu> (raw)
In-Reply-To: <OF8F6308EA.F9FADA81-ON86256F40.0071B981-86256F40.0071B9A6@raytheon.com>
* Mark_H_Johnson@raytheon.com <Mark_H_Johnson@raytheon.com> wrote:
> >The only other way for the NMI watchdog to
> >trigger is if for whatever reason the local APIC timer interrupts are
> >not getting through and the NMI ticks (which come via a different
> >interrupt pin) get through.
>
> The other symptoms I was seeing appeared to be timer related
> - never returned from "sleep 1s" in the shell script
> - "ps -fe" worked fine, but "top" did not
> You may be on to something here.
was this already in the default bootup, or only after the crash
happened? Does this also happen if you chrt ksoftirqd to FIFO prio 1?
Does the 'LOC' count increase for both cpus in /proc/interrupts?
Ingo
next prev parent reply other threads:[~2004-11-02 21:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 20:42 [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8 Mark_H_Johnson
2004-11-02 21:09 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-02 22:35 Mark_H_Johnson
2004-11-03 8:39 ` Ingo Molnar
2004-11-03 8:42 ` Ingo Molnar
2004-11-03 10:00 ` Ingo Molnar
2004-11-03 12:39 ` Ingo Molnar
2004-11-03 19:51 ` Florian Schmidt
2004-11-03 23:02 ` Adam Heath
2004-11-02 21:39 Mark_H_Johnson
2004-11-02 18:00 Mark_H_Johnson
2004-11-02 19:18 ` Ingo Molnar
2004-11-02 19:27 ` Ingo Molnar
2004-11-02 22:04 ` K.R. Foley
2004-11-03 2:54 ` Fernando Pablo Lopez-Lezcano
2004-11-03 3:45 ` K.R. Foley
2004-11-02 15:44 Mark_H_Johnson
2004-11-02 19:38 ` Ingo Molnar
2004-11-02 19:49 ` Ingo Molnar
2004-10-31 12:54 [Fwd: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4] Lee Revell
2004-10-31 13:13 ` Ingo Molnar
2004-10-31 13:40 ` Ingo Molnar
2004-10-31 15:20 ` Florian Schmidt
2004-10-31 15:59 ` Florian Schmidt
2004-10-31 19:06 ` Florian Schmidt
2004-11-01 13:42 ` Ingo Molnar
2004-11-01 13:53 ` Ingo Molnar
2004-11-01 14:06 ` Ingo Molnar
2004-11-01 15:47 ` Thomas Gleixner
2004-11-02 15:06 ` [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8 Ingo Molnar
2004-11-02 17:52 ` K.R. Foley
2004-11-02 19:37 ` Ingo Molnar
2004-11-02 19:40 ` K.R. Foley
2004-11-02 19:24 ` Norberto Bensa
2004-11-02 19:35 ` Ingo Molnar
2004-11-02 23:09 ` Karsten Wiese
2004-11-03 1:12 ` Ingo Molnar
2004-11-03 10:15 ` Karsten Wiese
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=20041102210925.GA7029@elte.hu \
--to=mingo@elte.hu \
--cc=Mark_H_Johnson@raytheon.com \
--cc=annabellesgarden@yahoo.de \
--cc=bhuey@lnxw.com \
--cc=doogie@debian.org \
--cc=jackit-devel@lists.sourceforge.net \
--cc=kr@cybsft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mista.tapas@gmx.net \
--cc=nando@ccrma.stanford.edu \
--cc=paul@linuxaudiosystems.com \
--cc=rlrevell@joe-job.com \
--cc=rncbc@rncbc.org \
--cc=tglx@linutronix.de \
--cc=xschmi00@stud.feec.vutbr.cz \
/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