From: Ingo Molnar <mingo@elte.hu>
To: Mark_H_Johnson@raytheon.com
Cc: Rui Nuno Capela <rncbc@rncbc.org>,
linux-kernel@vger.kernel.org, Lee Revell <rlrevell@joe-job.com>,
"K.R. Foley" <kr@cybsft.com>, Bill Huey <bhuey@lnxw.com>,
Adam Heath <doogie@debian.org>,
Florian Schmidt <mista.tapas@gmx.net>,
Thomas Gleixner <tglx@linutronix.de>,
Michal Schmidt <xschmi00@stud.feec.vutbr.cz>,
Fernando Pablo Lopez-Lezcano <nando@ccrma.stanford.edu>,
Karsten Wiese <annabellesgarden@yahoo.de>
Subject: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.5.2
Date: Fri, 29 Oct 2004 18:26:22 +0200 [thread overview]
Message-ID: <20041029162622.GA8016@elte.hu> (raw)
In-Reply-To: <OFDD5E88CA.56DEE781-ON86256F3C.0059C080-86256F3C.0059C0A2@raytheon.com>
* Mark_H_Johnson@raytheon.com <Mark_H_Johnson@raytheon.com> wrote:
> The critical section nesting was "unique" and looks like
>
> | preempt count: 00010005 ]
> | 5-level deep critical section nesting:
> ----------------------------------------
> .. [<c03257cf>] .... _spin_lock+0x1f/0x70
> .....[<c01e217a>] .. ( <= __up_write+0x26a/0x2a0)
> .. [<c03257cf>] .... _spin_lock+0x1f/0x70
> .....[<c01e1f65>] .. ( <= __up_write+0x55/0x2a0)
> .. [<c0325817>] .... _spin_lock+0x67/0x70
> .....[<c011b54d>] .. ( <= task_rq_lock+0x3d/0x70)
> .. [<c03257cf>] .... _spin_lock+0x1f/0x70
> .....[<c0115f47>] .. ( <= nmi_watchdog_tick+0x127/0x140)
> .. [<c013d5bd>] .... print_traces+0x1d/0x60
> .....[<c0105bec>] .. ( <= show_regs+0x14c/0x174)
this might as well have been the NMI watchdog interacting. Could you
turn off the NMI watchdog to see whether that stabilizes things?
> The script then exits with preempt count of 3 and an atomic counter
> underflow BUG message. This is followed right after with
>
> BUG: Unable to handle kernel NULL pointer dereference at virtual address
> 00000
> 020
these are then probably just followup-errors. Will take a look at the
logs.
Ingo
next prev parent reply other threads:[~2004-10-29 16:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 16:20 [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.5.2 Mark_H_Johnson
2004-10-29 16:26 ` Ingo Molnar [this message]
2004-10-29 17:52 ` John Gilbert
2004-10-29 20:30 ` Ingo Molnar
2004-10-29 20:41 ` Lee Revell
-- strict thread matches above, loose matches on Subject: below --
2004-10-28 15:02 Mark_H_Johnson
2004-10-28 18:38 ` Ingo Molnar
2004-10-27 13:53 [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.3 Ingo Molnar
2004-10-27 15:26 ` [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4 Rui Nuno Capela
2004-10-27 20:51 ` Ingo Molnar
2004-10-27 21:19 ` Ingo Molnar
2004-10-27 23:31 ` Rui Nuno Capela
2004-10-28 6:36 ` Ingo Molnar
2004-10-28 8:31 ` Rui Nuno Capela
2004-10-28 8:56 ` Ingo Molnar
2004-10-28 9:17 ` Rui Nuno Capela
2004-10-28 9:32 ` Ingo Molnar
2004-10-28 13:57 ` [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.5.2 Ingo Molnar
2004-10-28 14:10 ` DaMouse
2004-10-28 14:18 ` 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=20041029162622.GA8016@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=kr@cybsft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mista.tapas@gmx.net \
--cc=nando@ccrma.stanford.edu \
--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;
as well as URLs for NNTP newsgroup(s).