Bug 241824
Summary: | ethtool does not detect link with broadcom / tg3 network card | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Till Maas <opensource> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED WORKSFORME | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | janina |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://www.redhat.com/archives/fedora-test-list/2007-May/msg00549.html | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-09-03 15:52:32 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
Till Maas
2007-05-30 20:59:06 UTC
This bug seems to have vanished, I did not have this probleme recently with F7, so I guess it is fixed in FC6, too. This is not fixed by F-7 on my system. The problem persists as previously reported. Indeed, whenever I boot the particular workstation where my tg card is the gigabit ethernet device, I must run ifup eth0 several times to get a connection--still. (In reply to comment #2) > This is not fixed by F-7 on my system. The problem persists as previously reported. > Indeed, whenever I boot the particular workstation where my tg card is the gigabit ethernet device, I must > run ifup eth0 several times to get a connection--still. There may also notice similiar beheaviour when you connect to a gigabit switch with you gigabit nic but use a network cable that only connects the two cable pairs that are used for fast ethernet. Then the link goes up after a little timeout. With the HP switch I use it is around 15 seconds. When I reported this bug, I also experienced this beheaviour with a fast ethernet only setup, where I did not see this bug anymore. |