Conference vaxaxp::vmsnotes

   Machine checks normally indicate hardware-related problems.

   You will need to decode the machine check per the Mikasa
   documentation, and determine more about the particular
   reported problem(s) -- without this information, it is
   exceedingly difficult to suggest anything...

   You might want to look around in the WRKSYS::MIKASA notes
   conference -- information on decoding machine checks might
   be available there.

   Here are a few notes -- also try a COMET search for any
   machine check information -- from the MIKASA conference:

    15  WRKSYS::DUTTON        7-FEB-1995     0  Mikasa Machine Check Logout Fra
    83  BACHUS::VANHAVERE    18-JAN-1995    10  Machinecheck 0x208 with EISA mo
   126   RULLE::WALLMAN       3-MAR-1995     3  Machinecheck while in PAL-mode
   132  AUSSIE::TAJALLI      10-MAR-1995     4  FATAL BUGCHECK
   140  CHOOKE::KLUMPES      15-MAR-1995     6  Machine Check 208
   162  KERNEL::SCOTT        31-MAR-1995     5  machine check decode information
   170  UTOPIE::PUCHINGER_G   5-APR-1995     8  Machine check - Hardware Error
   183  DABEAN::EMBY         19-APR-1995     0  Machine Check Program
   201  GIDDAY::PUDIPEDDI     2-MAY-1995     4  m/c check code=255
   284  ANNECY::DEBACKER      4-JUL-1995     4  Machine check at boot time on 1
   304  CIVPR1::WOOD         26-JUL-1995     2  Bugcheck 3C4
   310   CSC32::HUTMACHER     1-AUG-1995     6  as1000 mach check 8e since vms 
   317  SCOVAX::MORTON       11-AUG-1995    19  test and memtest causes machine
   372   CSC32::HUTMACHER    29-SEP-1995     5  208 machine checks as1000 V6.1-
   374  ANGLIN::HITTENMILLER  4-OCT-1995     1  Need help with Machine Check 24
   380  JULIET::HATTRUP_JA   16-OCT-1995    11  Machine Checks-New Power Supply
   495  TKTVFS::OKUMURA       9-FEB-1996     4  Machine check code "20d"
   502  VIRGIN::SUTTER       15-FEB-1996     1  Pressing halt crashes AS1000 on
   517  TKTVFS::AEBA         23-FEB-1996     0  Machine check manual
   561  VAXRIO::VELASCO      19-APR-1996     2  Help required to troubleshoot a
   585  VIVIAN::C_MCCARTHY   15-MAY-1996     0  machine check code 0x20c
   586   CSC32::D_WHITEHORN  15-MAY-1996     2  Console test machine checks and
   612   CSC32::B_HIBBERT     7-JUN-1996     1  Machine check 205, which PCI de
   631  EEMELI::KARPPINEN    25-JUN-1996     1  machine check in PALmode
   641  STPVNV::voinov       28-JUN-1996     3  Panic (cpu 0): Machine check -_
   647  PRSSOS::FONDI         8-JUL-1996     4  Machine check code 206 !
   857   COL01::HOLZGREVE    18-MAR-1997     3  AlphaServer 1000 machine check 

    Thanks for you input.
    
    The machine check code is 215. I can find the meaning of this code.
    
    Anyway, I may try to solve the problem by swapping some hardware.
    
    
    Thanks,
    Jimmy Wong

    It's actually the bugcheck code that is 215. You can find out what
    the machine check code is using Decevent ($ diagnose).
    Sue

    Hi,
    
    Console message about the machine check is shown below.
    
                             :
                             :
    **** Error log buffers not dumped to SYS$ERRLOG.DMP
    
    **** OpenVMS (TM) Alpha Operating System V7.1     - BUGCHECK ****
    ** Code=00000215: MACHINECHK, Machine check while in kernel mode
    ** Crash CPU:00     Primary CPU: 00    Active CPUs: 00000001
    ** Current Process = <see below> 
    ** Image Name = <see below>
    **** Canceled memory dump, file blocks left = 00000000, Dump PTE
    address = FFE00 
    
    halted CPU 0
    
    halt code = 5
    HALT instruction executed
    PC = ffffffff8007bf28
    
    CPU 0 booting
                             :
                             :
    
    The following combinations of Current Process and Image Name have be
    encountered.
    
    Current Process = AXPVMS_INSTALL
    Image Name = DKA400:[SYS0.SYSCOMMON.][SYSEXE]PCSI$MAIN.EXE
    
    Current Process = AXPVMS_INSTALL
    Image Name = DKA400:[SYS0.SYSCOMMON.][SYSEXE]LIBRARIAN.EXE
    
    Current Process = NULL
    Image Name = <BLANK>
    
    With ref to .2, the machine check code is 215 and the meaning is
    "Machine check while in kernel mode". Am i correct ?
    
    Thanks for all input,
    
    Jimmy Wong
    

   Boot the CD-ROM and get to the $$$ DCL prompt.  Create a system
   dump file in ddcu:[SYS%.SYSEXE]SYSDUMP.DMP of the V7.1 system
   disk.  (Probably ddcu:[SYS0.SYSEXE]SYSDUMP.DMP.)

   The "215" is the bugcheck code for "machinechk" bugcheck.

   What is needed is the machine check code, which is available from
   the error log via DECevent or similar.  

   The last few error log entries can be stored in the system dump file
   during the system crash -- but the dump does not appear to have been
   written, and I am assuming this is a result of the incomplete nature
   of the system upgrade, where the dump file has not been created.

   Once you have a dump, get the CLUE from the dump, and try CANASTA.
   And using DECevent, see of you can find any other similar entries
   in the WRKSYS::MIKASA notes conference, and in COMET.  If you cannot
   locate any previous relevent machine check discussions and if the
   system diagnostics run cleanly, package up the crashdump and log an
   IPMT.

    Hi,
    
    The strange problem was fixed by replacing the CPU module (54-23297-04).
    
    
    Thanks,
    Jimmy