Bug 200810
Summary: | RHEL4 UP4 Beta2 Intel ethernet problem (tel Corporation PRO/1000 EB Network Connection with I/O Acceleration) | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Dave Olson <dave.olson> |
Component: | kernel | Assignee: | John W. Linville <linville> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | jbaron, lindahl |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-08-07 14:42:50 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
Dave Olson
2006-07-31 19:15:48 UTC
Is the e1000 device on the NIS client? or server? It isn't clear to me from the above message. Presuming the e1000 is on the NIS client, can you use tcpdump or ethereal/wireshark to ascertain whether or not the NIS requests are getting to the server? You will likely need to run them on the server itself or on another box on the same LAN segment (i.e. on a hub on the same switch port as the server). The system with the problem is an NIS client. The problem shows up even with all NIS services disabled, and all the nsswitch.conf lines using just "files" (or for hosts, "files dns". The server was seeing the requests in the failing case, but the client was not seeing the server response, so far as I could tell. I've since witched those clients to SLES10, so I can't easily get a tcpdump trace. SLES10 shows a similar problem, but less frequently. If you happen to either switch the boxes back to RHEL or find a new RHEL box that exhibits the problem, then please collect and post the info requested in comment 1. Also, the output of sysreport would be most welcome. :-) Without that info, I don't think I have enough here to pursue a solution. :-( |