From: "Michael D. Berger" <m.d.berger@ieee.org>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Kernel panic - not syncing
Date: Sun, 8 Jan 2006 13:03:59 -0500 [thread overview]
Message-ID: <000101c6147d$e9affc10$2801a8c0@MBRC40> (raw)
I reported this problem previously on redhat-list@redhat.com
possibly in relation to the leap second. We see now that the
leap second may have been coincidental.
I am running a rather complex libipq daemon, which may be
related to this.
I am also running tethereal in the background on this box.
I note that while previously the failure occurred on two
boxes, in this case, only one box failed.
I am considering upgrading to the latest fedora.
On:
Red Hat Enterprise Linux WS release 4(Nahant)
Kernel 2.6.9-5.EL on an i686
I get:
Kernel panic - not syncing: net/ipv4/tcp_timer.c:yyy:
spin_lock(net/ipv4/tcp_minisocks.c:xxxxxxxx) already locked by
net/ipv4/tcp_ipv4.c/1790
previous now
yyy 211 422
xxxxxxxx f5fee080 f62db080
Suggestions would be much appreciated.
Mike.
--
Michael D. Berger
m.d.berger@ieee.org
next reply other threads:[~2006-01-08 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-08 18:03 Michael D. Berger [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-08 18:14 Kernel panic - not syncing Gary W. Smith
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='000101c6147d$e9affc10$2801a8c0@MBRC40' \
--to=m.d.berger@ieee.org \
--cc=netfilter@lists.netfilter.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