Bug 65364
Summary: | (NET EPIC100) Network driver fails to get link randomly | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Ted Wright <wright> |
Component: | kernel | Assignee: | Jeff Garzik <jgarzik> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | peterm |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:39:37 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ted Wright
2002-05-22 19:20:05 UTC
After further digging through the network initialization scripts, I have found that a link _IS_ established when the computer boots, but it disappears when the network service is started. Before the network service is started, "mii-tool -v" reports: eth0: negotiated 100baseTx-FD, link ok product info: TDK 78Q2120 rev 10 basic mode: autonegotiation enabled basic status: autonegotiation complete, link ok capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD After "ip link set eth0 up" is run when starting the network service, "mii-tool -v" reports: eth0: no link product info: TDK 78Q2120 rev 10 basic mode: autonegotiation enabled basic status: no link capabilities: advertising: link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD Have you tried using ethtool to restart autonegotiation? I had not tried that until now; "ethtool -r eth0" says: Cannot restart autonegotiation: Operation not supported I've tried some more things to make this work, but without success. The two kernel upgrades for Red Hat 7.3 have not made a difference, and the same symptom are present with the Red Hat 7.3.92 beta version. In retrospect: Red Hat 7.0 works perfectly (card is automatically detected and configured) Red Hat 7.1 works perfectly Red Hat 7.2 works perfectly Red Hat skipjack beta1 (original kernel) works perfectly Red Hat skipjack beta1 (beta kernel-2.4.18-0.8 installed through up2date) fails Red Hat skipjack beta2 fails Red Hat 7.3 (all released kernels) fails Red Hat 7.3.92 (limbo) fails One new symptom appeared in testing Red Hat 7.3.92, I get a message in /var/log/messages every 15-20 seconds after boot until I force a link with "mii-tool -F 100baseTx-FD" that looks like: ... Jul 8 17:18:24 segui kernel: eth0: Setting full-duplex based on MII #1 link partner capability of 41e1. Jul 8 17:18:39 segui kernel: eth0: Setting half-duplex based on MII #1 link partner capability of 0000. Jul 8 17:18:54 segui kernel: eth0: Setting full-duplex based on MII #1 link partner capability of 01e1. ... More symptoms: running "mii-tool -v" several times in a row randomly alternates bewteen two different results. Sometimes is says: eth0: no link product info: TDK 78Q2120 rev 10 basic mode: autonegotiation enabled basic status: no link capabilities: advertising: and other times it says: eth0: no link product info: TDK 78Q2120 rev 10 basic mode: autonegotiation enabled basic status: no link capabilities: advertising: link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD I've tried this with several different (identical) Ositech Jack of Spades network cards plugged into two different switches, and the link partner status seems to fluctuate randomly in all cases. 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/ |