Attempts to connect to my Yeeloong via ssh from an i386 client still
hang. I'm not getting any console messages, but that may be a side
effect from my 'amd' investigation.
The symptoms from the client end remain the same. The server prompts
for password and no further operations are possible on the client end.
the client terminal is locked into an unresponsive network connection.
The usual "~." doesn't work. In a graphical environment, one must
destroy the window. (I haven't tried from a non-graphical client, but
I expect one must log in to the client from elsewhere and kill the
Below are what may be relevant snippets of ktruss output generated with
'sudo ktruss -i -p <pid> | tee sshd.ktruss'. In this instance, the PID
of the master sshd process was 630. There were no messages relevant
to this logged in /var/log/messages.
The output is some different than before. Before, I saw a distinct
pattern of user-after-close. This time, an attempt is made to close
a file descriptor of -1 (0xffffffff)
I killed the client window and tried again. This time there are
messages about "tcgetattr: Bad file descriptor", but their PIDs don't
match the recorded session. I'll have to try again later and see if
anything is different.
|/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X
|\ / jdbaker[snail]mylinuxisp[flyspeck]com OpenBSD FreeBSD
| X No HTML/proprietary data in email. BSD just sits there and works!
|/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645