Bug 44561
Summary: | etherexpress pro/10+ fails under load | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Brock Nanson <brock.nanson> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
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: | 2003-06-06 13:42:13 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
Brock Nanson
2001-06-14 05:34:19 UTC
Not xinetd-related... reassigning component. Could you do 2 things for me? 1) try the "e100" driver instead of the "eepro100" (change it in /etc/modules.conf) 2) give me the "lspci" output for the network-card With regard to the e100.o module, it seems to load, however the failure is the same. Note, this was tested from an SSH session, not sure if all information was conveyed. As for lspci, this card is ISA and the computer is pre-PCI! A direct response from maintainer suggests a new improved module for 2.2 and 2.4 is forthcoming. My mistake with regard to the e100 and eepro100 modules... they don't load. Linuxconf appeared to insert them, but a reboot at the machine showed they didn't load (not surprising!). Only eepro.o loads successfully, but dies as described earlier. I see this too. Stopping networking, removing the module and then reinserting fixes it, but obviously having to do this every few minutes is very very annoying. Last version that worked for me was the original module which came with Redhat 6.2 - when the 6.2 kernel was updated, things were broken. I can confirm that this happens in my setup too. Doing a network restart or a full reboot will fix it, but it then dies again about 5 - 10 mins later. I haven't seen this to be triggered by any particular network operation or protocol (unlike some posts above). The interface using this driver will die after a while even without use. Running kernel 2.4.2-12 on a 486 with only ISA support. 3c509 in the machine works fine. |