| I have seen this problem before. In my instance it turned out that the
console terminal (VT###) was throwing out a strange escape sequence
or break key. My suggestion is to swap the terminal if possible. If you
do not have a spare, just disconnect the console cable from the
bulkhead. I do not suggest running this way very long, only for
troubleshooting purposes. Customer should understand. Good luck..
|
| Please pardon my tardiness in replying...
I'd start by looking at the PC and seeing where in the VMS exec the
halt is located.
We had a spate of halts like this on one of our VAX 7630 systems, where
it would just halt with no dump, no message, nothing. The PC, however,
was located in the area of VMS that would be trying to load the
bugcheck module. It turned out that what was happening was that VMS
was trying to crash, but it could not (for some never discovered
reason) load the bugcheck module. I don't recall what was done to
resolve the situation, however.
Someone in support or in VMS was able to supply a new EXECEPTION.EXE
module which would printout some potentially useful information in this
type of situation, but as it happened, we never had a problem while
running that module.
Just for grins, you might try performing the manual crash dump
procedure:
>>> E PSL ! Get the Processor Status
>>> E ISP ! Get the Interrupt Stack Pointer
>>> E PC ! Get the contents of the PC
>>> D PC FFFFFFFF ! Invalidate the PC
>>> D PSL 41F0000 ! Force Interrupt Stack and IPL=31
>>> C ! Continue [and crash]
Stu
|