From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Chris Stromsoe <cbs@cts.ucla.edu>
Cc: netdev@vger.kernel.org
Subject: Re: skge- "soft lockup on CPU#0" with mtu=9000 (2.6.20.1 + web100 patch)
Date: Thu, 8 Mar 2007 13:48:11 -0800 [thread overview]
Message-ID: <20070308134811.38a8ec81@freekitty> (raw)
In-Reply-To: <Pine.LNX.4.64.0703081256440.25051@potato.cts.ucla.edu>
On Thu, 8 Mar 2007 13:31:13 -0800 (PST)
Chris Stromsoe <cbs@cts.ucla.edu> wrote:
> Thanks. That fixes the soft lockup.
>
> I've got another problem now. The cards I'm using are dual port
> (sk-9844). I am bonding both ports together.
>
> The card presents as eth2 and eth3. If I remove eth2 from the bond so
> that eth3 is the active interface, I get a hard lock (nothing prints to
> serial console, sysrq isn't responsive) and have to power cycle.
>
> This is with plain 2.6.20.1. I also tested using skge.[ch] from the
> current netdev git tree.
Which form of bonding failover, there are locking issues with some
of the bonding modes. You should ask on the bonding mailing list.
--
Stephen Hemminger <shemminger@linux-foundation.org>
next prev parent reply other threads:[~2007-03-08 21:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 19:20 skge- "soft lockup on CPU#0" with mtu=9000 (2.6.20.1 + web100 patch) Chris Stromsoe
2007-03-08 19:34 ` Stephen Hemminger
2007-03-08 21:31 ` Chris Stromsoe
2007-03-08 21:48 ` Stephen Hemminger [this message]
2007-03-08 22:23 ` Chris Stromsoe
2007-03-08 23:04 ` Jay Vosburgh
2007-03-08 23:13 ` Chris Stromsoe
2007-03-12 22:09 ` Chris Stromsoe
2007-03-12 22:16 ` [PATCH] skge: set mac address bonding fix Stephen Hemminger
2007-03-12 22:39 ` Chris Stromsoe
2007-03-12 23:18 ` Stephen Hemminger
2007-03-13 0:37 ` Chris Stromsoe
2007-03-15 14:35 ` Jeff Garzik
2007-05-08 22:28 ` skge- "soft lockup on CPU#0" with mtu=9000 (2.6.20.1 + web100 patch) Chris Stromsoe
2007-05-09 0:06 ` Chris Stromsoe
2007-03-08 21:37 ` 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=20070308134811.38a8ec81@freekitty \
--to=shemminger@linux-foundation.org \
--cc=cbs@cts.ucla.edu \
--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).