Subject: Re: /netbsd: ex1: uplistptr was 0
To: None <>
From: Erik Rungi <>
List: current-users
Date: 09/24/1999 10:00:05
On Wed, 22 Sep 1999, Matthias Drochner wrote:

> 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.
> Although I'm living on a quite busy and broadcast polluted
> network, this never happens to me unless I drop into DDB and
> resume.
> 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?)

Hi again!

I can't seem to figure out how to track down the cause of this problem, or
how to get rid of it.

I keep getting it logged and hitting my console maybe 3-5 times an hour, and
it seems to happen more often than not when I'm logged into the box either on
console or via ssh (weird).  When it does happen, everything freezes for about
5 seconds preceeding the message (I guess thats the Ethernet card

Maybe I should just switch to other cards?  Which cards are easily available
and known to be good?  I've heard good things about the fxp/EtherExpress Pro