From: Andrew Morton <akpm@osdl.org>
To: netdev@oss.sgi.com
Subject: Fw: [Bugme-new] [Bug 3746] New: Bridge causes machine lockups
Date: Mon, 15 Nov 2004 12:20:46 -0800 [thread overview]
Message-ID: <20041115122046.1413527e.akpm@osdl.org> (raw)
Begin forwarded message:
Date: Mon, 15 Nov 2004 04:33:51 -0800
From: bugme-daemon@osdl.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 3746] New: Bridge causes machine lockups
http://bugme.osdl.org/show_bug.cgi?id=3746
Summary: Bridge causes machine lockups
Kernel Version: 2.6.9
Status: NEW
Severity: high
Owner: acme@conectiva.com.br
Submitter: alchemyx@uznam.net.pl
Distribution: Gentoo 2004.2 with vanilla kernel sources
Hardware Environment: 2 x Xeon 2.80 GHz, 1GB RAM, 4 x e1000 NIC, 2 x e100 NIC
Software Environment: bridge-utils-0.9.6, bridged 2x e100 and 3x e1000
Problem Description:
On my Linux box I have few scripts that modify entries in ebtables filtering
chains. I have main chain called BLOCKED and in FORWARD chain I have entry "-j
BLOCKED", which directs every bridged packet to BLOCKED chain. Blocked chain
consists of entries:
-s SO:ME:MA:CA:DD:R0 -j DROP
-d SO:ME:MA:CA:DD:R0 -j DROP
[... about 50 of them ...]
-j RETURN
It works fine. About twenty or thirty times a day, a script does 'iptables -F
BLOCKED' and writes new entries into chain BLOCKED. Problem is that machine dies
from time to time (under heavy network load it happens once a day). It just
locks, nothing happenes, no oopses, or entries in logs. Then after 60 seconds,
watchdog from Intel motherboard resets machine.
Also I was doing some changes manually into chains and noticed that machine died
after I have issued 'ebtables -F BLOCKED' (clearing the chain). Once again after
60 seconds watchdog reset machine.
Problem is present in 2.6.8.1 and 2.6.9 kernels. There was no such problem on
2.4.26.
The only weird thing I noticed is when I initalise my bridge, is something about
that it can't get speed of some interfaces (guessing it is about e1000). I can't
give you full error message at the moment, because those have been rotated by
logrotate.
Steps to reproduce:
1. Set up a bridge consisting of few devices and having chains as described in
"Problem description"
2. Use high flow trough those devices (at least 50 megabits per second cumulative).
3. Change chain BLOCKED few tens of time a day.
4. Wait for lockup.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2004-11-15 20:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 20:20 Andrew Morton [this message]
2004-11-15 20:46 ` Fw: [Bugme-new] [Bug 3746] New: Bridge causes machine lockups Bart De Schuymer
2004-11-15 20:48 ` Andrew Morton
2004-11-15 21:57 ` Michał Margula
2004-11-16 10:16 ` Michał Margula
2004-11-18 11:27 ` Michał Margula
2004-11-18 19:59 ` Bart De Schuymer
2004-11-21 16:27 ` Bart De Schuymer
2004-11-21 22:21 ` Michał Margula
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041115122046.1413527e.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).