From: Thomas Gleixner <tglx@linutronix.de>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: john stultz <johnstul@us.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Nick Piggin <npiggin@suse.de>
Subject: Re: 2.6.33.6-rt26: oops (network related?)
Date: Mon, 2 Aug 2010 09:50:55 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1008020940090.9198@localhost.localdomain> (raw)
In-Reply-To: <1280602902.11380.6.camel@localhost.localdomain>
On Sat, 31 Jul 2010, Fernando Lopez-Lezcano wrote:
> On Thu, 2010-07-29 at 20:30 -0700, Fernando Lopez-Lezcano wrote:
> > Hi all...
> > This may not be rt related but here it goes anyway. It happened when I
> > tried to restart my iptables service (/sbin/service iptables start). I
> > think a day or two ago I had another network related hang, but it was a
> > complete hang (no clues left behind - power button to reset).
>
> Ok this one is rt related (apparently). The workstation (4 core, intel
> based) hang hard while a process was starting a daily backup but the
> logs captured the BUG:
>
> --------
> Jul 31 06:48:35 localhost kernel: ------------[ cut here ]------------
> Jul 31 06:48:35 localhost kernel: kernel BUG at kernel/rtmutex.c:808!
Weird, line 808 is a comment. The BUG_ON in rt_spin_lock_slowlock() is
at line 831.
> Jul 31 06:48:35 localhost kernel: [<c0792332>] ? rt_spin_lock+0x8/0xa
> Jul 31 06:48:35 localhost kernel: [<c075f896>] ? ipt_do_table+0xce/0x4f0
Yeah, that's the iptables locking problem, which is fixed in rt27.
Thanks,
tglx
next prev parent reply other threads:[~2010-08-02 7:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 3:30 2.6.33.6-rt26: oops Fernando Lopez-Lezcano
2010-07-31 19:01 ` 2.6.33.6-rt26: oops (network related?) Fernando Lopez-Lezcano
2010-08-01 1:55 ` Fernando Lopez-Lezcano
2010-08-02 7:50 ` Thomas Gleixner [this message]
2010-08-03 8:18 ` 2.6.33.6-rt26: oops John Kacur
2010-08-03 8:38 ` John Kacur
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=alpine.LFD.2.00.1008020940090.9198@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=nando@ccrma.Stanford.EDU \
--cc=npiggin@suse.de \
--cc=rostedt@goodmis.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).