linux-origin
[Top] [All Lists]

Re: posix0 "eth0: RX overflow"

To: John Hawkes <hawkes@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: posix0 "eth0: RX overflow"
From: Ralf Baechle <ralf@xxxxxxxxxxx>
Date: Mon, 25 Sep 2000 22:52:01 +0200
Cc: Kanoj Sarcar <kanoj@xxxxxxxxxxxxxxxxxxxx>, linux-origin@xxxxxxxxxxx
In-reply-to: <00fd01c02721$353bf620$6401a8c0@xxxxxxxxxxxxxxxxxxxx>; from hawkes@xxxxxxxxxxxxxxxxxxxx on Mon, Sep 25, 2000 at 11:48:33AM -0700
References: <00fd01c02721$353bf620$6401a8c0@xxxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-origin@xxxxxxxxxxx
On Mon, Sep 25, 2000 at 11:48:33AM -0700, John Hawkes wrote:

> FYI, I built a kernel (with Lockmeter in it) from this morning's mips64
> sources, and after a fairly heavy AIM7-like load for 15 minutes, I saw
> multiple "eth0: RX overflow" messages and networking no longer worked.

A known problem with the IOC3 network driver.  For some reason in 99% of
cases it fails to reinitialize the driver after it receives such a RX
overflow interrupt.

> Also, I can't rlogin to posix0 more than once.  That is, I can rlogin
> with one window, but not with a second window.

Maybe /etc/securetty?  I normally use telnet and haven't noticed any
problems.

We got another fairly bad problem with the kernel.  It seems that it's
leaking filedescriptors.  Even when I kill all processes except init and
my last shell I occasionally can't remount / read-only resulting in a
fsck on reboot.  I would suspect that this happens somewhere in the binary
compatibility code.

Oh, and I verified that the recent console changes broke /dev/console.

  Ralf

<Prev in Thread] Current Thread [Next in Thread>