dan@blender.UUCP (Dan Keizer) (01/10/90)
I just had my first hp3000 crash. Seems it received a parity error. The specifics are listed below: ----------------- Parity Error B=26 A=056772 **** System Failure #13 Status %100001 DELTA-P %044451 HALT 15 1-Normal H for Help-> --------------------- Question of the day is: is this going to be recurring? or was it just a chance happening? or better yet, do I have some bad memory that should be looked at? As I say, this is the first time I've had anything like this happen and would just like to know what everyone else's opinion is. Dan Keizer Western Software Solutions ...!uunet!calgary!wsscal!dan or ...!uunet!calgary!xenlink!blender!dan
Mike_W_Ryan@cup.portal.com (01/15/90)
|I just had my first hp3000 crash. Seems it received a parity error. |The specifics are listed below: |Parity Error |B=26 |A=056772 |**** System Failure #13 The B stands for the bank number in which the multi bit error occurred. The A is the address of the error within the bank. Both numbers are in OCTAL. A multi bit cannot be corrected as single bit errors, hence the crash. You can figure the memory board responsible by knowing that there are 8 banks per 1 megabyte of memory. You may have 1/4 meg, 1, 2, or 4 meg boards (they are marked on the board). I wouldnt panic over 1 occureence but I would run MEMLOGAN.pub.sys and check the memory logs. If there are any logged errors on the same board as the failure, I would consider replacing it proactively. In your case the problem is on the 3rd meg of memory or board 2 if you have all 1 meg pcas.
bmp@hpcupt1.HP.COM (Brian M. Perkin) (01/16/90)
There is a program called MEMTIMER documented in the system utilities manual (I'm not sure what title is on the manual now.) You can use that program to tell the system process that talks to the Memory Controller to do inquiries more often as the memory controller has limited storage for parity error information. Once the data has been copied to a protected disc file, it remains there until the logs are reset. Brian Perkin P.S. The MPE-XL implementation is much different.