From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 10:06:03 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5E5B106572A for ; Tue, 23 Sep 2008 10:06:03 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by mx1.freebsd.org (Postfix) with ESMTP id 939098FC19 for ; Tue, 23 Sep 2008 10:06:03 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA05.westchester.pa.mail.comcast.net ([76.96.62.43]) by QMTA10.westchester.pa.mail.comcast.net with comcast id JA0d1a0030vyq2s5AA62a9; Tue, 23 Sep 2008 10:06:02 +0000 Received: from koitsu.dyndns.org ([67.180.253.227]) by OMTA05.westchester.pa.mail.comcast.net with comcast id JA611a00A4v8bD73RA62yy; Tue, 23 Sep 2008 10:06:02 +0000 X-Authority-Analysis: v=1.0 c=1 a=QycZ5dHgAAAA:8 a=-Pjz0un6Z4JgZXN2MLQA:9 a=OE4EJ9pC7vIz1pNyk1RriTVXyPcA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 6E33117B81A; Tue, 23 Sep 2008 03:06:01 -0700 (PDT) Date: Tue, 23 Sep 2008 03:06:01 -0700 From: Jeremy Chadwick To: Bruce M Simpson Message-ID: <20080923100601.GA52531@icarus.home.lan> References: <48D8BAF1.1020602@incunabulum.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48D8BAF1.1020602@incunabulum.net> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: FreeBSD stable , Jack Vogel Subject: Re: fxp multicast forwarding problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2008 10:06:04 -0000 On Tue, Sep 23, 2008 at 10:46:25AM +0100, Bruce M Simpson wrote: > Hi, > > Whilst doing some QA work on XORP on my desktop, which has fxp0 and > msk0, fxp0 got totally hosed. > I was running PIM-SM and IGMPv2 router-mode on the box at the time. > > I wonder if this is related to the problems with fxp multicast > transmission I saw back in April. > I'm a bit concerned about this as fxp is still a very widespread and > useful network chip. > > I am running 7.0-RELEASE-p4/amd64. > sysctls for dev.fxp.0 are set to their default values. > > I'm not expert on the fxp driver internals, but perhaps someone else has > seen this kind of problem before. Multicast-promiscuous mode (aka > ALLMULTI) was enabled on the interface. I know some NICs have problems > with this, or don't even support it. > > The errors look like this: > fxp0: SCB timeout: 0x10 0x0 0x80 0x0 > fxp0: SCB timeout: 0x10 0x0 0x80 0x0 > fxp0: DMA timeout > ... repeated ... > > Attempted workarounds which don't work to un-wedge the chip: > Reload the fxp0 microcode with "ifconfig fxp0 link0" > Forcibly unloading the kernel module and reloading it > Unpatching and repatching at the switch (a cheap 10/100 one) > Enabling and disabling promiscuous mode > Twiddling dev.fxp.0.noflow > > The link status looks fine, but the card will not send or receive traffic. > A warm reboot was enough to get things back up again. > > regards, > BMS Adding Jack Vogel, who's responsible for fxp(4). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |