On Thursday 18 November 2004 12:27, MichaÅ Margula wrote:
> >Bart De Schuymer <bdschuym@xxxxxxxxxx> wrote:
> >>>Problem is present in 220.127.116.11 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
# 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
I strongly doubt there is a deadlock hidden in the ebtables code. Perhaps
other people on this list can throw in possibilities...
Description: Text Data