Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Thomas Habets <thomas@habets.pp.se>
Cc: Matt Carlson <mcarlson@broadcom.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 15:19:28 +0200	[thread overview]
Message-ID: <1283347168.2556.319.camel@edumazet-laptop> (raw)
In-Reply-To: <alpine.DEB.1.10.1009011034560.31938@red.crap.retrofitta.se>

Le mercredi 01 septembre 2010 à 11:21 +0200, Thomas Habets a écrit :
> 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.
> 
> 
> System
> ------
> HP Proliant DL320 G5p
> Xeon 3GHz
> 1GB RAM
> Arch: amd64
> NIC: Broadcom Corporation NetXtreme BCM5715 Gigabit Ethernet (rev a3)
> Debian Lenny (5.0.5)
> Kernels: 2.6.35 mainline, 2.6.33.6
> Config: http://pastebin.com/raw.php?i=Y6S8iKW7
> 
> 
> 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.
> 
> If I on the neighboring Cisco router run "clear ipv6 neighbors" (or it 
> times out) that router cannot re-acquire the neigborship with the buggy 
> box. Instant IPv6 breakage until I do one of:
> * Turn on promisc mode long enough for IPv6 ND to do its thing
> * ip ne del <address of neighbor> on the buggy host.
> 
> 
> Workarounds
> -----------
> Either one of these will hide the problem:
> * Set promisc mode on interface (ip link set promisc on eth0) forever
> * Disable ILO
> * Use eth1 instead of eth0.
> 
> 
> Troubleshooting
> ---------------
> Got patch for kernel from Eric Dumazet (eric.dumazet@gmail.com) to output 
> what MAC addresses are being subscribed to, and some registers from the 
> card. Output is earlier in this thread, along with "ethtool -i eth0" and 
> some other data.
> 
> Managed to get diagnostic tool[1] booting from stick (no CD drive in 
> server), but did not set up memory (himem.sys etc..). Running b57udiag 
> it therefore failed due to insufficient memory at test "Group D. Driver 
> Associated tests". Card is assumed to be OK anyway.
> 
> Matt Carlson (mcarlson@broadcom.com) suspected firmware bug and asked me 
> to try disabling ASF and/or IPMI using the diagnostic tool, but running 
> "setasf -d" and "setipmi -d" inside "b57udiag -cmd" did not seem to stick 
> across reboot. It stuck properly before reboot (confirmed with setasf -q). 
> Also tried "b57udiag -u 0". Tried both C-A-D reboot and powercycling (by 
> power cord).
> 
> At boot Linux still said ASF[1] for eth0 and ASF[0] for eth1:
> tg3 0000:03:04.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1]
> tg3 0000:03:04.1: eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
> (this output never changed throughout the process)
> ethtool -d eth1 | grep 0x047 did not change either.
> 
> Then I disabled ILO and PXE in ILO bios and BIOS respectively. That fixed 
> it. eth0 now works with multicast.
> 
> I don't use ILO on this server so in this case that fixes it for me, but 
> the bug is still there.
> 
> At this point Matt thinks I should file a bug report with HP. I will 
> attempt to do that.
> 
> I have more detailed logs of what I did and when, and what the effect was.
> 
> 
> Related
> -------
> May be the same issue as this:
>    https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263260
> Which means it's the same with Ubuntu kernels 2.6.26.3, 2.6.26-5-generic 
> and 2.6.27-2-generic, and mainline kernels 2.6.25, 2.6.26 and 2.6.27.
> 
> 
> [1] http://www.broadcom.com/support/ethernet_nic/netxtreme_server.php
> 


Thanks a lot Thomas for this very detailed report !

  reply	other threads:[~2010-09-01 13:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.1.10.1008131952470.19570@red.crap.retrofitta.se>
2010-08-16 10:19 ` BUG: IPv6 stops working after a while, needs ip ne del command to reset 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 [this message]
2010-09-01 14:40                                 ` Brian Haley
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
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=1283347168.2556.319.camel@edumazet-laptop \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox