Skip to contentSkip to conversation

Still having problems with eepro100

DISCUSSION Johan 10 participants 13 messages Oct 30, 2001 – Nov 1, 2001

lore
Share & tools
lore

Johan

author
#0 lore raw

Hello,
Does anyone except me still having problems with the eepro100 drivers ?

The network connection stalls and I'll get this message:

eepro100: wait_for_cmd_done timeout!

I am using the eepro100 drivers with my 100/10 card running in 10mbit and it works in windows.

I have been trying all new kernels + the ac patches but nothing seems to work. The fun thing is that I only gets this problem when I am running XFree, is this just a weird coincidence?

/Johan Nilsson

#1 lore raw

Johan:

Quoted 1 line

Does anyone except me still having problems with the eepro100 drivers ?

Yes, as I've mentioned in a earlier thread on this list, we have problems, but trying the e100-driver from intel doesn't seem to help either (I'm running tests now, and so far, they don't look very promising).

Quoted 2 lines

The network connection stalls and I'll get this message:
eepro100: wait_for_cmd_done timeout!

I'm experiensing the:
eth0: Card reports no resources

And, then a hang of at least a minute before the network connection is restored. All my connections are 100Mbit full duplex, and the error comes when doing heavy traffic. (Try bonnie++ over NFS, for instance).

Signature · 1 line
Thomas
author
#2 lore raw
Quoted 6 lines · On Tue, 30 Oct 2001 12:57:20 +0100 Thomas Langås <[email protected]> wrote:

Johan:

Quoted 1 line

Does anyone except me still having problems with the eepro100 drivers ?

Yes, as I've mentioned in a earlier thread on this list, we have problems, but trying the e100-driver from intel doesn't seem to help either (I'm running tests now, and so far, they don't look very promising).

Yes, I have read it, but it was a while ago and I thought the problem were sovled.

Quoted 6 lines

I'm experiensing the:
eth0: Card reports no resources

And, then a hang of at least a minute before the network connection is restored. All my connections are 100Mbit full duplex, and the error comes when doing heavy traffic. (Try bonnie++ over NFS, for instance).

Yes, its the same for me.

Now I'll know that the driver still have problems. Thanks for your quick answear.

Signature · 1 line
// Johan
#3 lore raw
In reply to Johan
Quoted 6 lines

I am using the eepro100 drivers with my 100/10 card running in 10mbit and it works in windows.

I have been trying all new kernels + the ac patches but nothing seems to work. The fun thing is that I only gets this problem when I am running XFree, is this just a weird coincidence?

Possibly not.

I have one problem box where you have to disable the kernel ACPI stuff but the XFree case is a new one to me

#4 lore raw
Quoted 8 lines · Alan Cox
Quoted 3 lines

I have been trying all new kernels + the ac patches but nothing seems to work. The fun thing is that I only gets this problem when I am running XFree, is this just a weird coincidence?

Possibly not.

I have one problem box where you have to disable the kernel ACPI stuff but the XFree case is a new one to me

I have the same problem with this card and I do not use XFree at all in my servers

linux-2.4.10-ac12 / 2.4.9 / 2.4.3
eepro100: wait_for_cmd_done timeout!

Rafael Martinez

#6 lore raw
In reply to Johan

This problem is inherent in FreeBSD, OpenBSD, NetBSD as well as Linux. I spent a few months hacking my Sony Vaio with number of OS's (it has this network card built onto it).

The problem is fatal unfortunately and the only solution I found was Intel's e100 driver.

'nuff said

Lee Packham

Quoted 21 lines

Hello,
Does anyone except me still having problems with the eepro100 drivers ?

The network connection stalls and I'll get this message:

eepro100: wait_for_cmd_done timeout!

I am using the eepro100 drivers with my 100/10 card running in 10mbit and it works in windows.

I have been trying all new kernels + the ac patches but nothing seems to work. The fun thing is that I only gets this problem when I am running XFree, is this just a weird coincidence?

/Johan Nilsson
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#7 lore raw
In reply to Johan

I've seen this problem when I compiled 2.4.10 kernel with gcc version 3.0.1. I think there is some problem with broadcast and multicast packets because I managed to make direct connection but I can't use dhcpd or xdmcp.

Quoted 39 lines · Lee Packham

This problem is inherent in FreeBSD, OpenBSD, NetBSD as well as Linux. I spent a few months hacking my Sony Vaio with number of OS's (it has this network card built onto it).

The problem is fatal unfortunately and the only solution I found was Intel's e100 driver.

'nuff said

Lee Packham

Quoted 15 lines

Hello,
Does anyone except me still having problems with the eepro100 drivers ?

The network connection stalls and I'll get this message:

eepro100: wait_for_cmd_done timeout!

I am using the eepro100 drivers with my 100/10 card running in 10mbit and it works in windows.

I have been trying all new kernels + the ac patches but nothing seems to work. The fun thing is that I only gets this problem when I am running XFree, is this just a weird coincidence?

Quoted 6 lines

/Johan Nilsson
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#8 lore raw
In reply to Johan

Johan,

If you mean occasional lockups, which go away if you do ifdown / ifup, then try the patch I posted Sunday - it forces one of the bug workarounds on, which was dependent on eeprom by default. Also has a debug line which writes out what it thinks the chip ID is, which activates (or not) the other bug workaround. Alan put some or all of this patch into the latest -ac; from his docs I couldn't tell whether he put in the 'always use bug override' bit, and I expect not. if you want to do it yourself, find where rx_bug is set, and just set it to 1 the line afterwards, and try that.

Alternatively, try the intel drivers.

Alex

Quoted 15 lines · --On Tuesday, October 30, 2001 12:39:27 +0100 Johan <[email protected]> wrote:

Hello,
Does anyone except me still having problems with the eepro100 drivers ?

The network connection stalls and I'll get this message:

eepro100: wait_for_cmd_done timeout!

I am using the eepro100 drivers with my 100/10 card running in 10mbit and it works in windows.

I have been trying all new kernels + the ac patches but nothing seems to work. The fun thing is that I only gets this problem when I am running XFree, is this just a weird coincidence?

Quoted 7 lines

/Johan Nilsson
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

--
Alex Bligh

#9 lore raw

Johan,

Quoted 9 lines · --On Tuesday, October 30, 2001 5:07 PM +0000 Alex Bligh - linux-kernel…

If you mean occasional lockups, which go away if you do ifdown / ifup, then try the patch I posted Sunday - it forces one of the bug workarounds on, which was dependent on eeprom by default. Also has a debug line which writes out what it thinks the chip ID is, which activates (or not) the other bug workaround. Alan put some or all of this patch into the latest -ac; from his docs I couldn't tell whether he put in the 'always use bug override' bit, and I expect not. if you want to do it yourself, find where rx_bug is set, and just set it to 1 the line afterwards, and try that.

Though this worked for me before, it appears to have stopped working and I don't think I reverted the code (sigh). Are you by any chance using something with apm in, or using it as a module and removing the module? The only difference here between working and non-working is that I've suspended and resumed the machine (/without/ power management / apm compiled in).

Quoted 1 line

Alternatively, try the intel drivers.

I am informed by someone who really should know that this /does/ work.

--
Alex Bligh

#10 lore raw
In reply to Johan
Quoted 6 lines · Thomas Langås

I'm experiensing the:
eth0: Card reports no resources

And, then a hang of at least a minute before the network connection is restored. All my connections are 100Mbit full duplex, and the error comes when doing heavy traffic. (Try bonnie++ over NFS, for instance).

I used to have this problem too. Whenever I downloaded something at high speed, I got that error.

This was with an older 2.4 kernel (2.4.5 I think), and the previous harddisk which died on me. Now with 2.4.8 I don't have the problem anymore. I assumed it had to do with the other disk being slow, I think it was still doing PIO. Maybe it's some other thing which causes the kernel not being able to react fast enough?

Kurt

#11 lore raw
In reply to Johan
Quoted 7 lines · Johan

Hello,
Does anyone except me still having problems with the eepro100 drivers ?

The network connection stalls and I'll get this message:

eepro100: wait_for_cmd_done timeout!

Try to add `udelay(1);' inside the loop in wait_for_cmd_done(). It helped to some people with same problems.

Andrey

#12 lore raw
In reply to Johan
Quoted 6 lines · Andrey Savochkin
Quoted 4 lines · Johan

Hello,
Does anyone except me still having problems with the eepro100 drivers ?

Quoted 6 lines
Quoted 3 lines

The network connection stalls and I'll get this message:

eepro100: wait_for_cmd_done timeout!

Try to add `udelay(1);' inside the loop in wait_for_cmd_done(). It helped to some people with same problems.

In 2.4 that's already there:

Quoted 10 lines

static inline void wait_for_cmd_done(long cmd_ioaddr)

{
        int wait = 1000;
        do  udelay(1) ;
        while(inb(cmd_ioaddr) && --wait >= 0);
#ifndef final_version
        if (wait < 0)
                printk(KERN_ALERT "eepro100: wait_for_cmd_done timeout!\n");

#endif
}

In contrast, here is what Becker's current version looks like. It looks like Becker just added a hack to continue waiting.

Things to try:
(a) add a rmb() after the udelay
(b) the Becker version

Quoted 16 lines

/* How to wait for the command unit to accept a command.
Typically this takes 0 ticks. */

static inline void wait_for_cmd_done(long cmd_ioaddr)

{
        int wait = 0;
        do
                if (inb(cmd_ioaddr) == 0) return;
        while(++wait <= 100);
        do
                if (inb(cmd_ioaddr) == 0) break;
        while(++wait <= 10000);
        printk(KERN_ERR "Command %4.4x was not immediately accepted, %d ticks!\n
",
                   inb(cmd_ioaddr), wait);
}
Signature · 3 lines
Jeff Garzik      | Only so many songs can be sung
Building 1024    | with two lips, two lungs, and one tongue.
MandrakeSoft     |         - nomeansno