Bug 14913
| Summary: | eepro driver (for Intel Ether Express Pro 10+) locks up | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Mr. Grace <kb1cvh> | ||||
| Component: | kernel | Assignee: | Alan Cox <alan> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.2 | CC: | alan | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i586 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2002-12-15 00:32:44 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: |
|
||||||
Sorry - I sent to this bug report to block device in error. Should have been assisgned to net. Can you reassign? thanks, Alan, have you seen this? Seen similar: Thge 2.2.17pre eepro driver is the one you want, at least acme claims its fixed 8) Any suggestions on where I can get the 2.2.17pre eepro driver or, do I have to patch my whole 2.2.16 kernel source? If recommended - how do I patch the redhat 2.2.16-3 kernel source - I tried before using the patch from kernel.org but id didn't like it - I think it was looking for "linux vanilla". Peter kb1cvh Wait for the updated kernel rpms ? Mandrakesoft just released some. I'll try that. Thanks for your help! I built a kernel from the MDK 2.2.17-0.16mdk source. The eepro driver seems to work 'better'. Less frequent lock up requiring ifconfig eth1 down;ifconfig eth1 up, but that still happens. No errors in dmesg or log/messages. I expectto replace the card with a 3com one shortly so it's liveable. As this is a pre 2.2.17 kernel, I may try replacing the eepro.c module in the 2.2.16 source with the one from 2.2.17 so that I can take advantage of IPSEC masquerading which hasn't been inserted into the 2.2.17pre0.16 kernel yet. Thanks, Peter kb1cvh Created attachment 2680 [details]
eepro driver patch in our current kernel tree, from pre17
|
The eepro driver (eepro.c) locks up shortly after use. Discovered on an Intel Ether Express ISA card as the 2nd nic. Kernel is 2.2.16-3 custom rolled a number of times to see if would work correctly 1) with eepro as module 2) with eepro compiled into the kernel. From dmesg: Linux version 2.2.16-3 (root@locahost) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Sat Jul 29 21:29:43 EDT 2000 Detected 132958 kHz processor. eth0: RealTek RTL8139 Fast Ethernet at 0x6400, IRQ 9, 00:00:b4:90:8b:a4. id: 0x64 io: 0x210 eth1: Intel EtherExpress Pro/10+ ISA at 0x210, 00:a0:c9:eb:82:bc, IRQ 3, 10BaseT. eth1: set Rx mode to 1 address. eth1: set Rx mode to 1 address. eth1: set Rx mode to 1 address. eth1: carrier error eth1: XMT status = 0xc4f9 eth1: carrier error eth1: XMT status = 0x5516 eth1: carrier error eth1: XMT status = 0x5532 EtherExpress (using eepro) is eth1: eth0 Link encap:Ethernet HWaddr 00:00:B4:90:8B:A4 inet addr:24.91.112.38 Bcast:24.91.113.255 Mask:255.255.254.0 UP BROADCAST RUNNING MTU:1500 Metric:1 RX packets:3601 errors:0 dropped:0 overruns:0 frame:0 TX packets:3432 errors:0 dropped:0 overruns:0 carrier:0 collisions:139 txqueuelen:100 Interrupt:9 Base address:0x6400 eth1 Link encap:Ethernet HWaddr 00:A0:C9:EB:82:BC inet addr:192.168.1.1 Bcast:192.168.1.127 Mask:255.255.255.128 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3374 errors:0 dropped:0 overruns:0 frame:0 TX packets:223 errors:5 dropped:0 overruns:0 carrier:11 collisions:32 txqueuelen:100 Interrupt:3 Base address:0x210 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:1019 errors:0 dropped:0 overruns:0 frame:0 TX packets:1019 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 Is there a patch to fix this? Peter Grace kb1cvh