From: Mark_H_Johnson@raytheon.com
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@osdl.org>,
Andrew Rodland <arodland@entermail.net>,
Bill Huey <bhuey@lnxw.com>, Adam Heath <doogie@debian.org>,
Daniel Walker <dwalker@mvista.com>, "K.R. Foley" <kr@cybsft.com>,
linux-kernel@vger.kernel.org,
Lorenzo Allegrucci <l_allegrucci@yahoo.it>,
Lee Revell <rlrevell@joe-job.com>,
Rui Nuno Capela <rncbc@rncbc.org>
Subject: Re: [patch] Real-Time Preemption, -VP-2.6.9-rc4-mm1-U3
Date: Fri, 15 Oct 2004 11:56:20 -0500 [thread overview]
Message-ID: <OFB6EC1D35.D97E8854-ON86256F2E.005B1743@raytheon.com> (raw)
>i have released the -U3 PREEMPT_REALTIME patch:
>
>
http://redhat.com/~mingo/voluntary-preempt/voluntary-preempt-2.6.9-rc4-mm1-U3
>
Built without any problems, booted as single user and had no errors until I
started running init scripts.
First attempt - When I got to S10network start, had a couple
messages displayed about sleeping in invalid contexts (scrolled by too
fast).
It ended with a kernel bug, looked similar to what I reported before. The
new data displayed included:
preempt count: 4
entry 1: schedule+0x46/0x810 / (ksoftirqd+0xd4/0xf0)
entry 2: _spin_lock_irqsave+0x1f/0x80 / (schedule+0x108/0x810)
entry 3: _spin_lock+0x67/0x70 / (load_balance_newidle+0x66/0xc0)
entry 4: _spin_lock+0x67/0x70 / (die_nmi+0x1b/0xa0)
System locked up, hardware reset to reboot. After reboot, noticed
I did capture some data, will send that separately.
Second attempt - basically the same symptom. The kernel BUG output was
incomplete with a "preempt count: 4" but only one entry displayed
(same as entry 1 above).
System locked up, hardware reset to reboot. Will boot with max_cpus=1
to see if I get farther.
Third attempt - had two outputs of tracing data while starting the
network interface. Tried a couple ping commands with numeric destinations
and the machine had no response (displayed) on the first one, Ctrl-C to
abort. On the second try, the system responded the same until I hit Ctrl-C,
no response. Alt-SysRq-T did display task data, ping was in D mode, and
call trace was pretty deep. Thought it was somewhat odd that it (and
several
tasks above it) had a preempt count:1 with
entry 1: _spin_lock+0x1f/0x70 / (__handle_sysrq+0x1f/0xf0)
not sure if that is the expected behavior or not.
Alt-SysRq-S had the same traceback as I reported before. Rebooted with
Alt-SysRq-B.
As mentioned before, will send the system log data in a separate
message.
--Mark H Johnson
<mailto:Mark_H_Johnson@raytheon.com>
next reply other threads:[~2004-10-15 16:59 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 16:56 Mark_H_Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-11 18:23 [patch] CONFIG_PREEMPT_REALTIME, 'Fully Preemptible Kernel', VP-2.6.9-rc4-mm1-T4 Mark_H_Johnson
2004-10-11 21:59 ` [patch] VP-2.6.9-rc4-mm1-T5 Ingo Molnar
2004-10-12 9:15 ` [patch] VP-2.6.9-rc4-mm1-T6 Ingo Molnar
2004-10-12 12:33 ` Ingo Molnar
2004-10-12 19:54 ` [patch] VP-2.6.9-rc4-mm1-T8 Ingo Molnar
2004-10-13 6:15 ` [patch] VP-2.6.9-rc4-mm1-T9 Ingo Molnar
2004-10-14 0:24 ` [patch] Real-Time Preemption, -VP-2.6.9-rc4-mm1-U0 Ingo Molnar
2004-10-14 14:31 ` [patch] Real-Time Preemption, -VP-2.6.9-rc4-mm1-U1 Ingo Molnar
2004-10-14 23:42 ` [patch] Real-Time Preemption, -VP-2.6.9-rc4-mm1-U2 Ingo Molnar
2004-10-15 10:26 ` [patch] Real-Time Preemption, -VP-2.6.9-rc4-mm1-U3 Ingo Molnar
2004-10-15 11:59 ` Dominik Karall
2004-10-15 12:03 ` Ingo Molnar
2004-10-15 16:48 ` Lee Revell
2004-10-15 17:40 ` Adam Heath
2004-10-15 17:54 ` K.R. Foley
2004-10-15 18:16 ` K.R. Foley
2004-10-15 20:29 ` Gunther Persoons
2004-10-15 23:16 ` Bill Huey
2004-10-16 0:21 ` Bill Huey
2004-10-16 6:48 ` Ingo Molnar
2004-10-16 1:00 ` Lee Revell
2004-10-16 2:35 ` Lee Revell
2004-10-16 6:42 ` Ingo Molnar
2004-10-16 9:02 ` Lee Revell
2004-10-16 10:36 ` Ingo Molnar
2004-10-16 11:03 ` Rui Nuno Capela
2004-10-16 11:12 ` Ingo Molnar
2004-10-16 11:55 ` Rui Nuno Capela
2004-10-16 12:01 ` Ingo Molnar
2004-10-16 12:32 ` K.R. Foley
2004-10-17 13:14 ` Rui Nuno Capela
2004-10-17 13:21 ` Ingo Molnar
[not found] ` <32793.192.168.1.5.1098023139.squirrel@192.168.1.5>
2004-10-17 16:12 ` Ingo Molnar
2004-10-17 17:20 ` Rui Nuno Capela
2004-10-17 17:27 ` Ingo Molnar
2004-10-17 16:47 ` Ingo Molnar
2004-10-17 19:05 ` Rui Nuno Capela
2004-10-17 19:24 ` Ingo Molnar
2004-10-17 20:23 ` Rui Nuno Capela
2004-10-16 10:29 ` Rui Nuno Capela
2004-10-16 12:54 ` K.R. Foley
2004-10-16 13:04 ` Ingo Molnar
2004-10-16 13:07 ` K.R. Foley
2004-10-16 13:41 ` Rui Nuno Capela
2004-10-16 13:55 ` K.R. Foley
2004-10-16 2:58 ` Adam Heath
2004-10-16 7:56 ` Ingo Molnar
2004-10-16 8:18 ` Ingo Molnar
2004-10-16 18:38 ` Adam Heath
2004-10-16 6:13 ` Lee Revell
2004-10-16 14:21 ` Dominik Karall
2004-10-16 15:24 ` Ingo Molnar
2004-10-16 20:30 ` Dominik Karall
2004-10-16 20:31 ` Lee Revell
2004-10-16 21:44 ` Dominik Karall
2004-10-17 5:21 ` Ingo Molnar
2004-10-17 15:32 ` OGAWA Hirofumi
2004-10-17 17:46 ` Dominik Karall
2004-10-18 3:50 ` OGAWA Hirofumi
2004-10-21 10:24 ` Dominik Karall
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=OFB6EC1D35.D97E8854-ON86256F2E.005B1743@raytheon.com \
--to=mark_h_johnson@raytheon.com \
--cc=akpm@osdl.org \
--cc=arodland@entermail.net \
--cc=bhuey@lnxw.com \
--cc=doogie@debian.org \
--cc=dwalker@mvista.com \
--cc=kr@cybsft.com \
--cc=l_allegrucci@yahoo.it \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rlrevell@joe-job.com \
--cc=rncbc@rncbc.org \
/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®