Bug 112449

Summary: (TG3) driver doesn't work properly with bcm5700 nic
Product: Red Hat Enterprise Linux 3 Reporter: mike <supermike>
Component: kernelAssignee: David Miller <davem>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 3.0CC: jgarzik, petrides, riel, rperkins, shawn174, tao
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard: tg3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-05-12 01:08:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
bcm5700 driver none

Description mike 2003-12-19 20:43:28 UTC
Description of problem:
tigon3 driver redhat includes in kernel to work with broadcom cards: 
if setting speed/duplex manually, interface stops responding shortly 
after being up (might also not work properly in autoneg mode but I 
haven't tried).

kernel: linux-2.4.21-4.0.1.EL
(This is just the version i've done my testing on specific to using 
the redhat kernel package, i have the same problem in custom builds 
of kernels of different versions when using tg3 in place of bcm5700).
server: dell poweredge 2650 with:
Broadcom Corporation NetXtreme BCM5700 Gigabit Ethernet
(at 14e41644)

How reproducible:

Steps to Reproduce:
1. have the above server with the above card
2. use the tg3 driver for that interface
3. try for eg: ethtool -s eth4 speed 100 duplex full autoneg off
4. ethtool eth4 # -> doesn't show the applied settings, (mii-tool 
doesn't work either)
5. transfer a lot of packets on that interface... it stops 
responding. see rx/tx errs using netstat -ni
6. it comes back to life if you bring the interface down/up

I'll include a patch to add the bcm driver to this redhat kernel 
(patch could be applied to other versions as well though).
It just adds the bcm drivers and allows CONFIG_NET_BROADCOM to 
actually do something (in the redhat kernel it appears it was just 
taken out and selecting that option doesn't do anything).
I've tested it on more than one system, with different kernel 
versions etc. and it works perfectly.

Additional info:
After applying the patch, change tg3 in modules.conf to bcm5700 if 
using modules.

Comment 1 mike 2003-12-19 20:44:57 UTC
Created attachment 96643 [details]
bcm5700 driver

Comment 2 Jeff Garzik 2004-01-12 18:40:53 UTC
Can you provide 'lspci' and 'dmesg' output, so that we may identify
your hardware, and work on the problem?

The bcm5700 has its own bugs, and will not be used.

Comment 3 mike 2004-01-12 19:18:46 UTC
03:08.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5700 
Gigabit Ethernet (rev 12)

also have had speed/duplex related issues using tg3 driver for BCM5703

after searching a bit more on this it appears the issue is fairly 
well known/reported and patches exist from 
http://www.broadcom.com/drivers/downloaddrivers.php and dell...
so, sorry for reproducing that here.

drivers available from dell:
Release Title: Network: Broadcom BCM5700, NetXtreme Family of 
Adapters , Driver, Enterprise Linux, Multi Language, Multi System, 
v.2.2, A01  
Release Date: 12/30/2003 
Description: This package provides an updated tg3 driver for Broadcom 
Gigabit network cards for Red Hat Enterprise Linux 3.  

Additional Information
This RPM fixes an issue with the tg3 driver in the Red Hat 2.4.21-
4.EL series of kernels where the duplex setting cannot be manually 
configured with ethtool. 


Comment 4 mike 2004-01-12 20:40:03 UTC

Comment 5 mike 2004-01-12 20:41:20 UTC
ok well if the url doesn't work just search for network drivers for 
the 2650 for rhel3 on support.dell.com

Comment 6 Shawn Stephens 2004-01-19 13:52:38 UTC
In response to comment #2, what bugs specifically does the bcm5700
driver have?  I think that the bugs in the tg3 driver not being able
to autonegotiate properly and failing far outweigh whatever bugs are
present in the bcm5700 driver. (At least it seems to work better for
folks with BMC57xx NICs)

Comment 8 David Miller 2004-03-29 23:14:05 UTC
I think the current U2 candidate update should fix this
bug, can you try it out?

Comment 9 Ernie Petrides 2004-04-12 21:41:27 UTC
The latest respin of the RHEL3 U2 kernel (version 2.4.21-13.EL)
should resolve this problem.  Changing state of this bug report
to "modified" for final confirmation by reporter.  -ernie

Comment 10 John Flanagan 2004-05-12 01:08:04 UTC
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.