Bug 500667
Summary: | Hardware Error bringing up e1000e interface with jumbo frames | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Orion Poplawski <orion> |
Component: | kernel | Assignee: | Andy Gospodarek <agospoda> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.3 | CC: | dzickus, james.brown, peterm, rnickel, uwe.knop |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-04-22 13:57:31 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
Orion Poplawski
2009-05-13 16:07:16 UTC
There were no changes specifically to e1000e between -128.1.6 and -128.1.10, so this is a bit odd. Is there a particular ring size between 1500 and 8982 that seems to work as close to 100% of the time as far as you can tell? I'd be curious how consistently exactly 4000 or 8000 worked. Also seeing: e1000e: probe of 0000:05:00.1 failed with error -2 and no presence of eth1 at all. I'll try 1500 a bit and see if that makes any difference. Has 5.4 been tried and does it resolve this problem? Several errors related to the system PHY that produced failure like this: e1000e: probe of 0000:04:00.1 failed with error -2 were fixed in RHEL5.5. There were a few other times when we have seen this error that were fixed with BIOS updates. Please update to the latest kernel and re-open if that is still broken. |