Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!hplabs!hp-ses!hpcuhb!hpindda!burdick
From: burdick@hpindda.HP.COM (Matt Burdick)
Newsgroups: comp.sys.hp
Subject: Re: NetISR log messages.
Message-ID: <4310042@hpindda.HP.COM>
Date: 22 Jun 89 16:26:07 GMT
References: <5035@zyx.ZYX.SE>
Organization: HP Information Networks, Cupertino, CA
Lines: 35

> We have a number of workstations connected via ethernet and with each
> others' disks mounted via NFS. One of them is an HP9000/320 with HP-UX
> 6.2 running diskless, swapping on a HP9000/350. A third one is a
> DecStation 3100, running Ultrix 3.0.

> June 21  ..time.. Network NetISR Error 2002 pid [ICS]
>   ** Unknown log event

> Does anyone have an idea what these messages mean, and what can be done
> about them (except not running Ultrix applications on a HP-UX X11 server
> :-( )? While they last, my workstation is next to unusable.

The netisr process (/etc/netisr) on your 320 is not keeping up with the
inbound LAN traffic.  When this happens, the queue holding the inbound
packets overflows and the error messages you've seen get logged to the
console (usually screwing up the X display).

	1) Check if netisr is running.  If not, start it up 
	(/etc/netisr 127).

	2) Check if any other processes on your 320 are running at
real-time priority.  If so, it may be hogging the CPU so that netisr can't
keep up.  You could either remove real-time priority from the other process
or processes or boost netisr's priority.  Normally, netisr runs at
real-time priority 127, which is the lowest available.  It may be neccesary
to boost it to 50 or more.

	3) If all of this fails, consider masking the messages from
appearing on your console.  Use "netlogstart -cC" (I believe) to mask off
the messages from the console.  It may also be wise to either keep an eye
on disk space or mask off logging to /usr/adm/neterrlog as well.

-- 
Matt Burdick			| Hewlett-Packard
burdick%hpda@hplabs.hp.com	| Technical Communications Lab