RE: Kernel panic when routing large pings on an XScale (IXP425).

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The patch over on the RH site will fix the problem though.  My problem
also started when I changed the subnetting to cover a broader range of
subnets that also route to other locations.


> -----Original Message-----
> From: Eduardo Spremolla [mailto:edspremolla@xxxxxxxxxxxx]
> Sent: Tuesday, May 31, 2005 6:08 AM
> To: Gary W. Smith
> Cc: Cian Masterson; netfilter@xxxxxxxxxxxxxxxxxxx
> Subject: Re: Kernel panic when routing large pings on an XScale
(IXP425).
> 
> I experience the very same error just yesterday:
> KERNEL PANIC - Not Syncing: net/ipv4/xfrm4_output.c:106 : spin_lock
> (net/xfrm/xfrm_state.C : ddd2b014) already locked by
> net/ipv4/xfrm4_output.c/106
> 
> on a Fedora Core2 box running 2.6.10-1.771_FC2 kernel and
> ipsec-tools-0.5-2.fc2.
> 
> the curiosity is that this box was running ok for more than a month
with
> this policies:
> 
> spdadd 10.3.1.0/24 10.3.4.0/24 any -P in ipsec
>            esp/tunnel/CENTER_IP-MY_IP/require;
> 
> spdadd 10.3.4.0/24 10.3.1.0/24 any -P out ipsec
>            esp/tunnel/MY_IP-CENTER_IP/require;
> 
> and start to trouble when changed to :
> 
> 
> spdadd 10.0.0.0/8 10.3.4.0/24 any -P in ipsec
>            esp/tunnel/CENTER_IP-MY_IP/require;
> 
> spdadd 10.3.4.0/24 10.0.0.0/8 any -P out ipsec
>            esp/tunnel/MY_IP-CENTER_IP/require;
> 
> 
> LALO
> 
> 
> 
> On Mon, 2005-05-30 at 10:46 -0700, Gary W. Smith wrote:
> > I experienced a similar problem when I was doing some IPSEC stuff
with
> > IPTABLES under RHEL 4.  There was an issue with a TCP packet being
> locked by
> > the system and in a chain and under a certain case it would attempt
to
> lock
> > it again.  Not sure of the complete details though.
> >
> > Anyways, after talking with some people about my problem it had to
do
> with
> > locking of the chain before passing it around through other chains
for
> IPSEC
> > where it had to traverse the same table again.  It sounds similar to
my
> > problem.  Here is the link to the RedHat bug I submitted (and was
> closed)
> > some time ago.
> >
> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=154347
> >
> > It does require a kernel recompile as it's a kernel bug.
> >
> > Hope this helps.
> >
> > Gary Smith
> >



[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux