Ralf Baechle wrote:
> 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.
Ralf,
I have seen this pretty often on the SNIA64 machine too and I normally see
it on the way to multi-user ..
Are you saying that in 99% of the time when we get RX overflow, we can
reinit the driver and card? I was led to believe that we NEVER been able to
recover
from an RX overflow situation.
The bottom line is that for SNIA64, this may be our only ethernet connection
and
we need to stabilize it. Are you actively engaged in this problem?
Thanks.
Colin
>
>
> > 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
|