Bug 77037 - e1000 driver autonegotiation only works 50% of the time
e1000 driver autonegotiation only works 50% of the time
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
8.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-10-31 01:03 EST by Rick Richardson
Modified: 2008-08-01 12:22 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-09-30 11:40:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Rick Richardson 2002-10-31 01:03:31 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.18-17.7.x i686)

Description of problem:
I have an Intel PRO/1000 integrated ethernet adapter in a Dell server.  The
server is plugged into a Linksys 10/100 hub.  After a reboot, there is about a
50% chance that the link lights on both ends will stay green and the ethernet
will be usable.  Half the time, as soon as the e1000 driver is loaded by Linux,
the link lights will go out and stay out and the ethernet will fail to come up.

Unplugging the ethernet and plugging it back in will sometimes correct the
problem,
but this is obviously not a solution that can be tolerated on a server.
I have tried unloading and reloading the e1000 driver with no success.

This is with the stock RH 8.0 kernel.

How reproducible:
Sometimes
Comment 1 Bugzilla owner 2004-09-30 11:40:09 EDT
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.