Re: Ethernet not so good.
> cat /proc/interrupts some times before and after the telnet attempt.
OK - before initiating telnet out...
auto 0: 0 spurious int
auto 1: 1731127 L VIA1 Dispatch
auto 2: 44849 L VIA2 Dispatch
auto 3: 0 L PSC Dispatch
auto 4: 224151 L PSC Dispatch
auto 5: 0 L PSC Dispatch
auto 6: 0 L PSC Dispatch
auto 7: 0 L NMI
via1 9: 631722 console/cursor
via1 10: 64759 adb CUDA interrupt
via1 14: 1047058 timer
via2 17: 1731498 F Nubus Dispatch
via2 19: 44478 Mac ESP SCSI
psc 33: 224151 SCC A
psc 34: 0 SCC B
nbus 60: 372 8390 Ethernet
and after forcing session to close
auto 0: 0 spurious int
auto 1: 1801692 L VIA1 Dispatch
auto 2: 45042 L VIA2 Dispatch
auto 3: 0 L PSC Dispatch
auto 4: 250517 L PSC Dispatch
auto 5: 0 L PSC Dispatch
auto 6: 0 L PSC Dispatch
auto 7: 0 L NMI
via1 9: 655028 console/cursor
via1 10: 73329 adb CUDA interrupt
via1 14: 1085797 timer
via2 17: 1802105 F Nubus Dispatch
via2 19: 44629 Mac ESP SCSI
psc 33: 250517 SCC A
psc 34: 0 SCC B
nbus 60: 414 8390 Ethernet
now trying a telnet in (from elsewhere on home ether)
(console shows in.telnetd connect msg,
telnetd: ttloop: peer died -- when I force close on remote)
auto 0: 0 spurious int
auto 1: 1847166 L VIA1 Dispatch
auto 2: 45153 L VIA2 Dispatch
auto 3: 0 L PSC Dispatch
auto 4: 272988 L PSC Dispatch
auto 5: 0 L PSC Dispatch
auto 6: 0 L PSC Dispatch
auto 7: 0 L NMI
via1 9: 669359 console/cursor
via1 10: 80694 adb CUDA interrupt
via1 14: 1109616 timer
via2 17: 1847604 F Nubus Dispatch
via2 19: 44715 Mac ESP SCSI
psc 33: 272988 SCC A
psc 34: 0 SCC B
nbus 60: 439 8390 Ethernet
---
In both telnet experiments, I get a term msg that I've connected to the
remote. Even get login prompt for outbound test. There is some unrelated
activity on the local network -- don't know if that would bias the
numbers, too.
Thanks for your continued help, Michael! I'm still feeling very new to
alot of this and very much appreciate your time and suggestions!
Lon
Reply to: