From nobody@FreeBSD.org  Wed Jul 12 03:28:34 2006
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9AF4F16A4DA
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 12 Jul 2006 03:28:34 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 66F5943D46
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 12 Jul 2006 03:28:34 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id k6C3SYOh038791
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 12 Jul 2006 03:28:34 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id k6C3SYis038790;
	Wed, 12 Jul 2006 03:28:34 GMT
	(envelope-from nobody)
Message-Id: <200607120328.k6C3SYis038790@www.freebsd.org>
Date: Wed, 12 Jul 2006 03:28:34 GMT
From: Gala <galaluk@gmail.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Unstable of Broadcom NetXtreme II (BCM5708) PCI/PCIe Gigabit Ethernet
X-Send-Pr-Version: www-2.3

>Number:         100138
>Category:       kern
>Synopsis:       Unstable Broadcom NetXtreme II (BCM5708) PCI/PCIe Gigabit Ethernet
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jul 12 03:30:16 GMT 2006
>Closed-Date:    Wed Jul 19 08:19:11 GMT 2006
>Last-Modified:  Sun Aug  6 03:50:15 GMT 2006
>Originator:     Gala
>Release:        FreeBSD 6.1/AMD64
>Organization:
>Environment:
FreeBSD www2.ktzonehk.com 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun May  7 04:15:57 UTC 2006     root@bloom.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP  amd64

>Description:
We have a DELL PowedEdge 2950 that embedded Broadcom NetXtreme II 5708
Gigabit Ethernet NIC.

When we try to install something on it, it will suddenly disconnect till we
reboot that.

Ther error message is : bce0: /usr/src/sys/dev/bce/if_bce.c(4644): Error
mapping mbuf into TX chain!
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: ps 
State-Changed-When: Wed Jul 19 08:14:27 UTC 2006 
State-Changed-Why:  
Fixed in 1.2.2.3 

http://www.freebsd.org/cgi/query-pr.cgi?pr=100138 

From: "Scott Wilson" <scott.wilson@gmail.com>
To: bug-followup@FreeBSD.org, galaluk@gmail.com
Cc:  
Subject: Re: kern/100138: Unstable Broadcom NetXtreme II (BCM5708) PCI/PCIe Gigabit Ethernet
Date: Sun, 6 Aug 2006 05:40:27 +0200

 I am still experiencing this problem on a PowerEdge 1950 running amd64
 port with the patch mentioned in this pr:
 
 FreeBSD 6.1-RELEASE-p3 #0: Tue Aug  1 20:23:58 EDT 2006
     root@pe3.private.idealist.org:/usr/obj/usr/src/sys/SMP
 
 
 ---------- Forwarded message ----------
 From: Pyun YongHyeon <pyunyh@gmail.com>
 Date: Aug 5, 2006 5:10 AM
 Subject: Re: Re: bce0: Error mapping mbuf into TX chain!
 
 
 On Fri, Aug 04, 2006 at 03:52:40PM +0200, Scott Wilson wrote:
  > On 7/13/06, Doug Ambrisko <ambrisko@ambrisko.com> wrote:
  > >David (Controller AE) Christensen writes:
  > >| Sorry, I've been out on vacation and just got back into town.  I'll MFC
  > >| the patch within the next day or two.
  > >
  > >I'll let you merge in the down/up fix that I put into -current.
  > >
  > >Doug A.
  >
  > Hi, I just had a bce interface lock up with the same problem:
  >
  > Aug  4 07:00:16 pe3 kernel: bce0: /usr/src/sys/dev/bce/if_bce.c(4644):
  > Error mapping mbuf into TX chain!
  > Aug  4 07:00:47 pe3 last message repeated 368 times
  > ....
  >
  > running v 1.2.2.5 of if_bce.c from RELENG_6 which has the
  > defragmentation patch mentioned in this thread.  Any suggestions on
  > how I can help find a fix?
  >
  > scott
 
 Hmm... I can see several bus_dma(9) related bugs in bce(4).
 For architectures that have IOMMU hardware it may have corrupted DMA
 mapping and I'm pretty sure it wouldn't work on sparc64.
 When it has to handle many fragmented frame or has insufficient
 number of free Tx descriptors it would show unexpected results.
 Unfortunately I don't have hardwares supported by bce(4) and
 fixing requiries a working hardware. :-(
 
 --
 Regards,
 Pyun YongHyeon
>Unformatted:
