From nobody@FreeBSD.org  Sat Jun  5 03:17:31 2004
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 1055116A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Sat,  5 Jun 2004 03:17:31 -0700 (PDT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0A19143D45
	for <freebsd-gnats-submit@FreeBSD.org>; Sat,  5 Jun 2004 03:17:31 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i55AHGj6065946
	for <freebsd-gnats-submit@FreeBSD.org>; Sat, 5 Jun 2004 03:17:16 -0700 (PDT)
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id i55AHGGi065945;
	Sat, 5 Jun 2004 03:17:16 -0700 (PDT)
	(envelope-from nobody)
Message-Id: <200406051017.i55AHGGi065945@www.freebsd.org>
Date: Sat, 5 Jun 2004 03:17:16 -0700 (PDT)
From: Luuk van Dijk <lvd@mndmttr.nl>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Broadcom NetXtreme BCM5704s brgphy not detected on Nexicon Blade server
X-Send-Pr-Version: www-2.3

>Number:         67598
>Category:       kern
>Synopsis:       Broadcom NetXtreme BCM5704s brgphy not detected on Nexicon Blade server
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jun 05 03:20:09 PDT 2004
>Closed-Date:    Wed Jun 09 16:06:20 GMT 2004
>Last-Modified:  Wed Jun 09 16:06:20 GMT 2004
>Originator:     Luuk van Dijk
>Release:        5.0 upto 5.2.1
>Organization:
Mind over Matter B.V.
>Environment:
5.2.1 install cd with generic kernel, fixit shell, no uname available
>Description:
on the Nexicon Blade server, equipped with Broadcom NetXtreme BCM5704s,
the bge driver detects both interfaces, but not the miibus/brgphy
interfaces (as it does on another server that I have which has 2x BCM5703)

in the fixit shell, both bge0 and bge1 show up with ifconfig, and
with the correct mac address.  assigning an ip address changes the state from 'no carrier' to 'active, but the interface cannot be pinged 
from another computer on the same net, nor is any packet sent out when I try to install over NFS.

a driver written by broadcom for 4.2, 'if_bc.c' exists, which works fine under 4.8, so the hardware is correct.  also, I can pxeboot over bootp/tftp/nfs. unfortunately this driver is incompatible with the 5.x architecture.
>How-To-Repeat:
boot the install image, start fixit shell, ifconfig bge0 192.168.1.1,
ping from another machine on the same net.  try to install from NFS, watch the net with tcpdump. observe the absence of traffic.
>Fix:
(probably in the bgrphy probe code)
>Release-Note:
>Audit-Trail:

From: Luuk van Dijk <lvd@mndmttr.nl>
To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-bugs@FreeBSD.org
Cc:  
Subject: Re: kern/67598: Broadcom NetXtreme BCM5704s brgphy not detected on
	Nexicon Blade server
Date: 05 Jun 2004 13:19:25 +0200

 looking for documentation on the 5704s, I notice that the 's' means: has
 no 'PHY' but a 'SERDES' physical layer.  So the above diagnose does not
 apply, but the phenomena are still there: chip is detected, but no
 traffic
 

From: Paul Saab <ps@mu.org>
To: Luuk van Dijk <lvd@mndmttr.nl>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/67598: Broadcom NetXtreme BCM5704s brgphy not detected on Nexicon Blade server
Date: Sun, 6 Jun 2004 17:09:00 -0700

 What does a verbose bootup look like?
 
 Luuk van Dijk (lvd@mndmttr.nl) wrote:
 > 
 > >Number:         67598
 > >Category:       kern
 > >Synopsis:       Broadcom NetXtreme BCM5704s brgphy not detected on Nexicon Blade server
 > >Confidential:   no
 > >Severity:       non-critical
 > >Priority:       medium
 > >Responsible:    freebsd-bugs
 > >State:          open
 > >Quarter:        
 > >Keywords:       
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Sat Jun 05 03:20:09 PDT 2004
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Luuk van Dijk
 > >Release:        5.0 upto 5.2.1
 > >Organization:
 > Mind over Matter B.V.
 > >Environment:
 > 5.2.1 install cd with generic kernel, fixit shell, no uname available
 > >Description:
 > on the Nexicon Blade server, equipped with Broadcom NetXtreme BCM5704s,
 > the bge driver detects both interfaces, but not the miibus/brgphy
 > interfaces (as it does on another server that I have which has 2x BCM5703)
 > 
 > in the fixit shell, both bge0 and bge1 show up with ifconfig, and
 > with the correct mac address.  assigning an ip address changes the state from 'no carrier' to 'active, but the interface cannot be pinged 
 > from another computer on the same net, nor is any packet sent out when I try to install over NFS.
 > 
 > a driver written by broadcom for 4.2, 'if_bc.c' exists, which works fine under 4.8, so the hardware is correct.  also, I can pxeboot over bootp/tftp/nfs. unfortunately this driver is incompatible with the 5.x architecture.
 > >How-To-Repeat:
 > boot the install image, start fixit shell, ifconfig bge0 192.168.1.1,
 > ping from another machine on the same net.  try to install from NFS, watch the net with tcpdump. observe the absence of traffic.
 > >Fix:
 > (probably in the bgrphy probe code)
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted:
 > _______________________________________________
 > freebsd-bugs@freebsd.org mailing list
 > http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
 > To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org"
 > 
 
 -- 
 -ps
State-Changed-From-To: open->closed 
State-Changed-By: wpaul 
State-Changed-When: Wed Jun 9 16:02:26 GMT 2004 
State-Changed-Why:  
The BCM5704 appears to have some special (and undocumented) registers 
that have to be set to properly advertise flow control ability when 
autonegotiating with a switch in TBI/fiber mode. I added code to 
the bge(4) driver to set these registers during autoneg, and the 
link seems to be properly negotiated now, and traffic is exchanged 
correctly. A patch for this problem is available at 
http://www.freebsd.org/~wpaul/bge.diff. This patch has been supplied 
to the submitter and checked in to the FreeBSD-current sources. 

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