i386/96382:

[Mark Saad]

>Number:         96382
>Category:       i386
>Synopsis:       
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-i386
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Apr 26 21:50:15 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Mark Saad <msaad at datapipe.com>
>Release:        FreeBSD 6.1-RC1 i386
>Organization:
DataPipe.com
>Environment:
System: 6.1-RC1 FreeBSD 6.1-RC1 #0: Mon Apr 10 17:03:22 UTC 2006 root at op us.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP i386


bge0: <Broadcom BCM5714C Gigabit Ethernet, ASIC rev. 0x9001> mem 0xfdef0000-0xfdefffff,0xfdee0000-0xfdeeffff irq 16 at device 4.0 on pci5
miibus0: <MII bus> on bge0
brgphy0: <BCM5714 10/100/1000baseTX PHY> on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto
bge0: Ethernet address: 00:15:60:0f:e8:81
bge1: <Broadcom BCM5714C Gigabit Ethernet, ASIC rev. 0x9001> mem 0xfded0000-0xfdedffff,0xfdec0000-0xfdecffff irq 17 at device 4.1 on pci5
miibus1: <MII bus> on bge1
brgphy1: <BCM5714 10/100/1000baseTX PHY> on miibus1
brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto
bge1: Ethernet address: 00:15:60:0f:e8:82

>Description:
The current generation of HP Proliant DL/ML Servers contain a Broadcom BCM5714c NIC.
In 6.1-RC1 The bge driver will not reliable work with the BCM5714c. It produces the following issues

1. When the NIC is activated the system hard locks; the keyboard and ACPI power buttons do not work.
2. When the NIC is deactivated ( In Single user mode ) running /sbin/ifconfig will show  spurious "link up" messages
displayed in the ifconfig output; as well as hard lock the server.	
>How-To-Repeat:
     Preform a base 6.1-RC1 from CD. Configure the servers NIC to use DHCP; This will cause the system to Hard lock.

>Fix:
  I beleive the issues are addressed in if_bge.c,v 1.113 and newer. A pull up of the driver from HEAD will fix the issue.



>Release-Note:
>Audit-Trail:
>Unformatted:
 Synopsis:       Support For BCM5714c Not working in 6.1-RC