Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!uvaarpa!mcnc!duke!dukempd!ethos!cbosgd!mandrill!hal!ncoast!axcess!allbery
From: allbery@axcess.UUCP (Brandon S. Allbery)
Newsgroups: comp.sys.att
Subject: Re: Mysterious crashes on UNIX pc.
Message-ID: <119@axcess.UUCP>
Date: 21 Dec 87 13:33:11 GMT
References: <174@icus.UUCP> <450@gethen.UUCP>
Organization: aXcess Company, Mentor, Ohio
Lines: 31
In-reply-to: farren@gethen.UUCP's message of 16 Dec 87 10:30:47 GMT


In article <174@icus.UUCP> lenny@icus.UUCP (Lenny Tropiano) writes:
+---------------
| >Also what are these that comes up in the /usr/adm/unix.log pretty often?
| >
| >	Spurious interrupt - level 2 Sat Dec 12 16:58:51 1987
| 
| These interrupts occur when your line printer is powered on and off, or
| any other time the system sees enough noise on the parallel port lines.
| 
| >Should I be worried?
| 
| No.  I get 'em all the time, and haven't had a problem yet.
+---------------

I, however, have observed that they seem to be tied to the window manager out
of memory bug.  I haven't yet had the actual out-of-memory message happen, but
then I turn off my printer when the windaemon starts eating CPU time all of a
sudden (one of the symptoms of the bug).  I'm leaving my printer on now, just
to see if I can duplicate the hangs with the printer on (they don't happen
with the printer off, certainly).

I might suggest that you want to try moving the parallel printer cable about
in its socket; I've found that it's *very* particular about the position -- if
it's just right it works fine, otherwise it doesn't work at all or I get the
constant interrupts and windaemon starts eating CPU.
-- 
 ___  ________________,	Brandon S. Allbery	       cbosgd \
'   \/  __   __,  __,	aXcess Company		       mandrill|
 __  | /__> <__  <__	6615 Center St. #A1-105		       !ncoast!
/  ` | \__. .__> .__>	Mentor, OH 44060-4101	       necntc  | axcess!allbery
\___/\________________.	Moderator, comp.sources.misc   hoptoad/