Bug 102057 - (NET 3C59X) Error messages, but no network
(NET 3C59X) Error messages, but no network
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Garzik
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-08-10 00:28 EDT by John Morris
Modified: 2013-07-02 22:13 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 15:35:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description John Morris 2003-08-10 00:28:17 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030708

Description of problem:
Machine is a Gateway E-4200, a very vanilla Intel BX board with a 3COM 3C905 in
a PCI slot.  Network doesn't work and things like this are in the logs:

eth0: Host error, FIFO diagnostic register 2000
eth0: PCI bus error, bus status 00a0002a
eth0: Transmit error, Tx status register d0

Previous Redhat releases run just fine on this hardware, in fact it's normal
duty has it running a rather ancient RH6.2.  Trying to test RHAS on as many
platforms as I can get at and this one failed.

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

How reproducible:

Steps to Reproduce:
1. Install RHAS Beta
2. Reboot
3. Watch it fail to bring up the network

Additional info:
Comment 1 RHEL Product and Program Management 2007-10-19 15:35:45 EDT
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

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