| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 554.1 | | UFP::MURPHY | Rick Murphy | Tue Sep 15 1987 11:02 | 7 |
| Have you looked at the error log? Since you mention a "78032", it's
probably a microvax-II.. they will crash with "Machine Check" if
they get a memory error; if you want to continue shotgunning it,
swap the memory.
Bugcheck.Mem is at VAXWRK::SYS$PUBLIC: last I knew..
-Rick
|
| 554.2 | Not there either. | MDADMN::EATOND | Dan Eaton | Tue Sep 15 1987 11:31 | 22 |
| RE:554.1
Looking at VAXWRK::sys$public I find:
$ dir vaxwrk::sys$public:bugcheck*
%DIRECT-W-NOFILES, no files found
$ dir vaxwrk::sys$public:*.mem
Directory VAXWRK::DOCD$:[SYS$PUBLIC]
ODS2.MEM;1 PCS750V99.MEM;2 SALVAGE.MEM;1 WORKPLAN.MEM;1
Total of 4 files.
Doesn't seem to be there any more. If some one has a pointer to BUGCHECK.MEM,
I'd also like to know where it's located.
Thanks,
Dan Eaton
|
| 554.3 | | WJG::GUINEAU | | Tue Sep 15 1987 11:35 | 17 |
|
Yes, MICROVAX II.
I havent seen any memory errors with SHO MEM. I didn't look too closely
at the error log yet.
when I swapped the CPU this morning, I also set the VMS8 sysgen parm to 1.
The system MACHINE CHECKED about 10 mins after every reboot! Before CPU swap
it would crash a couple times a day or sometimes not for days...
Since resetting VMS8 to 0 (and CPU), seems ok now. I guess I'll wait till
tomorrow before believing it!
|
| 554.4 | found pointer in VMSNOTES | WJG::GUINEAU | | Tue Sep 15 1987 11:38 | 11 |
|
$ dir/size/date VAXWRK::SYS$NOTES:BUGCHECK.MEM
Directory VAXWRK::NOTES$DEVICE:[NOTES]
BUGCHECK.MEM;1 1353 14-AUG-1985 15:14
Total of 1 file, 1353 blocks.
|
| 554.5 | error log of machine check | WJG::GUINEAU | | Tue Sep 15 1987 14:30 | 40 |
|
Heres the latest one (after CPU swap!)
Funny thing is the error log says USER mode and the bugcheck was
machine check while in kernal mode... Maybe the fatal one dosen't get into
the ERRLOG?
V A X / V M S SYSTEM ERROR REPORT COMPILED 15-SEP-1987 13:30
PAGE 1.
**************************** ENTRY 3266. ****************************
ERROR SEQUENCE 4301. LOGGED ON SID 08000101
MACHINE CHECK 15-SEP-1987 12:56:34.18
KA630
EXCEPTION PC 800BD147
ERROR PSL 03C00008
N-BIT
INTERRUPT PRIORITY LEVEL = 00.
PREVIOUS MODE = USER
CURRENT MODE = USER
SUMMARY CODE 00000081
READ BUS ERR, VAP IS PHYS ADDRS
PARAMETER ONE 00FDE624
CURRENT CONTENTS OF VAP REGISTER
PARAMETER TWO 12080000
INTERNAL STATE INFORMATION
_ ATDL REGISTER = 12(X)
_ STATE = 00(X)
_ ALU CONDITION CODE = 08(X)
_ VAX RESTART BIT = 00(X)
_ PC INCREMENT = 00(X)
ANALYZE/ERROR/INC=MACHINE/SINCE=15-SEP-1987 12:00:00.00/OUT=MC.TXT
|
| 554.6 | | UFP::MURPHY | Rick Murphy | Tue Sep 15 1987 22:18 | 11 |
| Yup.. sounds like a memory error. Do you have a dump file? If not,
I don't think the detail on the error will get logged. (During a
crash, the error log buffers get written to the dump file, and then
get copied out to the error log file upon reboot. If it happens
again, create yourself a 4 block SYSDUMP.DMP so the error logging
data gets to the file.
According to this log, you got a read error. The VAP (address) is
way up in memory - Do you have a 16Mb machine? if so, i'd suggest
that the second memory card is bad..
-Rick
|
| 554.7 | | WJG::GUINEAU | | Wed Sep 16 1987 08:47 | 30 |
|
Yes, 16 meg VS II.
I put a dump in
Directory WJG""::DUA0:[SYSDUMP]
SYSDUMP.DMP;1 32772 27-JUL-1987 08:32
Total of 1 file, 32772 blocks.
if your interested!
What should I do about the memory? run some diagnostics and then try
to get the board swapped? Are 8 meg boards still hard to get?
Is there a common problem with these boards? Maybe I can resolder bad
connections...
I guess this explains why BANNER keeps dying. BANNER_ERROR.LOG has
lots of access violations in it. These must be caused by bad memory?
Thanks for all the help. I was hopeing it wasn't memory but...
|