Re: VAX ODT console fault

2019-06-12 Thread Jon Elson via cctalk

On 06/12/2019 03:41 AM, r.stricklin via cctalk wrote:

If I install a spare KA630-A and 8 MB memory board, I get a similar fault where 
chevrons repeat to infinity.
There are a couple possibilities.  If the baud rate is set 
wrong, the VAX could be replying to some gibberish at wrong 
baud rate, that causes the terminal to reply to that with 
something, and they endlessly jabber at each other.  Most 
terminals will send Xoff/Xon when a rapid burst of 
characters comes into the Rx port.  When misinterpreted by 
the VAX, that might cause it to send another burst of 
characters.  So, it could be entirely a software/setup issue.


Are you using a real terminal or a PC terminal program?  If 
a program, you might try a different one or try different 
comm settings.


As someone else mentioned, a leaking battery could have 
damaged traces or the baud selector switch on the panel 
interface module. Close inspection of that is strongly advised.


Jon




Re: VAX ODT console fault

2019-06-12 Thread Glen Slick via cctalk
On Wed, Jun 12, 2019, 5:13 AM r.stricklin via cctalk 
wrote:

>
> On Jun 12, 2019, at 1:25 AM, r.stricklin wrote:
>
> > I have a BA23 VAX of unknown provenance, which tonight I moved from the
> project backlog to the workbench. It comes up and passes selftest. But any
> key I press on the console terminal is repeated a couple dozen times (to
> the limit of the input line length?). This makes it impossible to interact
> with ODT.
>
> If I install a spare KA630-A and 8 MB memory board, I get a similar fault
> where chevrons repeat to infinity. This seems to suggest it's a fault
> between the CPU and my terminal. Can this be the result of a bulkhead or
> other cable problem?
>
> KA630-A.V1.3
>
> Performing normal system tests.
>
>   7..6..5..4..3..
>
> Tests completed.
>
>
> Loading system software.
>
>   2..
> ?40 NOSUCHDEV
> ?06 HLT INST
> PC = 0EE6
> Failure.
> >>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> (etc.)
>
>
>
> ok
> bear.
>
> --
> until further notice
>


Is the NVRAM battery still in place in the console bulkhead panel? Those
always go bad and leak over time. Even it was removed some time ago my
first guess would be battery corrosion on the bulkhead panel is causing the
problem if it happens with multiple CPU boards.


Re: VAX ODT console fault

2019-06-12 Thread r.stricklin via cctalk


On Jun 12, 2019, at 1:25 AM, r.stricklin wrote:

> I have a BA23 VAX of unknown provenance, which tonight I moved from the 
> project backlog to the workbench. It comes up and passes selftest. But any 
> key I press on the console terminal is repeated a couple dozen times (to the 
> limit of the input line length?). This makes it impossible to interact with 
> ODT.

If I install a spare KA630-A and 8 MB memory board, I get a similar fault where 
chevrons repeat to infinity. This seems to suggest it's a fault between the CPU 
and my terminal. Can this be the result of a bulkhead or other cable problem?

KA630-A.V1.3

Performing normal system tests.

  7..6..5..4..3..

Tests completed.


Loading system software.

  2..
?40 NOSUCHDEV
?06 HLT INST
PC = 0EE6
Failure.
>>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >  > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 
>>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > >
(etc.)



ok
bear.

-- 
until further notice



VAX ODT console fault

2019-06-12 Thread r.stricklin via cctalk
Folks;

I have a BA23 VAX of unknown provenance, which tonight I moved from the project 
backlog to the workbench. It comes up and passes selftest. But any key I press 
on the console terminal is repeated a couple dozen times (to the limit of the 
input line length?). This makes it impossible to interact with ODT.

Is this a normal sort of well-understood failure mode? In this session excerpt, 
the only thing I am sending is  (giving me the normal chevron prompt), 
 (giving me the repeated chevrons, sometimes with other characters in 
the pattern), ?, and h. I did not type any colons at the [XQA0] prompt, though 
I did try to backspace them. The behavior is the same if I remove all boards 
besides the KA655-B and 16 MB memory board.


KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
Loading system software.
No default boot device has been specified.

Available devices.
-DUA0 (RA81)
-DUA1 (RA81)
-XQA0 (08-00-2B-19-A2-D7)
-XQB0 (08-00-2B-0D-83-C0)

Device? [XQA0]: : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 
: : : : : : : : \ \\
?26 VAL TOO LRG
Device? [XQA0]:

(BOOT/R5:0 XQA0)



  2..
-XQA0
?4B CTRLERR, XQA0
?06 HLT INST
PC = 0C1A
Failure.
>>>A0
?22 ILL CMD
>AAAAAAAAAAAAAAAA>>^C
>>>
?22 ILL CMD
>>>
>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>
?22 ILL CMD
>>>
>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>
?22 ILL CMD
>>>
>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>^C
>>>
>>>
>>
?22 ILL CMD
>>>
>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>^C
>>>
?22 ILL CMD
>>>
>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>?2>>>\>\\^C
>>>
>>>
>>
?22 ILL CMD
>>>


ok
bear.

-- 
until further notice