Bug 98726 - (NET TG3) BCM5704 tg3 driver panics on AMD64/x86_64/Opteron AMD Serenade system
Summary: (NET TG3) BCM5704 tg3 driver panics on AMD64/x86_64/Opteron AMD Serenade system
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 8.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Miller
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-07-07 23:16 UTC by Konstantin Olchanski
Modified: 2007-04-18 16:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-09-30 15:41:16 UTC
Embargoed:


Attachments (Terms of Use)

Description Konstantin Olchanski 2003-07-07 23:16:29 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701

Description of problem:
The dual Opteron AMD Serenade system comes with a BCM5704 dual 10/100/1000
network interface. The corresponding tg3 linux driver does not work:
 - kernel-smp-2.4.20-18.8 (RH 8.0 errata) panics at ifconfig time ("CPU1 context
corrupt" or similar)
 - vanilla 2.4.21 kernel with compiled-in tg3 driver freezes during boot after
printing "tg3.c version whatever..." (or similar).

A 3COM 100 Mbit card in the 32-bit PCI slot does work.

K.Olchanski olchansk-at-triumf-dot-ca


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. blah...
2.
3.
    

Additional info:

Comment 1 Jeff Garzik 2004-03-03 05:38:31 UTC
Does this still occur in RHEL3 / Fedora?


Comment 2 Jason Tibbitts 2004-04-29 21:36:27 UTC
I have some dual Opteron systems using the Tyan S2882 motherboard,
which has two BCM5704 nics and an EEPro100.  Both FC1 and FC2T3 have
no significant problems with any of the nics.  (ksdevice=link doesn't
work for the Broadcomms, but that's another bug report.)

Comment 3 Bugzilla owner 2004-09-30 15:41:16 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/



Note You need to log in before you can comment on or make changes to this bug.