netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: netdev@vger.kernel.org
Subject: VxLAN system wedge in 4.0.0-rc5+ from davem net-next?
Date: Fri, 03 Apr 2015 17:11:12 -0700	[thread overview]
Message-ID: <551F2C20.1060908@hp.com> (raw)

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:

   INSTALL debian/headertmp/usr/include/asm/ (65 files)
parsechangelog/debian: warning:     debian/changelog(l2): found eof 
where expected first heading
parsechangelog/debian: error: fatal error occurred while parsing 
debian/changelog
dpkg-gencontrol: error: changelog parser 
/usr/lib/dpkg/parsechangelog/debian gave error exit status 255
scripts/package/Makefile:90: recipe for target 'deb-pkg' failed
make[1]: *** [deb-pkg] Error 255
Makefile:1238: recipe for target 'deb-pkg' failed
make: *** [deb-pkg] Error 2

Which I'm afraid goes beyond my knowledge of how to deal.  Does any of 
that - either the VxLAN or the build problem - sound familiar?

thanks,

rick jones

             reply	other threads:[~2015-04-04  0:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-04  0:11 Rick Jones [this message]
2015-04-06 17:32 ` VxLAN system wedge in 4.0.0-rc5+ from davem net-next? 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

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=551F2C20.1060908@hp.com \
    --to=rick.jones2@hp.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 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).