From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 09:46:27 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 92FE1106567B for ; Tue, 23 Sep 2008 09:46:27 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 6D2638FC18 for ; Tue, 23 Sep 2008 09:46:27 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id D1EE616562F for ; Tue, 23 Sep 2008 05:46:26 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Tue, 23 Sep 2008 05:46:26 -0400 X-Sasl-enc: CzBlP4opuzn+HkcFFmJb+MDVTaDUaWL3HPVnPpQEZfBs 1222163186 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 61AE820403 for ; Tue, 23 Sep 2008 05:46:26 -0400 (EDT) Message-ID: <48D8BAF1.1020602@incunabulum.net> Date: Tue, 23 Sep 2008 10:46:25 +0100 From: Bruce M Simpson User-Agent: Thunderbird 2.0.0.14 (X11/20080514) MIME-Version: 1.0 To: FreeBSD stable X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: 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 09:46:27 -0000 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