From owner-freebsd-stable@FreeBSD.ORG Tue Aug 22 15:14:14 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7611216A4E1 for ; Tue, 22 Aug 2006 15:14:14 +0000 (UTC) (envelope-from sam@fqdn.net) Received: from host.fqdn.net (host.fqdn.net [194.242.157.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA0A343D70 for ; Tue, 22 Aug 2006 15:14:08 +0000 (GMT) (envelope-from sam@fqdn.net) Received: by host.fqdn.net (Postfix, from userid 1003) id D1D422D2; Tue, 22 Aug 2006 16:14:07 +0100 (BST) Date: Tue, 22 Aug 2006 16:14:07 +0100 From: Sam Eaton To: stable@freebsd.org Message-ID: <20060822151407.GN68132@host.fqdn.net> References: <09BFF2FA5EAB4A45B6655E151BBDD90301B7B68B@NT-IRVA-0750.brcm.ad.broadcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <09BFF2FA5EAB4A45B6655E151BBDD90301B7B68B@NT-IRVA-0750.brcm.ad.broadcom.com> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: bce0: Error mapping mbuf into TX chain! 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, 22 Aug 2006 15:14:14 -0000 On Fri, Aug 11, 2006 at 10:27:09AM -0700, David Christensen wrote: > > > > The driver seems to work fine now, that test no longer crashes it. I > > also did some iperf tests between two machines with these cards ( the > > other running linux) and I was getting ~950 MBit /sec between them! > > > > Thanks for your help! I'll keep beating on these machines for a few > > days to come, but will be so glad to get them into productions, > > they're so fast! :-) > > > > Glad to hear things are working now. We've also got a Dell 1950, that was exhibiting exactly the same symptoms. I manually patched up the bce driver and rebuilt the kernel, which got me to the point of having a working enough network device to be able to cvsup to -STABLE and rebuild world and kernel. However, now we no longer get the 'Error mapping mbuf into TX chain!' errors, but instead, under quite low network load, we get : Watchdog timeout occurred, resetting! Which it never really entirely recovers from, requiring a reboot to get working networking back again. I'm a bit at a loss as to what to check next. Only thing that seems particularly different to the other systems described above is that we were running the i386 build, rather than the amd64, so I'm installing amd64 stable instead, just in case this makes any difference. I'm happy to provide any debugging output or whatever that might make it easier for anyone else to help diagnose things... Thanks, Sam. -- "Fortified with Essential Bitterness and Sarcasm" Matt Groening, "Binky's Guide to Love".