From khera@kcilink.com  Thu Mar 23 15:19:52 2006
Return-Path: <khera@kcilink.com>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CD39716A429
	for <FreeBSD-gnats-submit@freebsd.org>; Thu, 23 Mar 2006 15:19:52 +0000 (UTC)
	(envelope-from khera@kcilink.com)
Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6DDE443D72
	for <FreeBSD-gnats-submit@freebsd.org>; Thu, 23 Mar 2006 15:19:52 +0000 (GMT)
	(envelope-from khera@kcilink.com)
Received: by yertle.kcilink.com (Postfix, from userid 1002)
	id 40927B81F; Thu, 23 Mar 2006 10:19:51 -0500 (EST)
Message-Id: <20060323151951.40927B81F@yertle.kcilink.com>
Date: Thu, 23 Mar 2006 10:19:51 -0500 (EST)
From: Vivek Khera <vivek@khera.org>
Reply-To: Vivek Khera <vivek@khera.org>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: hack to get bge(4) working on IBM e326m
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         94863
>Category:       kern
>Synopsis:       [bge] [patch] hack to get bge(4) working on IBM e326m
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    yongari
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu Mar 23 15:20:15 GMT 2006
>Closed-Date:    Tue Jul 06 21:59:19 UTC 2010
>Last-Modified:  Tue Jul 06 21:59:19 UTC 2010
>Originator:     Vivek Khera
>Release:        FreeBSD 6.1-PRERELEASE amd64
>Organization:
>Environment:
System: FreeBSD yertle.int.kciLink.com 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #4: Thu Mar 2 13:53:40 EST 2006 khera@yertle.int.kciLink.com:/usr/obj/usr/src/sys/KCI64 amd64


	
>Description:
	

The IBM e326m Opteron server claims to have two Broadcom BCM5714 ethernet
controllers in it (according to the product literature PDF brochure).  FreeBSD
6.0-REL is unable to detect it upon boot, and reviewing the sources for HEAD
shows that there is not yet support for this device ID.

As a hack, I was able to make it recognize the chipset in this box by changing
the definition of the identifier values for BCM5714 in the driver:

In dev/bge/if_bgereg.h, change the definition of BGE_ASICREV_BCM5714 to 0x08
and the definition of BCOM_DEVICEID_BCM5714C to 0x166a.

I'm not sure how to make a full clean patch to support both versions of the
"BCM5714".  I was unable to find *anywhere* via google any info on this chip
ID.  Mostly my question is what naming to use for it?

Even the current release of linux (tried Ubuntu 5.10) doesn't recognize it.
The pre-installed RedHat supposedly did, but I never tried it before I wiped
it for FreeBSD :-)

>How-To-Repeat:
	

n/a

>Fix:

	


In dev/bge/if_bgereg.h, change the definition of BGE_ASICREV_BCM5714 to 0x08
and the definition of BCOM_DEVICEID_BCM5714C to 0x166a.
>Release-Note:
>Audit-Trail:

From: Lucas Nussbaum <lucas.nussbaum@imag.fr>
To: bug-followup@FreeBSD.org, vivek@khera.org
Cc:  
Subject: Re: kern/94863: [bge] hack to get bge(4) working on IBM e326m
Date: Fri, 24 Mar 2006 11:23:26 +0100

 Hi,
 
 Where did you find this information about BCM5714 on the IBM website ?
 
 The NICs are detected by Linux (kernel v. 2.6.15-1-amd64-k8-smp from
 Debian) here as :
 
 eth0: Tigon3 [partno(BCM95780) rev 8003 PHY(5780)] (PCIX:133MHz:64-bit)
 10/100/1000BaseT Ethernet 00:11:25:c4:32:5a
 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1]
 TSOcap[1] 
 eth0: dma_rwctrl[76144000]
 
 So they might be 5780, not 5714, and this would explain the different
 ID. See this Linux diff :
 http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=4cf78e4fb678807e3f8265c9e9031a84f5c601f0;hp=6b6a93c6876ea1c530d5d3f68e3678093a27fab0
 
 I patched the FreeBSD driver to add those IDs, but then, when tranfering
 large files, I got :
  bge1: discard frame w/o leading ethernet header (len 4294967292 pkt len
 4294967292)
 
 And:
  Fatal trap 12: page fault while in kernel mode
  fault virtual address   = 0x28
  fault code              = supervisor write, page not present
  instruction pointer     = 0x8:0xffffffff80227802
  stack pointer           = 0x10:0xffffffffb1b00b80
  frame pointer           = 0x10:0xffffffffb1f3a020
  code segment            = base 0x0, limit 0xfffff, type 0x1b
                          = DPL 0, pres 1, long 1, def32 0, gran 1
  processor eflags        = interrupt enabled, resume, IOPL = 0
  current process         = 18 (irq7: bge1)
  trap number             = 12
  panic: page fault
  Uptime: 1m57s
  Cannot dump. No dump device defined.
  Automatic reboot in 15 seconds - press a key on the console to abort
 
 You didn't run into similar issues ?
 -- 
 | Lucas Nussbaum
 | lucas.nussbaum@imag.fr   jabber: lucas@nussbaum.fr |
 | Doctorant                      Laboratoire ID-IMAG |

From: Vivek Khera <vivek@khera.org>
To: Lucas Nussbaum <lucas.nussbaum@imag.fr>
Cc: bug-followup@FreeBSD.org
Subject: Re: kern/94863: [bge] hack to get bge(4) working on IBM e326m
Date: Fri, 24 Mar 2006 09:57:58 -0500

 On Mar 24, 2006, at 5:23 AM, Lucas Nussbaum wrote:
 
 > I patched the FreeBSD driver to add those IDs, but then, when  
 > tranfering
 > large files, I got :
 >  bge1: discard frame w/o leading ethernet header (len 4294967292  
 > pkt len
 > 4294967292)
 >
 > And:
 >  Fatal trap 12: page fault while in kernel mode
 >  fault virtual address   = 0x28
 >  fault code              = supervisor write, page not present
 >  instruction pointer     = 0x8:0xffffffff80227802
 >  stack pointer           = 0x10:0xffffffffb1b00b80
 >  frame pointer           = 0x10:0xffffffffb1f3a020
 >  code segment            = base 0x0, limit 0xfffff, type 0x1b
 >                          = DPL 0, pres 1, long 1, def32 0, gran 1
 >  processor eflags        = interrupt enabled, resume, IOPL = 0
 >  current process         = 18 (irq7: bge1)
 >  trap number             = 12
 >  panic: page fault
 >  Uptime: 1m57s
 >  Cannot dump. No dump device defined.
 >  Automatic reboot in 15 seconds - press a key on the console to abort
 >
 > You didn't run into similar issues ?
 
 Yes I did when all I did was identify the card by the chip ID.  You  
 also need to activate the 5714 "evasive maneuvers" in bge.c where it  
 is special cased.  Then it works quite well (at least it doesn't  
 crash).  That's where you detect the ASIC as 0x08.
 
 I found the ID numbers by running "pciconf -l" and then adding it to  
 the driver, then I found the ASIC rev by reading the boot message  
 from FreeBSD.
 
 The "product review" literature claims it has a 5714 controller.  I  
 can forward the PDF if you care.  I put little faith into this,  
 though.  For example, the Dell PE800 literature claims it has a 5721  
 chip and so that is what the FreeBSD driver identifies the chip ID  
 as... but the pciconf database claims that chipid is a 5750A1 chip.   
 I'm inclined to trust the pciconf database more... We should make the  
 bge driver get the name from the chip like the commentary claims it  
 can do.  Then we'd know for sure!
 
 

From: Lucas Nussbaum <lucas.nussbaum@imag.fr>
To: Vivek Khera <vivek@khera.org>
Cc: bug-followup@FreeBSD.org
Subject: Re: kern/94863: [bge] hack to get bge(4) working on IBM e326m
Date: Fri, 24 Mar 2006 17:14:35 +0100

 On 24/03/06 at 09:57 -0500, Vivek Khera wrote:
 > 
 > On Mar 24, 2006, at 5:23 AM, Lucas Nussbaum wrote:
 > 
 > >I patched the FreeBSD driver to add those IDs, but then, when  
 > >tranfering
 > >large files, I got :
 > > bge1: discard frame w/o leading ethernet header (len 4294967292  
 > >pkt len
 > >4294967292)
 > >
 > >And:
 > > Fatal trap 12: page fault while in kernel mode
 > > fault virtual address   = 0x28
 > > fault code              = supervisor write, page not present
 > > instruction pointer     = 0x8:0xffffffff80227802
 > > stack pointer           = 0x10:0xffffffffb1b00b80
 > > frame pointer           = 0x10:0xffffffffb1f3a020
 > > code segment            = base 0x0, limit 0xfffff, type 0x1b
 > >                         = DPL 0, pres 1, long 1, def32 0, gran 1
 > > processor eflags        = interrupt enabled, resume, IOPL = 0
 > > current process         = 18 (irq7: bge1)
 > > trap number             = 12
 > > panic: page fault
 > > Uptime: 1m57s
 > > Cannot dump. No dump device defined.
 > > Automatic reboot in 15 seconds - press a key on the console to abort
 > >
 > >You didn't run into similar issues ?
 > 
 > Yes I did when all I did was identify the card by the chip ID.  You  
 > also need to activate the 5714 "evasive maneuvers" in bge.c where it  
 > is special cased.  Then it works quite well (at least it doesn't  
 > crash).  That's where you detect the ASIC as 0x08.
 
 Could you please provide a diff or a copy of your if_bge.* ? I was
 planning to hack the driver next week to support an e326m, so it would
 save me some time :-)
 
 > I found the ID numbers by running "pciconf -l" and then adding it to  
 > the driver, then I found the ASIC rev by reading the boot message  
 > from FreeBSD.
 
 I really think it's a BCM5780 : the same IDs were added to the linux
 driver for the 5780, and I remember ready about 5780 in some tech doc.
 
 > The "product review" literature claims it has a 5714 controller.  I  
 > can forward the PDF if you care.  I put little faith into this,  
 > though.  For example, the Dell PE800 literature claims it has a 5721  
 > chip and so that is what the FreeBSD driver identifies the chip ID  
 > as... but the pciconf database claims that chipid is a 5750A1 chip.   
 > I'm inclined to trust the pciconf database more... We should make the  
 > bge driver get the name from the chip like the commentary claims it  
 > can do.  Then we'd know for sure!
 
 Maybe the policy is to stay in sync with others systems...
 
 Anyway, thanks for the info.
 -- 
 | Lucas Nussbaum
 | lucas.nussbaum@imag.fr   jabber: lucas@nussbaum.fr |
 | Doctorant                      Laboratoire ID-IMAG |

From: Vivek Khera <vivek@khera.org>
To: Lucas Nussbaum <lucas.nussbaum@imag.fr>
Cc: bug-followup@FreeBSD.org
Subject: Re: kern/94863: [bge] hack to get bge(4) working on IBM e326m
Date: Fri, 24 Mar 2006 11:18:10 -0500

 On Mar 24, 2006, at 11:14 AM, Lucas Nussbaum wrote:
 
 > Could you please provide a diff or a copy of your if_bge.* ? I was
 > planning to hack the driver next week to support an e326m, so it would
 > save me some time :-)
 
 I didn't change the bge.c file at all.  I just changed the ID numbers  
 for 5714 in bge_ifreg.h to be those values in my original PR.  This  
 obviously disabled the original 5714, but apparently this 5780 chip  
 in the IBM needs the same special cases as the 5714.
 
 I'd just add the 5780 to the special cases you find for the 5714.   
 Now that I have a real name for this chip, I can attempt making a  
 real patch, unless you beat me to it.
 
Adding to audit trail from misfiled PR kern/95126:

Date: Thu, 30 Mar 2006 15:40:05 -0500
From: Vivek Khera <vivek@khera.org>
 
 Following up, I don't think that it is sufficient to treat this chip  
 as a 5714.  I'm doing a buildworld from an NFS mounted /usr/src to a  
 local /usr/obj while the output is going to my ssh login terminal  
 window.  Every 5 to 7 minutes, I get this in the system log:
 
 Mar 30 15:27:47 neo kernel: nfs server yertle:/usr/src: not responding
 Mar 30 15:27:55 neo kernel: bge0: watchdog timeout -- resetting
 Mar 30 15:27:55 neo kernel: bge0: link state changed to DOWN
 Mar 30 15:27:57 neo kernel: bge0: link state changed to UP
 Mar 30 15:27:58 neo kernel: nfs server yertle:/usr/src: is alive again
 
 and it picks up where it left off on the buildworld.
 
 FWIW here is a patch to implement my earlier hack.  It obviously  
 needs someone to go and see how the latest linux kernel supports this  
 chipset.  I've decided to go buy a Sun instead :-)
 
 --- if_bge.c.dist	Thu Mar 30 14:51:56 2006
 +++ if_bge.c	Thu Mar 30 14:55:23 2006
 @@ -174,6 +174,8 @@
  		"Broadcom BCM5751M Gigabit Ethernet" },
  	{ BCOM_VENDORID, BCOM_DEVICEID_BCM5752,
  		"Broadcom BCM5752 Gigabit Ethernet" },
 +	{ BCOM_VENDORID, BCOM_DEVICEID_BCM5780,
 +		"Broadcom BCM5780 Gigabit Ethernet" },
  	{ BCOM_VENDORID, BCOM_DEVICEID_BCM5782,
  		"Broadcom BCM5782 Gigabit Ethernet" },
  	{ BCOM_VENDORID, BCOM_DEVICEID_BCM5788,
 @@ -2099,10 +2101,11 @@
  	sc->bge_chiprev = BGE_CHIPREV(sc->bge_chipid);
  
  	/*
 -	 * Treat the 5714 and the 5752 like the 5750 until we have more info
 +	 * Treat the 5714, 5752 and the 5780 like the 5750 until we have more info
  	 * on this chip.
  	 */
  	if (sc->bge_asicrev == BGE_ASICREV_BCM5714 || 
 +	    sc->bge_asicrev == BGE_ASICREV_BCM5780 ||
              sc->bge_asicrev == BGE_ASICREV_BCM5752)
  		sc->bge_asicrev = BGE_ASICREV_BCM5750;
  
 --- if_bgereg.h.dist	Thu Mar 30 14:51:50 2006
 +++ if_bgereg.h	Thu Mar 30 14:53:45 2006
 @@ -257,6 +257,7 @@
  #define BGE_ASICREV_BCM5750		0x04
  #define BGE_ASICREV_BCM5714		0x05
  #define BGE_ASICREV_BCM5752		0x06
 +#define BGE_ASICREV_BCM5780		0x08
  
  /* chip revisions */
  #define BGE_CHIPREV(x)			((x) >> 24)
 @@ -1956,6 +1957,7 @@
  #define BCOM_DEVICEID_BCM5751		0x1677
  #define BCOM_DEVICEID_BCM5751M		0x167D
  #define BCOM_DEVICEID_BCM5752		0x1600
 +#define BCOM_DEVICEID_BCM5780		0x166a
  #define BCOM_DEVICEID_BCM5782		0x1696
  #define BCOM_DEVICEID_BCM5788		0x169C
  #define BCOM_DEVICEID_BCM5789		0x169D
 


From: "Internet Partners, Inc. Tech Support" <support@ipinc.net>
To: <bug-followup@FreeBSD.org>
Cc:  
Subject: Re: kern/94863: [bge] hack to get bge(4) working on IBM e326m
Date: Tue, 2 May 2006 13:01:03 -0700

 The current Linux driver from Broadcom, dated Feb 24th 2006, located here:
 http://www.broadcom.com/docs/driver_download/570x/tg3-3.43f.tar.gz
 has a bunch of other ID's in it.  Here's a patch to add these into the
 BGE driver header file and also to change some of the existing chip
 id's and asic revs that are incorrect per the Broadcom driver.
 
 $ diff -c if_bgereg.h.dist if_bgereg.h
 *** if_bgereg.h.dist    Tue May  2 10:58:48 2006
 --- if_bgereg.h Tue May  2 11:31:35 2006
 ***************
 *** 224,232 ****
   
   #define BGE_CHIPID_TIGON_I            0x40000000
   #define BGE_CHIPID_TIGON_II           0x60000000
   #define BGE_CHIPID_BCM5700_B0         0x71000000
 ! #define BGE_CHIPID_BCM5700_B1         0x71020000
 ! #define BGE_CHIPID_BCM5700_B2         0x71030000
   #define BGE_CHIPID_BCM5700_ALTIMA     0x71040000
   #define BGE_CHIPID_BCM5700_C0         0x72000000
   #define BGE_CHIPID_BCM5701_A0         0x00000000      /* grrrr */
 --- 224,234 ----
   
   #define BGE_CHIPID_TIGON_I            0x40000000
   #define BGE_CHIPID_TIGON_II           0x60000000
 + #define BGE_CHIPID_BCM5700_A0         0x70000000
 + #define BGE_CHIPID_BCM5700_A1         0x70010000
   #define BGE_CHIPID_BCM5700_B0         0x71000000
 ! #define BGE_CHIPID_BCM5700_B1         0x71010000
 ! #define BGE_CHIPID_BCM5700_B3         0x71020000
   #define BGE_CHIPID_BCM5700_ALTIMA     0x71040000
   #define BGE_CHIPID_BCM5700_C0         0x72000000
   #define BGE_CHIPID_BCM5701_A0         0x00000000      /* grrrr */
 ***************
 *** 236,251 ****
   #define BGE_CHIPID_BCM5703_A0         0x10000000
   #define BGE_CHIPID_BCM5703_A1         0x10010000
   #define BGE_CHIPID_BCM5703_A2         0x10020000
   #define BGE_CHIPID_BCM5704_A0         0x20000000
   #define BGE_CHIPID_BCM5704_A1         0x20010000
   #define BGE_CHIPID_BCM5704_A2         0x20020000
   #define BGE_CHIPID_BCM5705_A0         0x30000000
   #define BGE_CHIPID_BCM5705_A1         0x30010000
   #define BGE_CHIPID_BCM5705_A2         0x30020000
   #define BGE_CHIPID_BCM5705_A3         0x30030000
   #define BGE_CHIPID_BCM5750_A0         0x40000000
   #define BGE_CHIPID_BCM5750_A1         0x40010000
 ! #define BGE_CHIPID_BCM5714_A0         0x50000000
   
   /* shorthand one */
   #define BGE_ASICREV(x)                        ((x) >> 28)
 --- 238,258 ----
   #define BGE_CHIPID_BCM5703_A0         0x10000000
   #define BGE_CHIPID_BCM5703_A1         0x10010000
   #define BGE_CHIPID_BCM5703_A2         0x10020000
 + #define BGE_CHIPID_BCM5703_A3         0x10030000
   #define BGE_CHIPID_BCM5704_A0         0x20000000
   #define BGE_CHIPID_BCM5704_A1         0x20010000
   #define BGE_CHIPID_BCM5704_A2         0x20020000
 + #define BGE_CHIPID_BCM5704_A3         0x20030000
   #define BGE_CHIPID_BCM5705_A0         0x30000000
   #define BGE_CHIPID_BCM5705_A1         0x30010000
   #define BGE_CHIPID_BCM5705_A2         0x30020000
   #define BGE_CHIPID_BCM5705_A3         0x30030000
   #define BGE_CHIPID_BCM5750_A0         0x40000000
   #define BGE_CHIPID_BCM5750_A1         0x40010000
 ! #define BGE_CHIPID_BCM5750_A3         0x40030000
 ! #define BGE_CHIPID_BCM5752_A0_HW      0x50000000
 ! #define BGE_CHIPID_BCM5752_A0         0x60000000
 ! #define BGE_CHIPID_BCM5752_A1         0x60010000
   
   /* shorthand one */
   #define BGE_ASICREV(x)                        ((x) >> 28)
 ***************
 *** 255,262 ****
   #define BGE_ASICREV_BCM5704           0x02
   #define BGE_ASICREV_BCM5705           0x03
   #define BGE_ASICREV_BCM5750           0x04
 - #define BGE_ASICREV_BCM5714           0x05
   #define BGE_ASICREV_BCM5752           0x06
   
   /* chip revisions */
   #define BGE_CHIPREV(x)                        ((x) >> 24)
 --- 262,270 ----
   #define BGE_ASICREV_BCM5704           0x02
   #define BGE_ASICREV_BCM5705           0x03
   #define BGE_ASICREV_BCM5750           0x04
   #define BGE_ASICREV_BCM5752           0x06
 + #define BGE_ASICREV_BCM5780           0x08
 + #define BGE_ASICREV_BCM5714           0x09
   
   /* chip revisions */
   #define BGE_CHIPREV(x)                        ((x) >> 24)
 ***************
 *** 264,269 ****
 --- 272,282 ----
   #define BGE_CHIPREV_5700_BX           0x71
   #define BGE_CHIPREV_5700_CX           0x72
   #define BGE_CHIPREV_5701_AX           0x00
 + #define BGE_CHIPREV_5703_AX           0x10
 + #define BGE_CHIPREV_5704_AX           0x20
 + #define BGE_CHIPREV_5704_BX           0x21
 + #define BGE_CHIPREV_5750_AX           0x40
 + #define BGE_CHIPREV_5750_BX           0x41
   
   /* PCI DMA Read/Write Control register */
   #define BGE_PCIDMARWCTL_MINDMA                0x000000FF
 ***************
 *** 1945,1961 ****
 --- 1958,1986 ----
   #define BCOM_DEVICEID_BCM5703X                0x16C7
   #define BCOM_DEVICEID_BCM5704C                0x1648
   #define BCOM_DEVICEID_BCM5704S                0x16A8
 + #define BCOM_DEVICEID_BCM5704S_2      0x1649
   #define BCOM_DEVICEID_BCM5705         0x1653
 + #define BCOM_DEVICEID_BCM5705F                0x166E
   #define BCOM_DEVICEID_BCM5705K                0x1654
 + #define BCOM_DEVICEID_BCM5720         0x1658
   #define BCOM_DEVICEID_BCM5721         0x1659
   #define BCOM_DEVICEID_BCM5705M                0x165D
   #define BCOM_DEVICEID_BCM5705M_ALT    0x165E
   #define BCOM_DEVICEID_BCM5714C                0x1668
 + #define BCOM_DEVICEID_BCM5714S                0x1669
 + #define BCOM_DEVICEID_BCM5715         0x1678
 + #define BCOM_DEVICEID_BCM5715S                0x1679
   #define BCOM_DEVICEID_BCM5750         0x1676
   #define BCOM_DEVICEID_BCM5750M                0x167C
   #define BCOM_DEVICEID_BCM5751         0x1677
 + #define BCOM_DEVICEID_BCM5751F                0x167E
   #define BCOM_DEVICEID_BCM5751M                0x167D
   #define BCOM_DEVICEID_BCM5752         0x1600
 + #define BCOM_DEVICEID_BCM5753F                0x16FE
 + #define BCOM_DEVICEID_BCM5753M                0x16FD
 + #define BCOM_DEVICEID_BCM5780         0x166A
 + #define BCOM_DEVICEID_BCM5780S                0x166B
 + #define BCOM_DEVICEID_BCM5781         0x16DD
   #define BCOM_DEVICEID_BCM5782         0x1696
   #define BCOM_DEVICEID_BCM5788         0x169C
   #define BCOM_DEVICEID_BCM5789         0x169D
 
 
 Ted  
 
 

From: "Internet Partners, Inc. Tech Support" <support@ipinc.net>
To: <bug-followup@FreeBSD.org>, <vivek@khera.org>
Cc:  
Subject: Re: kern/94863: [bge] [patch] hack to get bge(4) working on IBM e326m
Date: Thu, 4 May 2006 22:45:38 -0700

 Please try the patch in PR kern/96806 it should correct this.
 
 Ted
State-Changed-From-To: open->feedback 
State-Changed-By: glebius 
State-Changed-When: Sat Oct 14 11:50:41 UTC 2006 
State-Changed-Why:  
Does latest RELENG_6 support your NIC or do you still need the hack? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=94863 
State-Changed-From-To: feedback->suspended 
State-Changed-By: glebius 
State-Changed-When: Sat Oct 14 22:08:55 UTC 2006 
State-Changed-Why:  
Submitter reports that he doesn't have the box, that 
experienced problem anymore. Leave the PR in suspended 
state, awaiting for a followup from a sombody, who 
can reproduce. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=94863 
Responsible-Changed-From-To: freebsd-bugs->freebsd-net 
Responsible-Changed-By: vwe 
Responsible-Changed-When: Wed Jan 14 21:51:39 UTC 2009 
Responsible-Changed-Why:  

Over to maintainer(s). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=94863 
State-Changed-From-To: suspended->closed 
State-Changed-By: yongari 
State-Changed-When: Tue Jul 6 21:58:43 UTC 2010 
State-Changed-Why:  
Close, BCM5780 support was made long time ago. 


Responsible-Changed-From-To: freebsd-net->yongari 
Responsible-Changed-By: yongari 
Responsible-Changed-When: Tue Jul 6 21:58:43 UTC 2010 
Responsible-Changed-Why:  
Track. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=94863 
>Unformatted:
