Path: utzoo!attcan!uunet!wuarchive!cs.utexas.edu!news-server.csri.toronto.edu!helios.physics.utoronto.ca!alchemy.chem.utoronto.ca!system
From: system@alchemy.chem.utoronto.ca (System Admin (Mike Peterson))
Newsgroups: comp.sys.apollo
Subject: Re: Apollo unkillable processes
Summary: Seen lots on DN10000
Keywords: sigp blast kill
Message-ID: <1990Sep21.170734.12930@alchemy.chem.utoronto.ca>
Date: 21 Sep 90 17:07:34 GMT
References: <2414@dover.sps.mot.com>
Organization: University of Toronto Chemistry Department
Lines: 21

This is a fairly common problem on our DN10020, and has been ever since
we got it in Jan/89. We have also seen this on M68K nodes, but not very
often since SR10.2 came out.

Our DN10000 is running SR10.2.0.5, and this problems seems to come and
go in severity with different OS patches, but never disappears.

Neither 'kill', 'kill -9' or 'sigp -stop' has any effect on the
process, but 'sigp -blast' always works as of SR10.2.p (it didn't
before!). Of course, you better shut down and reboot while you still can
once you blast anything.

The current rumor is that this is a problem on dual cpu 10K's - is
anyone still seeing this on any other configuration? If you call this
problem into the HOTLINE, try mentioning call # AT002411 or A2037038,
which have been open for several months already, so the lucky person
at the Response Center can get up to speed right away :-).
-- 
Mike Peterson, System Administrator, U/Toronto Department of Chemistry
E-mail: system@alchemy.chem.utoronto.ca
Tel: (416) 978-7094                  Fax: (416) 978-8775