Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!seismo!rlgvax!hadron!jsdy
From: jsdy@hadron.UUCP (Joseph S. D. Yao)
Newsgroups: net.unix-wizards
Subject: Re: Help with 4.3bsd kernel problem needed
Message-ID: <365@hadron.UUCP>
Date: Tue, 8-Apr-86 21:47:07 EST
Article-I.D.: hadron.365
Posted: Tue Apr  8 21:47:07 1986
Date-Received: Sat, 12-Apr-86 01:29:32 EST
References: <666@pucc-s>
Reply-To: jsdy@hadron.UUCP (Joseph S. D. Yao)
Organization: Hadron, Inc., Fairfax, VA
Lines: 23
Keywords: kernel, daemon, halt
Summary: Help exorcising your problems.

In article <666@pucc-s> news@pucc-j (Usenet news) writes:
>Date: 1 Apr 86 16:23:35
>We recently had occasion to investigate a recurring problem in our
>kernel; we experienced crashes (about one per day) on one of our vaxen,
>with only the message:
>
>panic: smr 0x0666 m_err_in
>	...
>Using "adb -k", we began to plow through the various core dumps we had
>lying about.  We were surprised to find a lot of symbols whose origin
>could not be clearly traced back to the kernel sources; along
>with the usual "fork()" and "kill()", things such as "horn()", and
>"tail()" and "clovn()" started showing up.

[ et cute cetera ]

Obviously, you're not running the correct diagnostics.  I have a tape
labelled EXOR-11: I believe it is a system exorciser.  Perhaps DEC has
one for the VAX as well?  For this procedure, of course, you'll need
a consecrated Host.  This should leave you with all virtuous memory,
and no trace of zombie processes.

"Computrem benedico in nomine Patris et Filii at Spiritus Sancti."