From: Brian Haley <brian.haley@hp.com>
To: Thomas Habets <thomas@habets.pp.se>
Cc: Matt Carlson <mcarlson@broadcom.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
Michael Chan <mchan@broadcom.com>
Subject: Re: BUG: IPv6 stops working after a while, needs ip ne del command to reset
Date: Wed, 01 Sep 2010 10:40:26 -0400 [thread overview]
Message-ID: <4C7E65DA.5020106@hp.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1009011034560.31938@red.crap.retrofitta.se>
Hi Thomas,
On 09/01/2010 05:21 AM, Thomas Habets wrote:
>
> I've continued this a bit off-list but thought I would summarize for the
> archives.
>
>
> Summary
> -------
> It looks like a firmware issue on the network card. When ILO is enabled
> it shares the first network card with the OS. When it does this
> multicast is broken. When multicast (on a L2 level) is broken IPv6
> neighbor discovery breaks. Only eth0 breaks, eth1 is unaffected.
So are you running with this set to "Shared Network Port" mode? I'm
guessing you are.
> System
> ------
> HP Proliant DL320 G5p
> Xeon 3GHz
> 1GB RAM
> Arch: amd64
> NIC: Broadcom Corporation NetXtreme BCM5715 Gigabit Ethernet (rev a3)
There was another report on netdev back in 11/2008 on this exact hardware,
with the same problem.
> Problem
> -------
> Buggy box will not answer IPv6 ND or ping to ff02::1. May work at some
> point in the boot process, but once box is fully booted it does not.
I dug-up my notes on the problem, and from what I can tell, the receive
multicast filters on the NIC were getting removed, causing both incoming
IPv6 and IPv4 multicast packets to get dropped. I'm not sure if there
was ever a fix developed, or if we ever came to a conclusion on where the
bug was - iLO, tg3, or some other area.
-Brian
next prev parent reply other threads:[~2010-09-01 14:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 17:55 BUG: IPv6 stops working after a while, needs ip ne del command to reset Thomas Habets
2010-08-13 21:34 ` David Miller
2010-08-16 10:19 ` Eric Dumazet
2010-08-16 10:59 ` Thomas Habets
2010-08-17 5:35 ` Thomas Habets
2010-08-17 6:00 ` Eric Dumazet
2010-08-17 11:08 ` Thomas Habets
2010-08-17 13:15 ` Eric Dumazet
2010-08-17 14:09 ` Thomas Habets
2010-08-17 14:34 ` Eric Dumazet
2010-08-17 15:58 ` Thomas Habets
2010-08-17 17:11 ` Matt Carlson
2010-08-17 17:29 ` Thomas Habets
2010-08-17 18:31 ` Matt Carlson
2010-08-17 18:52 ` Thomas Habets
2010-08-18 1:23 ` Matt Carlson
2010-08-18 7:02 ` Thomas Habets
2010-09-01 9:21 ` Thomas Habets
2010-09-01 13:19 ` Eric Dumazet
2010-09-01 14:40 ` Brian Haley [this message]
2010-09-14 19:56 ` Thomas Habets
2010-09-15 17:37 ` Brian Haley
2010-08-17 17:13 ` Eric Dumazet
2010-08-17 16:14 ` Thomas Habets
-- strict thread matches above, loose matches on Subject: below --
2010-08-06 8:25 Thomas Habets
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=4C7E65DA.5020106@hp.com \
--to=brian.haley@hp.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcarlson@broadcom.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=thomas@habets.pp.se \
/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.