From owner-freebsd-net@FreeBSD.ORG Wed Apr 20 15:21:30 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C194F1065672 for ; Wed, 20 Apr 2011 15:21:30 +0000 (UTC) (envelope-from prt@prt.org) Received: from smtp6.uk.umis.net (smtp6.mail.clearhost.co.uk [IPv6:2001:1420::25:106]) by mx1.freebsd.org (Postfix) with ESMTP id 694C58FC2D for ; Wed, 20 Apr 2011 15:21:30 +0000 (UTC) Received: from kate.prtsystems.ltd.uk ([217.65.165.35]) by smtp6.uk.umis.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1QCZDd-000ARd-03; Wed, 20 Apr 2011 15:21:29 +0000 Message-ID: <4DAEF9F8.5070305@prt.org> Date: Wed, 20 Apr 2011 16:21:28 +0100 From: Paul Thornton User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: Marius Strobl References: <4DADD913.5010208@prt.org> <20110419220907.GD1637@michelle.cdnetworks.com> <4DAEBB67.7070303@prt.org> <20110420131613.GA84319@alchemy.franken.de> <4DAEDE27.8080205@prt.org> <20110420134459.GL38455@alchemy.franken.de> In-Reply-To: <20110420134459.GL38455@alchemy.franken.de> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: pyunyh@gmail.com, freebsd-net@freebsd.org Subject: Re: Broadcom BCM57765 support? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2011 15:21:30 -0000 Hi, On 20/04/2011 14:44, Marius Strobl wrote: > Hrm, looks like neither NetBSD nor OpenBSD support this variant so > far, however Linux also doesn't seem to have special handling for it. > Could you please give the attached patch in addition to the existing > one a try? I've added your patch to brgphy as well - but at a user level I'm still seeing the same thing: - Ethernet frames are transmitted by the box, switch sees them with no errors. - Frames received don't seem to make it to/beyond the driver. - After I hit CTRL-C on the non-working ping, I get a "bge0: watchdog timeout -- resetting" message. If I tcpdump the interface, I see nothing, but the dev.bge.0.stats counters are incrementing when I attempt to ping. The switch is showing counts on both its tx and rx packets counters with no errors. Is there somewhere I need to add more debug in the driver to understand what it is doing? The current dmesg looks like: bge0: mem 0x93100000-0x9310ffff,0x93110000-0x9311ffff irq 18 at device 0.0 on pci4 bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0x93100000 bge0: attempting to allocate 1 MSI vectors (8 supported) msi: routing MSI IRQ 256 to local APIC 0 vector 56 bge0: using IRQ 256 for MSI bge0: CHIP ID 0x57785000; ASIC REV 0x57785; CHIP REV 0x577850; PCI-E bge0: Disabling fastboot bge0: Disabling fastboot miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: OUI 0x00d897, model 0x0024, rev. 0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge0: bpf attached bge0: Ethernet address: c4:2c:03:08:0b:9d bge0: [MPSAFE] bge0: [FILTER] Paul.