From: Eric Dumazet <eric.dumazet@gmail.com>
To: Yann Dupont <Yann.Dupont@univ-nantes.fr>
Cc: netdev@vger.kernel.org
Subject: Re: possible issue between bridge igmp/multicast handling & bnx2x on kernel 2.6.34 and >
Date: Fri, 07 Jan 2011 12:28:25 +0100 [thread overview]
Message-ID: <1294399705.3306.8.camel@edumazet-laptop> (raw)
In-Reply-To: <4D26EDA4.7060502@univ-nantes.fr>
Le vendredi 07 janvier 2011 à 11:40 +0100, Yann Dupont a écrit :
> Le 04/01/2011 14:40, Yann Dupont a écrit :
> ...
> > We just added BCM57711 10G cards (bnx2x driver) on our blade servers
> > (connected to 10G Power Connect M8024).
> > Since then, we are experiencing random lost of packets.
> >
> > Symptom : packets are lost on some vlans for a few seconds, then
> > things go back to normal (and stops again a few minutes later)
> >
>
> As I didn't had answer so far , I digged a little more and captured more
> packets.
> I just noticed that an event trigger that problem : IPv6 neighbor
> discovery packet .
>
> This is , of course, a multicast packet.
>
> Just saw that 2.6.36.3 should include this fix :
>
> > From: David Stevens<dlstevens@us.ibm.com>
> >
> > [ Upstream commit 04bdf0c9a451863e50fff627713a900a2cabb998 ]
> >
> > This patch fixes a missing ntohs() for bridge IPv6 multicast snooping.
> But in fact , I just tested, and this doesn't cure the problem :(
>
> This bug
> - only occurs with bnx2x with tagged vlans, attached to bridges. Other
> interfaces (bnx2 , for exemple) works fine. bnx2x without bridges works
> fine.
> - only happens when bridge is compiled with CONFIG_BRIDGE_IGMP_SNOOPING
> (default setting)
> - is triggered by IPv6 neighbor discovery packet. Just after that
> packet, others packets are discarded for some time.
> - packets originating from same vlans are not affected, only packets
> previously routed are discarded. Examinating those packets, I don't
> undersand why, apart TTL (and mac address), they seems similar .
> - has origin circa 2.6.33 :
> fe2d7c70b747d5d968f4e8fa210676d49d40059 is the first bad commit
> commit 3fe2d7c70b747d5d968f4e8fa210676d49d40059
> Author: Herbert Xu <herbert@gondor.apana.org.au>
> Date: Sun Feb 28 00:49:38 2010 -0800
>
> bridge: Add multicast start/stop hooks
>
> This patch hooks up the bridge start/stop and add/delete/disable
> port functions to the new multicast module.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
>
>
> What can I do to help fixing this bug ?
> regards,
>
Please take a look at whole thread at
https://lkml.org/lkml/2010/8/13/200
I guess this is a similar problem.
next prev parent reply other threads:[~2011-01-07 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 13:40 possible issue between bridge igmp/multicast handling & bnx2x on kernel 2.6.34 and > Yann Dupont
2011-01-07 10:40 ` Yann Dupont
2011-01-07 11:28 ` Eric Dumazet [this message]
2011-02-02 13:29 ` Yann Dupont
2011-03-14 10:40 ` Yann Dupont
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=1294399705.3306.8.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=Yann.Dupont@univ-nantes.fr \
--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