Bug 13238 - eepro driver broken
eepro driver broken
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.1
i386 Linux
high Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
Florence Gold
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-06-29 17:22 EDT by Hans de Goede
Modified: 2008-05-01 11:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-12-15 22:18:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Hans de Goede 2000-06-29 17:22:24 EDT
Hi,

With the kernel in beta2, my eepro soundcard consistently stops sending and
/ or receiving any data, this seem to happen at random moments, but can
always be reproduced by copying large files over nfs.

When it happen I get a lot of:
eth0: XMT status = 0x0
or
eth0: XMT status = 0x1
messages

Regards,

Hans
Comment 1 Hans de Goede 2000-06-29 17:22:59 EDT
Ehm make that eepro network card, duh.
Comment 2 Hans de Goede 2000-06-30 03:22:20 EDT
This NIC has worked flawlessly for me as my main nic since the 2.0
kernel days, this is the first time it breaks for me.

The only problem it has is that its bnc connecter has been kicked
against once, so sometimes (say once a month) it doesn't make electrical
contact and you have to remove and insert the cabel again. Due to this
it also has slightly more frame errors then you would normally expect. I
guess that this is what bites with the new kernel, something
probably busted the error handling.

Comment 3 Glen Foster 2000-07-18 15:52:49 EDT
This defect is considered MUST-FIX for Winston Beta-5
Comment 4 Hans de Goede 2000-07-19 02:26:43 EDT
Hint:

This is a known generic 2.2.16 kernel issue, get Alan to send you just the
2.2.17 patches for this, or maybe some more since 2.2.17 is supposed to be
overall better then 2.2.16.
Comment 5 Erik Troan 2000-07-21 12:54:10 EDT
Alan, can you help here?
Comment 6 Glen Foster 2000-07-21 14:08:29 EDT
This defect has been re-classified as MUST-FIX for Winston Gold-release
Comment 7 Michael K. Johnson 2000-08-01 17:46:14 EDT
Alan, should I suck the eepro.c changes from 2.2.17pre14 into our
current kernel?
Comment 8 Alan Cox 2000-08-01 18:00:56 EDT
As I understand from acme - yes
Comment 9 Michael K. Johnson 2000-08-03 12:24:01 EDT
Aha!  Those changes have been there since July 4 under
the guise of linux-2.2.16-sparc-eepro.patch

So this should be fixed in Pinstripe.  I'm therefore
marking this closed; reopen it if Pinstripe does not
fix this bug.
Comment 10 Hans de Goede 2000-08-11 15:43:30 EDT
Just tried it with RC1, still no go. Are you sure this patches aren't surrounded
by if($arch == sparc) in the spec file?


Comment 11 Hans de Goede 2000-08-11 15:51:14 EDT
p.s.

How about going back to eepro from the kernel with 6.2, that had some bugs too
(like hanging the machine if you insmod it without an io parameter and your card
is not at the default adres) but atleast it worked.

Alan I can miss this card, I usually just use it to torture kernels since it is
such a "great" card. so if you want it to test the eepro driver, send me a
private mail with your address and stuff.
Comment 12 Erik Troan 2000-08-16 12:53:03 EDT
Is this failing in the install or after the install?
Comment 13 Michael K. Johnson 2000-08-17 14:43:41 EDT
Yes, the patch is applied on all arch's in our spec file.
Also, while part of the patch is ifdef __sparc__, it is
the same in our sparc-eepro patch and in Alan's patch.
Comment 14 Michael K. Johnson 2000-08-17 14:53:35 EDT
Erm, I the sparc-eepro patch is against the eepro100 driver.
I'll go look again at 2.2.17-pre<latest>...
Comment 15 Michael K. Johnson 2000-08-17 15:06:07 EDT
OK, 2.2.16-21.3 and later will include this fix to the driver.
Sorry for the confusion!
Comment 16 Hans de Goede 2000-08-21 05:41:53 EDT
Verified, works fine now.
Comment 17 Ben LaHaise 2000-08-31 17:46:24 EDT
The eepro100 driver in 2.2.16-22 does not work on an 82559 based card here; it
spews card reports no resources/no RX buffers about once per second.
Comment 18 Michael K. Johnson 2000-08-31 18:14:33 EDT
OK, Ben, send me a patch!  :-)

Try the e100 driver and see if it works; that's useful info.
Comment 19 Glen Foster 2001-01-11 16:02:45 EST
This defect is considered MUST-FIX for Florence Gold release
Comment 20 Michael K. Johnson 2001-01-12 09:38:34 EST
Ben, this bug report was about the eepro, not eepro100.  Since it
was fixed for eepro, I'm closing this.  If eepro100 is still broken
with that card with the 2.4 kernel, please open a new bug report
against that kernel or simply fix it...  :-)
Comment 21 Alan Cox 2001-01-12 09:55:57 EST
Eepro is broken in 2.4.0. It might be fixed in -ac now but Im not sure
Comment 22 Brent Fox 2001-04-06 11:30:40 EDT
The eepro100 driver is working fine on my test machine with the 2.4.2-x kernels.
 Can we consider this issue resolved?
Comment 23 Arjan van de Ven 2001-04-07 20:38:30 EDT
bfox: no, this is not about eepro100!  It's about the 10mbit eepro driver.
Comment 24 Hans de Goede 2001-04-08 10:17:20 EDT
Tihs bug was about an eepro10 (isa) but I'm not sure anymore what it is about
right now, I guess it can be closed when both the eepro10 (isa) and the eepro100
(pci) work.

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