LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Vincent ETIENNE <ve@vetienne.net>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: Chris Snook <csnook@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
bonding-devel@lists.sourceforge.net,
"Andy Gospodarek" <andy@greyhouse.net>
Subject: Re: [Bonding-devel] [PROBLEM] Bonding driver in linux-2.6.21-rc6-mm1
Date: Thu, 26 Apr 2007 23:43:48 +0200 [thread overview]
Message-ID: <200704262343.49666.ve@vetienne.net> (raw)
In-Reply-To: <1791.1177620299@death>
Le Thursday 26 April 2007 22:44:59 Jay Vosburgh, vous avez écrit :
> Chris Snook <csnook@redhat.com> wrote:
> >Vincent ETIENNE wrote:
> >> Hi,
> >>
> >> Summary :
> >> Got this trace when one network interface come down or up in a 2
> >> interfaces bonding. So far, system seems to survive to this problem
> >> and works fine.
> >
> >I'm investigating a similar/possibly identical bug. Do you experience
> >packet loss or throughput stalls, beyond just the loss of the interface
> >that went down, when this happens?
>
> This problem looks to be one of the known locking issues with
> bonding.
>
> Andy Gospodarek <andy@greyhouse.net> and I have been working
> offline on the locking issues in bonding over the last several weeks.
> At the moment, we have a generally stable (but ugly with debug fluff and
> other yuckies) patch that seems to resolve at least the majority of the
> various issues. I'm thinking to clean it up for general posting early
> next week, and address additional problems from there (since it's
> hopefully at least a big step forward).
>
> -J
>
> ---
> -Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
Will be more than happy to test it and report the result with the new patch.
Thanks for your work,
next prev parent reply other threads:[~2007-04-26 21:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 18:58 Vincent ETIENNE
2007-04-26 20:27 ` Chris Snook
2007-04-26 20:44 ` [Bonding-devel] " Jay Vosburgh
2007-04-26 21:43 ` Vincent ETIENNE [this message]
2007-05-09 18:47 ` Vincent ETIENNE
2007-04-27 4:11 ` Andrew Morton
2007-04-27 9:25 ` VE (HOME)
2007-04-27 19:20 ` Andrew Morton
2007-04-27 21:18 ` USB HID bug (was [PROBLEM] Bonding driver in linux-2.6.21-rc6-mm1) Greg KH
2007-04-27 22:42 ` Jiri Kosina
2007-04-27 22:55 ` Jiri Kosina
2007-04-27 23:24 ` Paul Walmsley
2007-04-28 7:21 ` Vincent ETIENNE
2007-04-28 14:07 ` Paul Walmsley
2007-04-28 15:06 ` Jiri Kosina
2007-04-28 19:50 ` [linux-usb-devel] " Alan Stern
2007-04-28 20:43 ` Vincent ETIENNE
2007-04-29 11:18 ` Jiri Kosina
2007-04-29 13:40 ` Vincent ETIENNE
[not found] ` <200704272205.29131.ve@vetienne.net>
[not found] ` <20070427153237.03f3b59c.akpm@linux-foundation.org>
2007-04-28 21:10 ` [PROBLEM] Bonding driver in linux-2.6.21-rc6-mm1 Vincent ETIENNE
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=200704262343.49666.ve@vetienne.net \
--to=ve@vetienne.net \
--cc=andy@greyhouse.net \
--cc=bonding-devel@lists.sourceforge.net \
--cc=csnook@redhat.com \
--cc=fubar@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [Bonding-devel] [PROBLEM] Bonding driver in linux-2.6.21-rc6-mm1' \
/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
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).