Bug 86332
| Summary: | Failure of e100_2124k2 module during network load testing | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Mike Gahagan <mgahagan> | ||||
| Component: | kernel | Assignee: | John W. Linville <linville> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 2.1 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2004-10-12 20:30:27 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: | |||||||
| Attachments: |
|
||||||
Created attachment 90665 [details]
Trace recovered on Serial console during crash.
ok so what's the problem? eepro100 is the prefered default driver...... e100 driver has been updated in later RHEL 2.1...is this still a problem? Please reopen if driver version 3.0.27-k2 (i.e. RHEL 2.1 U6) still exhibits this problem... |
Description of problem: The following information from Art was submitted to as-errata-discuss: I ran tests with the e.13 kernel and the e100_2124k2 driver. I am using 5 Lake Clark 3.9 e100 PCI adapters and one Broadcom 5703 onboard. There are 3 clients attached to each NIC. The clients are running either FTP login / logout or SAMBA read / write tests. Attached is a log from the serial console. I had this failure after 10 minutes of testing. The default eepro100 driver works well. Version-Release number of selected component (if applicable): 2.4.9-e.10.13 How reproducible: Only with e100_2124k2 Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: See attached, sysreport should follow