Kernel panic - not syncing

Kernel panic - not syncing

[Michael D. Berger]

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 

RE: Kernel panic - not syncing

[Gary W. Smith]

Michael, 

This may or may not help but I know there were some spinlock issues
prior to the RHEL 4 update 2 kernels.  I don't have the links to the
patches offhand.  In my case, I ran into the spinlock bug when using
ipsec and netfilter.

Gary

> -----Original Message-----
> From: netfilter-bounces@lists.netfilter.org [mailto:netfilter-
> bounces@lists.netfilter.org] On Behalf Of Michael D. Berger
> Sent: Sunday, January 08, 2006 10:04 AM
> To: netfilter
> Subject: Kernel panic - not syncing
> 
> 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
>