Subject: Re: /netbsd: ex1: uplistptr was 0
To: None <M.Drochner@fz-juelich.de>
From: Erik Rungi <email@example.com>
Date: 09/22/1999 11:13:28
On Wed, 22 Sep 1999, Matthias Drochner wrote:
> firstname.lastname@example.org said:
> > Sep 20 17:14:02 doug /netbsd: ex1: uplistptr was 0
> That's quite harmless as long as it doesn't happen
> too often. It means that the receive ring of the
> 3com card was filled up and the card was reinitialized.
Hmm. According to my syslog it happend 61 times in the last 18 hours, and 412
times in the 59 hours before that. It doesn't happen when there's relatively
low traffic going through the box.
> If your network is not unusually loaded, it could indicate
> a problem - another device driver might block interrupts
> for too long. (Or your motherboard shares the PCI interrupt
> with another device?)
I'm routing 2 mostly-full T1s of data through the box. Other than 3
3C905Bs, the machine has a videocard, and the built-in IDE controller.
> You could also try to increase EX_NUPD (elinkxlreg.h), but
> I'm not sure about side effects.
I'll look into that.
Thanks for the advice!