Subject: Re: sip0: receive FIFO overrun
To: Manuel Bouyer <>
From: Bill Studenmund <>
List: current-users
Date: 05/22/2002 12:10:55
On Wed, 22 May 2002, Manuel Bouyer wrote:

> On Wed, May 22, 2002 at 12:53:46AM +0200, Michael Core wrote:
> > Hi,
> >
> > I use a ECI K7S5a mainboard with a onboard NIC "SiS 900 10/100
> > Ethernet". Sometimes I saw "sip0: receive FIFO overrun" but today this
> > line comes up much more often and the kernel reports "sip0: device
> > timeout", too. Then I'm disconnected from the internet. I tried
> > "ifconfig sip0 down; ifconfig sip0 up" but I did not help. I had to
> > reboot. After very few minutes the same problem popped up again. Looks
> > like a overheat problem, doesn't it? I wonder why it hits the NIC. It's
> > a rather slow DSL connection and I would expect another failure but the
> > system looks stable. 37 degrees celsius system temperature and 51
> > degrees celsius cpu temp. should not be fatal, right? The fan is OK, the
> > system is half-open all the time.
> Well, that may be the key: air flows don't go through the whole box when it's
> open. Parts of the motherboard may lack appropriate cooling because of this.

I also have a K7S5A MB, and see the same thing. I don't think it's
temperature related, but that there's a bug/quirk we aren't dealing with.

Whenever I see these problems, I have to reboot the machine. Nothing else

I've occasionally seen the problem when I first power up, so I don't think
it's temperature.

Also, I can failry reliably cause the problem by shoving a LOT of data
over the link. Like when I was first installing, I'd try to tar my msdos
partition to an NFS-mounted file system. The tar would alway die on the
first large file it found. I had to end up getting a different ethernet
interface for the machine to do the install.

Other thoughts?

Take care,