Bug 86332 - Failure of e100_2124k2 module during network load testing
Failure of e100_2124k2 module during network load testing
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: John W. Linville
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-03-19 16:49 EST by Mike Gahagan
Modified: 2007-11-30 17:06 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-12 16:30:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Trace recovered on Serial console during crash. (281.36 KB, text/plain)
2003-03-19 16:51 EST, Mike Gahagan
no flags Details

  None (edit)
Description Mike Gahagan 2003-03-19 16:49:15 EST
Description of problem:

 The following information from Art was submitted to as-errata-discuss@redhat.com:
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):


How reproducible:
Only with e100_2124k2

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

See attached, sysreport should follow
Comment 1 Mike Gahagan 2003-03-19 16:51:29 EST
Created attachment 90665 [details]
Trace recovered on Serial console during crash.
Comment 3 Arjan van de Ven 2003-03-19 16:54:47 EST
ok so what's the problem?
eepro100 is the prefered default driver......
Comment 4 John W. Linville 2004-08-25 11:23:00 EDT
e100 driver has been updated in later RHEL 2.1...is this still a problem?
Comment 5 John W. Linville 2004-10-12 16:30:27 EDT
Please reopen if driver version 3.0.27-k2 (i.e. RHEL 2.1 U6) still
exhibits this problem...

Note You need to log in before you can comment on or make changes to this bug.