netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: Andy Gospodarek <andy@greyhouse.net>,
	netdev@vger.kernel.org, bonding-devel@lists.sourceforge.net
Subject: Re: [Bonding-devel] quick help with bonding?
Date: Thu, 29 Mar 2007 17:42:54 -0600	[thread overview]
Message-ID: <460C4EFE.6030505@nortel.com> (raw)
In-Reply-To: <4074.1175207458@death>

Jay Vosburgh wrote:

> 	2.6.10 is pretty old, and there have been a number of fixes to
> the bonding ARP monitor since then, so it may be that it is simply
> misbehaving (presuming that you're running the 2.6.10 bonding driver).
> Are you in a position to test against a more recent kernel (and/or
> bonding driver)?  Does the miimon misbehave in a similar fashion?

Testing a more recent kernel is problematic.  A new bonding driver could 
be possible, assuming the code hasn't changed too much.

I just did another experiment.  Normally we boot via eth4 (which then 
becomes part of the bond  with eth5 at init time).  If I boot via eth6 
instead, it appears as though the problem doesn't show up.

Chris

  parent reply	other threads:[~2007-03-30  0:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-29 16:14 quick help with bonding? Chris Friesen
2007-03-29 16:24 ` [Bonding-devel] " Jay Vosburgh
2007-03-29 18:16 ` Andy Gospodarek
2007-03-29 22:08   ` Chris Friesen
2007-03-29 22:30     ` Jay Vosburgh
2007-03-29 23:01       ` Mark Huth
2007-03-29 23:42       ` Chris Friesen [this message]
2007-03-30  0:13         ` Jay Vosburgh
2007-03-30  0:36         ` Andy Gospodarek
2007-03-30  1:19           ` Chris Friesen
2007-03-30  1:26             ` Chris Friesen
2007-03-30  2:48               ` Andy Gospodarek
2007-03-30  2:49               ` Chris Friesen
2007-04-02 22:28 ` Chris Friesen

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=460C4EFE.6030505@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=andy@greyhouse.net \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=fubar@us.ibm.com \
    --cc=netdev@vger.kernel.org \
    /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).