kern/119779: FreeBSD 6.3 release does not recognize Broadcom BCM5722 card on HP ML110 G5

[Ted Mittelstaedt]

>Number:         119779
>Category:       kern
>Synopsis:       FreeBSD 6.3 release does not recognize Broadcom BCM5722 card on HP ML110 G5
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          update
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jan 18 19:20:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Ted Mittelstaedt
>Release:        FreeBSD 6.3-RELEASE i386
>Organization:
Internet Partners, Inc.
>Environment:
System: FreeBSD proxy.ipinc.net 6.3-RELEASE FreeBSD 6.3-RELEASE #0: Wed Jan 16 04:45:45 UTC 2008 root at dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP i386


	
>Description:

I just loaded FreeBSD 6.3-RELEASE on an HP ML110 G5 server, it did not recognize the
onboard network adapter.  I opened the case of the computer and read the top of the
network card chip, it has the following numbers:

Broadcom BCM5722KFB1G

This server does have a single PCI card slot and several PCI express slots,
I inserted an Intel Pro 100 card into the PCI slot which was recognized, to 
complete the install.

I ran pciconf -lv and here is the relevant output:

none2 at pci14:0:0:        class=0x020000 card=0x7051103c chip=0x165a14e4 rev=0x00 hdr=0x00
    vendor     = 'Broadcom Corporation'
    device     = 'NetXtreme BCM5722 Gigabit Ethernet PCIe'
    class      = network
    subclass   = ethernet

	
>How-To-Repeat:
	
>Fix:

I noted back in December that the following patch was posted to the mailing list,
I did not get a chance to try it out (as I only had a short amount of time to
test on this system before turning it over to the customer with a Different OS
on it)

$ pwd 
/usr/src/sys/dev/bge 
$ diff -c if_bge.c* 
*** if_bge.c Mon Nov 26 12:33:28 2007 
--- if_bge.c.NEW Sun Dec 23 15:44:40 2007 
*************** 
*** 169,174 **** 
--- 169,175 ---- 
  { BCOM_VENDORID, BCOM_DEVICEID_BCM5715S }, 
  { BCOM_VENDORID, BCOM_DEVICEID_BCM5720 }, 
  { BCOM_VENDORID, BCOM_DEVICEID_BCM5721 }, 
+ { BCOM_VENDORID, BCOM_DEVICEID_BCM5722 }, 
  { BCOM_VENDORID, BCOM_DEVICEID_BCM5750 }, 
  { BCOM_VENDORID, BCOM_DEVICEID_BCM5750M }, 
  { BCOM_VENDORID, BCOM_DEVICEID_BCM5751 }, 
$ diff -c if_bgereg.h* 
*** if_bgereg.h Tue May 22 15:22:58 2007 
--- if_bgereg.h.NEW Sun Dec 23 15:44:53 2007 
*************** 
*** 2011,2016 **** 
--- 2011,2017 ---- 
  #define BCOM_DEVICEID_BCM5715S 0x1679 
  #define BCOM_DEVICEID_BCM5720 0x1658 
  #define BCOM_DEVICEID_BCM5721 0x1659 
+ #define       BCOM_DEVICEID_BCM5722 0x165a 
  #define BCOM_DEVICEID_BCM5750 0x1676 
  #define BCOM_DEVICEID_BCM5750M 0x167C 
  #define BCOM_DEVICEID_BCM5751 0x1677 

Supposedly this was to be committed as the poster of the patch
reported it worked on his Dell PowerEdge T105 system.  I did not
see it in the driver, however.

Of course, the other workaround is to use a different network card like I
did.

	


>Release-Note:
>Audit-Trail:
>Unformatted: