From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Ben Greear <greearb@candelatech.com>
Cc: Hongmei Li <duckcncn@gmail.com>, netdev@vger.kernel.org
Subject: Re: IPv6 FIB related crash with MACVLANs in 3.9.11+ kernel.
Date: Mon, 29 Sep 2014 21:03:19 +0200 [thread overview]
Message-ID: <1412017399.14757.4.camel@localhost> (raw)
In-Reply-To: <5429A886.1040809@candelatech.com>
On Mo, 2014-09-29 at 11:44 -0700, Ben Greear wrote:
> On 09/29/2014 11:15 AM, Hongmei Li wrote:
> > Thanks Hannes for your prompt response!
> >
> > We just encountered this issue two times in our product stability test so far,
> > and my panic backtrace is the exactly same with the one reported here.
> > I don't know how to reproduce the issue till now.
> > I tried several method, unfortunately, I can not reproduce it by myself. :(
>
> We could reproduce it easily using our user-space tool that creates 1000
> mac-vlans, configures them, dumps routing tables, etc. But, we could
> only reproduce it when we had the ixgbe ports unplugged. If they
> were properly connected to a switch, we did not see any crashes.
>
> My original email on 2/3/2014 has more details, and the thread that
> follows has some info on debugging we did at the time.
I just tried to reproduce the problem, disabling the port on a switch
and setting up 1000 macvlans on a ixgbe, enabling ipv6 and dumping
routing tables. Unluckily I had no success. :(
Any more hints?
Bye,
Hannes
next prev parent reply other threads:[~2014-09-29 19:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 20:37 IPv6 FIB related crash with MACVLANs in 3.9.11+ kernel Ben Greear
2014-02-03 22:03 ` Hannes Frederic Sowa
2014-02-03 22:06 ` Ben Greear
2014-02-08 16:43 ` Ben Greear
2014-02-08 17:23 ` Hannes Frederic Sowa
2014-09-25 22:24 ` Hongmei Li
2014-09-28 12:11 ` Hannes Frederic Sowa
2014-09-29 18:15 ` Hongmei Li
2014-09-29 18:44 ` Ben Greear
2014-09-29 19:03 ` Hannes Frederic Sowa [this message]
2014-09-29 19:48 ` Ben Greear
2014-09-29 20:39 ` Cong Wang
2014-09-29 21:24 ` Ben Greear
2014-10-12 11:42 ` Vladislav Yasevich
2014-10-13 18:06 ` Ben Greear
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=1412017399.14757.4.camel@localhost \
--to=hannes@stressinduktion.org \
--cc=duckcncn@gmail.com \
--cc=greearb@candelatech.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.