All of lore.kernel.org
 help / color / mirror / Atom feed
From: francois.cami@supelec.fr
To: Andrew Morton <andrewm@uow.edu.au>, linux-kernel@vger.kernel.org
Subject: 3C905C and error e401 : problem solved
Date: Mon, 21 May 2001 19:13:35 +0200	[thread overview]
Message-ID: <3B094CBF.A1F36F3D@supelec.fr> (raw)
In-Reply-To: <20010521090946.D769@ipex.cz> <3B08C15E.264AE074@uow.edu.au>, <3B08C15E.264AE074@uow.edu.au> <20010521140443.C8397@ipex.cz> <3B090645.9D54574F@uow.edu.au>


Hi Mr Morton and all linux-kernel,

I have been experimenting with the 3C905C, trying
to get rid of the annoying e401 error (too much work
in interrupt).

I've tried using 64 as max_interrupt_work 
and it solves completely
the e401 problem on this particular machine :

- yoda.rez-gif.supelec.fr (dns/proxy for 500 clients,
  on a 10Mbits/s direct Internet connexion, local
  network is 100Mbits/s)
	ASUS P2B-DS
	dual PII-350
	512MB RAM (2*128+1*256)
	3*IBM 18GB 10KT U2W SCSI 
	3C905C
	S3 Virge
Linux Slackware-current, 2.2.19 or 2.4.4 both built for smp
with APIC. 

Before setting max_interrupt_work at 64, the e401 error
could occur 20 times a day.
Now it doesn't occur anymore.

I have waited for a long time to test that on the
SMP PC because it is critical for our network.
I have tried to link these e401 messages with another
activity on the PC, like heavy I/O, to no avail. The
3C905C does 10 times as many interruptions as the SCSI
controller does. Lowering the max_interrupt_work creates
a lot more errors in the logs (all are e401).


On that second PC, the message still appears (very rarely though,
about once in two or three days. I cannot relate those
occurences to anything). It used to appear very often
(about 40 times a day).
I have tried to put the machine under stress (4 heavy FTP
transfers at once, each 400MB long, with 4 different
clients, connected in 100 MBits FD). The e401 message
has not appeared... I'm a bit at a loss here.

- lando.rez-gif.supelec.fr (FTP for the same network)
	ABIT LX6
	PII300
	128MB RAM
	IBM 8.4GB IDE (1st Master) 
         + Maxtor 60GB IDE (2nd Master)
	3C905C
	S3 Virge
Linux Slackware-current, 2.4.4, ProFTPD

All our network is 100MBits Full Duplex, switched
with 3COM switches.

Best regards, thanks for all your work

François Cami

  parent reply	other threads:[~2001-05-21 17:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-21  7:09 3c905C-TX [Fast Etherlink] problem Robert Vojta
2001-05-21  7:18 ` Andrew Morton
2001-05-21 12:04   ` Robert Vojta
2001-05-21 12:12     ` Andrew Morton
2001-05-21 14:17       ` Robert Vojta
2001-05-21 17:13       ` francois.cami [this message]
2001-05-21 18:51 ` Wilfried Weissmann
2001-05-22  7:20   ` Robert Vojta

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=3B094CBF.A1F36F3D@supelec.fr \
    --to=francois.cami@supelec.fr \
    --cc=andrewm@uow.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.