bob@acornrc.UUCP (Bob Weissman) (05/11/88)
Can someone help decipher this message from a MicroVAX II running
4.3 BSD?
May 8 21:33:53 acornrc vmunix: machine check 80: vap 7fffe594 istate 10001 pc 30d5 psl 3c00000
May 8 21:33:53 acornrc vmunix: mser=0x2c1 page=11872
Prethanks.
--
Bob Weissman
Internet: bob@acornrc.uucp
UUCP: ...!{ ames | decwrl | oliveb | pyramid }!acornrc!bob
Arpanet: bob%acornrc.uucp@ames.arc.nasa.govjmk@scbhq.UUCP (05/12/88)
In article <780@acornrc.UUCP>, bob@acornrc.UUCP (Bob Weissman) writes: > Can someone help decipher this message from a MicroVAX II running > 4.3 BSD? > > May 8 21:33:53 acornrc vmunix: machine check 80: vap 7fffe594 istate 10001 pc 30d5 psl 3c00000 > May 8 21:33:53 acornrc vmunix: mser=0x2c1 page=11872 > > Bob Weissman Bob - When one of the two cpu parity bits <6-5> is set (bit 6 is), the memory cd bits <9-8> are loaded with a 2-bit code which indicates the source of the parity error: 00 - Q22 bus mem or device 01 - KA630 on board memory 10 - MEM expansion module #1 11 - MEM expansion module #2 bit 9 of your mser is set (8 is not) therefore, I suspect memory expansion module #1 is where your problem is. Good luck!! Mike Kitchen South Central Bell
johnd@physiol.su.oz (John Dodson) (05/13/88)
In article <780@acornrc.UUCP>, bob@acornrc.UUCP (Bob Weissman) writes: > Can someone help decipher this message from a MicroVAX II running > 4.3 BSD? > > May 8 21:33:53 acornrc vmunix: machine check 80: vap 7fffe594 istate 10001 pc 30d5 psl 3c00000 > May 8 21:33:53 acornrc vmunix: mser=0x2c1 page=11872 It could be one of a number of things, 1. if you get the same error every time, it could be a bad memory chip mser tells you the board its on, the error above is on module 2. (see KA630AA CPU Module User's Guide - EK-KA630-UG-001 in conjunction with the kernel code)) 2. if you get random errors, and your memory boards have *very long* PMI cables between them, shorten the PMI cable to *MINIMUM* length, ie so you can only just fit it between boards. This is generally a problem with 3rd party memory (mine that caused this problem was Cammington, but once the PMI cables were shortened we have had NO recurrence of the problem in over a year) 3. you could have a radiation source nearby zapping your bits ;-) johnd@physiol.su.oz