From: Rick Jones <rick.jones2@hp.com>
To: Marcelo Ricardo Leitner <mleitner@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: VxLAN system wedge in 4.0.0-rc5+ from davem net-next?
Date: Mon, 06 Apr 2015 13:00:53 -0700 [thread overview]
Message-ID: <5522E5F5.7050605@hp.com> (raw)
In-Reply-To: <20150406190743.GA3969@localhost.localdomain>
On 04/06/2015 12:07 PM, Marcelo Ricardo Leitner wrote:
> Hi,
>
> On Fri, Apr 03, 2015 at 05:11:12PM -0700, Rick Jones wrote:
>> Hi -
>>
>> I've been messing about with VxLAN with a pair of two socket systems with
>> ixgbe-driven NICs (HP 560FLRs for the curious) and have noticed that with a
>> kernel from a davem net-next tree I refreshed a couple days ago I can create
>> the vlxan link, and ifconfig it, but once I start trying to push packets
>> through it the system appears to hang and I have to reset it.
>>
>> I went back to checkout v3.19 and tried that kernel and all was happiness
>> and joy. So, I started down the bisect path, but after the first iteration
>> I ran into:
>
> That means you could send/receive some packets on it before the hang, right?
On v3.19 I could send and receive lots of packets without a hang. I
could even run netperf through the vxlan tunnel :)
Now that I've addressed my build issue I'm in the midst of a bisect, but
if someone has faster git-fu I'll not be disappointed if they are able
to bisect before me.
rick
next prev parent reply other threads:[~2015-04-06 20:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-04 0:11 VxLAN system wedge in 4.0.0-rc5+ from davem net-next? Rick Jones
2015-04-06 17:32 ` Rick Jones
2015-04-06 19:07 ` Marcelo Ricardo Leitner
2015-04-06 20:00 ` Rick Jones [this message]
2015-04-06 22:51 ` Rick Jones
2015-04-07 10:14 ` Hannes Frederic Sowa
2015-04-07 12:28 ` Hannes Frederic Sowa
2015-04-07 17:17 ` Rick Jones
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=5522E5F5.7050605@hp.com \
--to=rick.jones2@hp.com \
--cc=mleitner@redhat.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 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.