From: Stephen Hemminger <shemminger@osdl.org>
To: Michael Stone <mstone@mathom.us>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 4/4] skge: version 1.9
Date: Tue, 7 Nov 2006 09:51:04 -0800 [thread overview]
Message-ID: <20061107095104.734326cc@freekitty> (raw)
In-Reply-To: <20061107132506.GS2667@mathom.us>
On Tue, 07 Nov 2006 08:25:07 -0500
Michael Stone <mstone@mathom.us> wrote:
> The skge 1.9 patch is looking good on older syskonnect fiber cards.
> Stability issues seem to be taken care of and performance is good. There
> are some strange interactions with bonding, however. If I try to put
> both interfaces of an sk-9844 into a bonded interface, I only see
> traffic from one of them. If I try to config the bonded interface down,
> the system hangs. If I tcpdump either of the individual interfaces
> (before bonding them) I see all the expected traffic.
>
> Mike Stone
Which form of bonding link checking are you using. It could be that
bonding MII checking is confused.
--
Stephen Hemminger <shemminger@osdl.org>
next prev parent reply other threads:[~2006-11-07 17:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 22:49 [PATCH 0/4] skge: fiber related fixes Stephen Hemminger
2006-10-05 22:49 ` [PATCH 1/4] skge: fix stuck irq when fiber down Stephen Hemminger
2006-10-05 22:49 ` [PATCH 2/4] skge: pause mapping for fiber Stephen Hemminger
2006-10-05 22:49 ` [PATCH 3/4] skge: better flow control negotiation Stephen Hemminger
2006-10-05 22:49 ` [PATCH 4/4] skge: version 1.9 Stephen Hemminger
2006-11-07 13:25 ` Michael Stone
2006-11-07 17:51 ` Stephen Hemminger [this message]
2006-11-07 18:58 ` Michael Stone
2006-11-07 19:18 ` Stephen Hemminger
2006-11-07 19:33 ` Michael Stone
2006-11-07 20:28 ` Jay Vosburgh
2006-11-10 0:34 ` Michael Stone
2006-11-10 0:47 ` Jay Vosburgh
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=20061107095104.734326cc@freekitty \
--to=shemminger@osdl.org \
--cc=mstone@mathom.us \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.