[Info-vax] Opa0 in TIMOUT state

[Simon Clubley]

On 2021-07-07, Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP> wrote:
> On 2021-07-07, abrsvc <dansabrservices at yahoo.com> wrote:
>> Anyone seen this before?  I have a customer with the terminal device in TIMOUT state.  I've not seen this before nor can I figure out how it got into this state. It does not seem to impact the system at all other than showing increasing errors for  the device every time a reply message is received by the console.
>>
>> Ideas?
>>
>
> Never seen _that_ one before. :-)
>
> What's the allocation status and reference count for OPA0: ?
>
> Can you post a $ show device opa0: ?
>
> Has someone been playing with opening OPA0: directly while SHARE
> privilege was enabled ?
>
> What are the terminal settings for OPA0: ? Could modem control signals
> come into play for example ? If so, has the cable for OPA0: been damaged ?
>
> What is OPA0: actually connected to ? A dumb terminal or something else ?
>
> I suppose you have tried typing Ctrl-Q on the console just in case ? :-)
>

Another idea:

Have you examined the data structures to locate and view the _input_
buffer for OPA0: ? Is the input buffer full for some reason or does
it have junk in it ?

Simon.

-- 
Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.