netdev
[Top] [All Lists]

Re: Fw: [Bugme-new] [Bug 3746] New: Bridge causes machine lockups

To: MichaÅ Margula <alchemyx@xxxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxx>
Subject: Re: Fw: [Bugme-new] [Bug 3746] New: Bridge causes machine lockups
From: Bart De Schuymer <bdschuym@xxxxxxxxxx>
Date: Sun, 21 Nov 2004 17:27:43 +0100
Cc: netdev@xxxxxxxxxxx
In-reply-to: <419C8724.20006@uznam.net.pl>
References: <20041115122046.1413527e.akpm@osdl.org> <20041115124843.4c3dd72f.akpm@osdl.org> <419C8724.20006@uznam.net.pl>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: KMail/1.5
On Thursday 18 November 2004 12:27, MichaÅ Margula wrote:
> >Bart De Schuymer <bdschuym@xxxxxxxxxx> wrote:
> >>>Problem is present in 2.6.8.1 and 2.6.9 kernels. There was no such
> >>> problem on 2.4.26.
> >>
> >>Can you do something similar with iptables rules to see if it's specific
> >> to ebtables (which I doubt)?
>
> Over 50 hours after converting rules from ebtables to iptables and still
> no lockup. Everything is fine and I am sure it will go stable for days
> (as mentioned before lockup with ebtables happens in less than 24 hours).

The only thing I can come up with is that your packets are coming in so fast 
that the ebtables user context code cannot get the write_lock_bh.
Please apply the attached patch to be sure it hangs on the write_lock_bh, by 
doing
# cd /usr/src/linux-2.6.9/
# patch -p1 < patch
When your system hangs again, the message "EBTABLES: BEFORE WRITE LOCK"
should be in your syslog, and check that it is not followed by "EBTABLES: 
AFTER WRITE LOCK".

Is the bridge still forwarding packets while it hangs?

Perhaps try to link all network traffic to one cpu before doing your ebtables 
updates...
I strongly doubt there is a deadlock hidden in the ebtables code. Perhaps 
other people on this list can throw in possibilities...

cheers,
Bart

Attachment: patch
Description: Text Data

<Prev in Thread] Current Thread [Next in Thread>