Bug 161914
Summary: | tg3 driver does not detect network on GigE | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Christian Huettermann <chuetter> |
Component: | kernel | Assignee: | John W. Linville <linville> |
Status: | CLOSED CANTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | jbaron, jgarcia |
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: | 2005-09-16 14:22:58 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
Christian Huettermann
2005-06-28 13:59:55 UTC
jgarcia Does it work w/ the Cisco switch if you use a statically assigned IP address? Yes Is the Cisco switch configured for spanning tree protocol (STP) on that port? If so, it should be turned-off. STP doesn't serve much purpose on a "leaf" port (i.e. a port connected to an end-station) anyway. STP progresses a newly activated port through a number of stages in which the link is physically active, but the switch is not allowing it to communicate to the rest of the network. Since the physical link is active, the DHCP client proceeds to issue requests. Since the switch is still not passing traffic on that port, the DHCP requests go unanswered. Often the DHCP client will timeout and give-up before STP on the switch has transition the port to a forwarding state. All of the above can be avoided by disabling STP on the switch port (or by using a static IP address). Does disabling STP (presuming that it is currently active) improve the situation for you? Thank you but we already checked that as first thing and STP was and is disabled on that port (default for our user ports). And we would get the same problems or at least the 30 seconds delay while the switchport is throttled to 100 Mbit but there it works flawlessly. We also checked that the port has trunking explicitly disabled and not on auto sensing. We tried also a different port and cable. I do have RHEL4 test kernels w/ a tg3 driver update available here: http://people.redhat.com/linville/kernels/rhel4/ Let's start by trying those kernels to see if things clear-up? Even if not, we'll need to start w/ that as a base. Please post the results of your testing here...thanks! New kernels at the same location, w/ latest tg3 driver from upstream...FYI... Closing due to lack of response. Please re-open when current testing information becomes available. |