[eepro100] sgi 320 visws and eepro100

[Jim Edwards]

Okay, I now hoave some info I hope you'll find a little more useful.  I can reproduce the problem consistantly by starting an
ftp or rcp process with a nearby machine (in network terms)
These processes use and do not return memory to the system, I have 640MB so it takes awhile but eventually the machine starts
swapping and everything goes downhill from there.

The messages written to the system log are being mangled (how to fix this?)  but I get something like


exiting interupt, status=0x0050                  <- repeated frequently
scavenge candidate 14 status 400ca000         <-  also repeated with candidate number changes


Note that starting an ftp process with a machine networkly far has no problems.

what can I try next?

Jim


Jim Edwards wrote:

> Donald,
>
> The problems only occur after some particularly streesful internet activity, as for example running a xdmcp client.  I
> wasn't getting any messages to the /var/log/messages file yesterday.  So after I got your e-mail I reinstalled the
> eepro100 module with debug=6.  I also rebooted the machine at that time and haven't yet been able to reproduce the
> problems, could switching the debug level be having some effect?   But I did conduct an experiment in which I went back to
> init 3 and ran procinfo -n0 on one console and ping on another.  What I found (and this is when I'm not having problems )
> is that each ping seems to use 2 eth0 interupts and 3 usb interupts.   I'm a little in over my head here, can you tell me
> what it is I am seeing?
>
> thanks,
> Jim
>
> Jim Edwards wrote:
>
> > Hi again,
> >
> > I've updated to the v1.15 driver and compiled using -DUSE_IO_OPS,   I'm not getting the same messages (see the previous
> > posting below) from the driver any longer but I still have some very strange network problems happening.  For example
> > here is a little output from a ping of our local nameserver.   Note the sequence in which things are returned.
> >
> > PING modelo.inmet.gov.br (192.168.99.22) from 192.168.99.91 : 56(84) bytes of data.
> > 64 bytes from modelo.inmet.gov.br (192.168.99.22): icmp_seq=0 ttl=64 time=224 usec
> > 64 bytes from modelo.inmet.gov.br (192.168.99.22): icmp_seq=18 ttl=64 time=141 usec
>
> _______________________________________________
> eepro100 mailing list
> eepro100@scyld.com
> http://www.scyld.com/mailman/listinfo/eepro100