All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>,
	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: Tue, 07 Apr 2015 10:17:14 -0700	[thread overview]
Message-ID: <5524111A.80408@hp.com> (raw)
In-Reply-To: <1428409685.3947287.250212889.1919258C@webmail.messagingengine.com>

On 04/07/2015 05:28 AM, Hannes Frederic Sowa wrote:
> On Tue, Apr 7, 2015, at 12:14, Hannes Frederic Sowa wrote:
>> On Tue, Apr 7, 2015, at 00:51, Rick Jones wrote:
>>> The git bisect has implicated:
>>>
>>> b6a7719aedd7e5c0f2df7641aa47386111682df4 is the first bad commit
>>> commit b6a7719aedd7e5c0f2df7641aa47386111682df4
>>> Author: Hannes Frederic Sowa <hannes@stressinduktion.org>
>>> Date:   Wed Mar 25 17:07:44 2015 +0100
>>
>> Thanks for the report, I try to reproduce this right now!
>
> Rick, can you send me more details on your setup? I am not able to
> reproduce it here, I am able to send a lot of fragments via vxlan
> interfaces here.

Pair of HP Sl230s Gen8 systems with HP 560FLR 10GbE NICs (Intel
82599ES) connected to an HP 5900 series switch running Comware 7.11.035, 
Release 2208P01.  On one side I have a 3.14.mumble kernel (which was 
also the source of the config file used to build the upstream kernels). 
  On the other side I have the test kernels from davem's net-next tree. 
  I create the vxlan0 interface using:

  ip li add vxlan0 type vxlan id 42 group 239.1.1.1 dev eth2 dstport 4789

Which is taken almost verbatim from Documentation/networking/vxlan.txt
and then I assign an IP address to the interface with ifconfig.  Then I 
ping the other system (which I have setup vxlan similarly) and before I 
even see ping report one reply, the system ceases to respond via the 
network or console.

I suspect my present mail client would munge it as inline so I'll send 
you a copy of the config file as a direct email with an attachment.

rick

      reply	other threads:[~2015-04-07 17:17 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
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 [this message]

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=5524111A.80408@hp.com \
    --to=rick.jones2@hp.com \
    --cc=hannes@stressinduktion.org \
    --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.