linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jeff Chua" <jeffchua@silk.corp.fedex.com>
To: "Christian Robottom Reis" <kiko@async.com.br>, <eepro100@scyld.com>
Cc: <saw@saw.sw.com.sg>, <linux-kernel@vger.kernel.org>,
	"Jeff Chua" <jchua@fedex.com>
Subject: Re: eepro100 problems with 2.2.19 _and_ 2.4.0
Date: Sun, 17 Jun 2001 23:49:41 +0800	[thread overview]
Message-ID: <003e01c0f745$3e0cbc40$a35812bc@corp.fedex.com> (raw)
In-Reply-To: <Pine.LNX.4.32.0106162339280.191-100000@blackjesus.async.com.br>

Try to add "options eepro100 options=0" to your /etc/modules.conf
to default the speed to 10Mbps if you're using 10BaseT.

add to /etc/modules.conf ...
# options=0x30 100mbps full duplex
# options=0x20 100mbps half duplex
# options=0     10mbps half duplex
options eepro100 options=0

then run "depmod -a"

Thanks,
Jeff
[ jchua@fedex.com ]
----- Original Message ----- 
From: "Christian Robottom Reis" <kiko@async.com.br>
To: <eepro100@scyld.com>
Cc: <saw@saw.sw.com.sg>; <linux-kernel@vger.kernel.org>
Sent: Sunday, June 17, 2001 10:43 AM
Subject: Re: eepro100 problems with 2.2.19 _and_ 2.4.0



Just noticed:

On Sat, 16 Jun 2001, Christian Robottom Reis wrote:

> Steps to reproduce problem:
>
> * Run large ( > 2MB works ) ftp transfer in box.
> * ssh in from another box and attempt an ls -lR /

Note below:

> * 2.2.19 with Donald's eepro100.c scyld:network/
> Hard lock (seems to take longer to hang) - it also creates
> 8 devices eth0-eth7!
>
> * 2.2.19 with Donald's eepro100.c fromscyld:network/test/
> Hard lock (pretty fast) - no multiple creation bugs

Actually, they don't hang _immediately_. They report:

eth0: Transmit timed out: status 0050  0000 at 6022/6034 commands 000c0000
000c0000 000c0000
Command 0000 was not immediately accepted, 10001 ticks!

And the ssh connection stalls but does on trying (it eventually hangs, but
not after a lot of errors are reported on the problem-box's console)

And then the box hard locks. Interesting to see that only when I run the
ssh ls -lR is that any error at all is produced. The lockups I was seeing
were all interactive use and I never really noticed if errors were showing
up or not; I just assumed they weren'.

Any help you can provide is very much appreciated. I'm about to try
Intel's drivers to see how they do.

Take care,
--
/\/\ Christian Reis, Senior Engineer, Async Open Source, Brazil
~\/~ http://async.com.br/~kiko/ | [+55 16] 274 4311

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



  reply	other threads:[~2001-06-17 15:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-17  2:26 eepro100 problems with 2.2.19 _and_ 2.4.0 Christian Robottom Reis
2001-06-17  2:43 ` Christian Robottom Reis
2001-06-17 15:49   ` Jeff Chua [this message]
2001-06-17 19:09     ` Christian Robottom Reis
2001-06-18  8:48       ` Jeff Chua
2001-06-17  3:40 ` Christian Robottom Reis
2001-06-18 19:41   ` Andrey Savochkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='003e01c0f745$3e0cbc40$a35812bc@corp.fedex.com' \
    --to=jeffchua@silk.corp.fedex.com \
    --cc=eepro100@scyld.com \
    --cc=jchua@fedex.com \
    --cc=kiko@async.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saw@saw.sw.com.sg \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).