From: Nathan Grennan <ngrennan@willowgarage.com>
To: linux-rt-users@vger.kernel.org
Subject: Soft lock issue with 2.6.33.7-rt29
Date: Wed, 17 Nov 2010 11:11:07 -0800 [thread overview]
Message-ID: <4CE428CB.20808@willowgarage.com> (raw)
I have been working for weeks to get a stable rt kernel. I had been
focusing on 2.6.31.6-rt19. It is stable for about four days under stress
testing before it soft locks. I am using rt19 instead of rt21, because
rt19 seems to be more stable. The rtmutex issue that seems to still be
in rt29 is in rt21. I also had to backport the iptables fix to rt19.
I just started looking at 2.6.33.7-rt29 again, since I can reproduce
a soft lock with it in 10-15 minutes. I have yet to get sysrq output for
rt19, since it takes four days. The soft lock with rt29 as far as I can
tell seems to relate to disk i/o.
There are links to two logs of rt29 from a serial console below.
They include sysrq output like "Show Blocked State" and "Show State".
The level7 file is with nfsd enable, and level9 is with it disable. So
nfsd doesn't seem to be the issue.
If any other debugging information is useful or needed, just say the
word.
http://proton.cygnusx-1.org/~edgan/kernel-logs/kernel-2.6.33-rt29.level7.log
http://proton.cygnusx-1.org/~edgan/kernel-logs/kernel-2.6.33-rt29.level9.log
next reply other threads:[~2010-11-17 19:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 19:11 Nathan Grennan [this message]
2010-11-18 1:26 ` Soft lock issue with 2.6.33.7-rt29 Darren Hart
2010-11-18 11:35 ` Luis Claudio R. Goncalves
2010-11-18 17:48 ` Nathan Grennan
2010-11-18 22:11 ` Nathan Grennan
2010-11-19 12:05 ` Locating processes impacting my rt application Leggo, Adam (UK)
2010-11-19 14:53 ` Uwe Kleine-König
2010-11-19 15:11 ` Husak, Jan
2010-11-19 18:46 ` Soft lock issue with 2.6.33.7-rt29 Darren Hart
2010-11-19 19:21 ` Nathan Grennan
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=4CE428CB.20808@willowgarage.com \
--to=ngrennan@willowgarage.com \
--cc=linux-rt-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).