NetNews Usenet Archive 1993 #3/NN_1993_3.iso/spool/comp/sys/apollo/4347

Text File | 1993-01-28 | 1.9 KB | 34 lines

Newsgroups: comp.sys.apollo
Path: sparky!uunet!europa.eng.gtefsd.com!emory!gatech!paladin.american.edu!howland.reston.ans.net!spool.mu.edu!torn!utcsri!helios.physics.utoronto.ca!alchemy.chem.utoronto.ca!system
From: [e-mail] (System Admin (Mike Peterson))
Subject: Re: First init error and then self tests failed...
Message-ID: <[e-mail]>
Organization: University of Toronto Chemistry Department
References: <[e-mail]>
Date: Thu, 28 Jan 1993 18:00:56 GMT
Lines: 23

In article <[e-mail]> [e-mail] (jt -- John Thompson) writes:
>If you have more than one memory board, you might want to pull the board in
>slot 7 and try again.  If things succeed, then you really do have a bad RAM board
>(this doesn't explain the 270001 status though).

I agree the power supply LEDs should be checked first, though the usual
symptom is that the system just powers down spontaneously.
I would add the Utility (SP) board, the Translator, and even the CPU
to the list. Any bad board on the X-Bus (CPU/MEM/SP) can cause what
appear to be memory problems in our experience.
Problems with any of them can cause weird errors when status gets
(mis)interpreted, which probably explains why you "get" VME errors.
Also, I hope you are not using the SR10.4.p DEX diagnostics - most of them
don't work, including Ethernet, memory and cpu (this situation is
absolutely retarded !!!); the scatman diagnostics do seem to work.

This is not very helpful though if you don't have spares / a spare system,
since you'll probably have to get HP to bring "everything", and just pay
for what fixes it.
--
core error - bus dumped    -*-    Mike Peterson, SysAdmin, U/Toronto Chemistry
 *******   As usual, I speak only for me, myself and I; nobody else   *******
E-mail: [e-mail]  Tel: [phone]  Fax: [phone]