Conference wonder::turbolaser

1077.0. "OpenVMS V6.2 - Opa0: Hang" by JOBURG::BARNES () Tue Jan 28 1997 06:58

    	Cross posted in VAXAXP::VMSNOTES
    
A customer is having a problem with their console on a
Turbolaser 8400 5/300 running OpenVMS V6.2.

The console recieves and displays OPCOM messages,
but they are unable to log into the system from the
console. Powering off the console does not help either.

The only way around is to reboot the system, which 
they are not too keen to do an a regular basis, just to
free up the console.

The console device is a VT510, with V2.1 firmware.

They have replaced the console with another VT510, but
they have exactly the same problem.

I have suggested they try a VT420 or VT320 to see if they 
have the same problem.

OPA0 is logging errors, but there are no entries in the
errorlog.

ALPOPDR02_062 patch kit has been installed.

The following info has been extracted from their system:

PEP001::SYSTEM $ sh term opa0:
Terminal: _OPA0:      Device_Type: VT200_Series  Owner: Not Available

   Input:    9600     LFfill:  0      Width:  80      Parity: None
   Output:   9600     CRfill:  0      Page:   24

Terminal Characteristics:
   Interactive        Echo               Type_ahead         No Escape
   No Hostsync        TTsync             Lowercase          Tab
   Wrap               Scope              No Remote          Eightbit
   Broadcast          No Readsync        No Form            Fulldup
   No Modem           No Local_echo      No Autobaud        No Hangup
   No Brdcstmbx       No DMA             No Altypeahd       Set_speed
   No Commsync        Line Editing       Overstrike editing No Fallback
   No Dialup          No Secure server   No Disconnect      No Pasthru
   No Syspassword     No SIXEL Graphics  No Soft Characters No Printer Port
   Application keypad ANSI_CRT           No Regis           No Block_mode
   Advanced_video     Edit_mode          DEC_CRT            DEC_CRT2
   No DEC_CRT3        No DEC_CRT4        No DEC_CRT5        No Ansi_Color
   VMS Style Input

PEP001::SYSTEM $

        Image Identification Information

                image name: "OPCOM"
                image file identification: "X-7"
                image file build identification: "X61Q-SSB-0000"
                link date/time:  4-MAY-1995 22:49:08.48
                linker identification: "A11-12"

        Image Identification Information

                image name: "OPDRIVER"
                image file identification: "X-1"
                image file build identification: "X61Q-SSB-1100"
                link date/time: 24-OCT-1995 18:17:09.21
                linker identification: "A11-12"

PEP001::SYSTEM $ sh err
Device                           Error Count
PEP001$OPA0:                            11

Thanks for any suggestions to overcome this problem.

Les Barnes,
Digital Services Division
Johannesburg

I have seen CPU modules, at least twice, with failure modes where the 
TX works and the RX is broken on the UART.

    I found the problem to be an un-supported piece of software
    called Watcher V2.8, dated 1993, similar to ZAP.
    
    I advised the customer to remove OPA0: from the configuration
    file of the Software.
    
    Thanks and Regards,
    
    Les Barnes.