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

Bug#599816: marked as done (Kernel panic on 36 and more encapsulated GRE tunnels)

Your message dated Fri, 7 Jun 2013 20:20:06 +0200
with message-id <20130607182006.GC24112@inutil.org>
and subject line Re: Kernel panic on 36 and more encapsulated GRE tunnels
has caused the Debian Bug report #599816,
regarding Kernel panic on 36 and more encapsulated GRE tunnels
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
599816: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599816
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- Package: Debian GNU/Linux
Version: 5.0.6

When creating 36 or more GRE tunnels, with the script attached to the mail, and sending a packet, I got a kernel panic.
The last line in syslog is: “GRE over IPv4 tunneling driver”

#tunels.sh 37

%ping -I 192.168.9.1 192.168.10.1
->kernel panic


--
Béatrice Barbe
Ingénieur INSA 2010
Spécialité Réseaux Télécoms


Attachment: tunnels.sh
Description: Bourne shell script

Attachment: network-configuration.jpg
Description: JPEG image


--- End Message ---
--- Begin Message --- 
Version: 2.6.37-1

On Thu, Oct 14, 2010 at 04:29:46AM +0100, Ben Hutchings wrote:
> On Wed, 2010-10-13 at 05:02 +0100, Ben Hutchings wrote:
> > On Mon, 2010-10-11 at 16:53 +0200, Beatrice Barbe wrote:
> > > Package: Debian GNU/Linux
> > > Version: 5.0.6
> > > 
> > > When creating 36 or more GRE tunnels, with the script attached to the
> > > mail, and sending a packet, I got a kernel panic.
> > > The last line in syslog is: “GRE over IPv4 tunneling driver”
> > > 
> > > #tunels.sh 37
> > > 
> > > %ping -I 192.168.9.1 192.168.10.1
> > > ->kernel panic
> > 
> > Hmm, that's a weird bug.  I can reproduce it in Debian stable (Linux
> > 2.6.26) though it is fixed in testing (Linux 2.6.32).
> 
> > It looks like the send() call returns with a spinlock held.  I haven't
> > yet found the change between versions 2.6.26 and 2.6.32 that fixed this,
> > but I will keep looking.
> 
> In fact this has not been fixed, and I am able to reproduce it with the
> very latest version of Linux.

Fixed in 2.6.37 with 11a766ce915fc9f8663714eac6d59239388534ea

Cheers,
        Moritz

--- End Message ---
Reply to: