[an error occurred while processing this directive]

HP OpenVMS Systems

ask the wizard
Content starts here

Forcing Console VAXstation/MicroVAX Crash?

» close window

The Question is:

 
Recently replaced the disk drive in a VAX 4000-60 due to disk space
concerns. The image backup was restored to the RZ29(4.3Gb) disk w/o errors.
The system booted and ran for 48 hours and then, apparently hung. It has no
mouse movement or keyboard access.
It can't be pinged from other systems. It also isn't collecting any data
during this period. After performing a cold boot, the VAX ran without
incident for approx. 45 days, then hung again a few days ago. It seems
almost impossible to troubleshoot since t
he system can't be accessed. I've heard a 'forced crash' procedure can
sometimes lead to the problem area. I'm not sure how to perform this or if
this will show anything. Any suggestions on a better utility to point me in
the right direction? Any help wou
ld be appreciated.
 
John
 


The Answer is :

 
  Please contact your hardware support organization for assistance,
  this appears to be a hardware problem.
 
  Check the SCSI bus configuration for problems including an overly
  long cable, termination problems, and device firmware revisions.
 
  For information on forcing a crash from the system console, please see:
 
http://www.openvms.digital.com:8000/72final/6017/6017pro_011.html#perf_crash
 
  HALT the system, and enter the following at the console prompt, logging
  the responses:
 
        E/G F               ! Get the PC
        E PSL               ! Examine PSL to determine IPL level
        E/I 0               ! Examine Stack Pointers - Kernel
        E +                 !                        - Exec
        E +                 !                        - Super
        E +                 !                        - User
        E +                 !                        - Interrupt
        E/G/N:F R0          ! Get contents of R0-R15
        D PC FFFFFFFF       ! Invalidate the PC
        D PSL 041F0000      ! Interrupt stack, IPL 31
        C                   ! Force an INVEXCEPTN Bugcheck
 
  Also check the firmware for the VAXstation 4000 model 60, to ensure
  that it is current.
 

answer written or last revised on ( 5-AUG-1999 )

» close window