From: Chris Chabot <chabotc@reviewboard.com>
To: tadavis@lbl.gov, linux-kernel@vger.kernel.org
Subject: Bonding driver
Date: Fri, 09 Feb 2001 14:27:38 +0100 [thread overview]
Message-ID: <3A83F04A.7182E3E1@reviewboard.com> (raw)
A few bugs still show up in the 2.4.x series with the bonding
(drivers/net/bonding.c / bonding.0) driver. Ive tried all the below
situations in both 2.4.0 and 2.4.1 (both clean/final versions), and on
redhat's default 2.2.16enterprise kernel. the 2.2.16 kernel doesnt have
any of the bugs described below, so it seems they are newly introduced
in the 2.4 series at some point.. The system im testing on is a dual p3
600 (asus p2b-ds mainboard, 440 chipset), 512Mb ecc ram, raid0 4xide
disks, 2x 3com 3c905b network cards connected to a 3com superstack III
switch. The system runs redhat 7.0 with a clean self compiled 2.4.0/1
kernel.
Things that go wrong..
<BUG>
ifdown bond0
ifdown eth0
--> kernel oops, system hard crash
system shutdown does the above as well, so as result i cant normaly shut
down my servers anymore. This is very anoying for my fsck's on the 300Gb
raid0.. and i fear for my data :)
<BUG>
ping <some-addr>
ifconfig
--> packets go over the 2 interfaces
ifdown bond0
ifup bond0
ping <same-addr>
--> packets go -only- over eth0
<BEHAVIOUR>
ping -f <some-addr>
ifconfig
--> bond0 shows 0 rx packets, while eth0/1 do show rx's being
distributed over the 2 interfaces.
If there's more information i can provide, dont hesitate to ask. Pls cc
me in replies since im not subscribed to linux-kernel.
-- Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-02-09 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-09 13:27 Chris Chabot [this message]
2004-08-17 20:22 Bloch, Jack
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=3A83F04A.7182E3E1@reviewboard.com \
--to=chabotc@reviewboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tadavis@lbl.gov \
/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
all inboxes | Powered by JetHome®