This is Help:-Getty-lock-ups-on-serial-lines in view mode; [Up]
Date: Sun 13-Jul-1991 02:23:37 From: michael@makaha.cs.ucla.edu (michael gersten) Subject: Help: Getty lock ups on serial lines Help. My getty's are locking up on my serial lines. By locking up, I mean not doing anything, even if I do a kill -9 (they don't die). pin cable, a null modem adapter, and then another 25 to 25 pin cable (the second machine is a 3b1). I have tried this with the NeXT running a getty, on both the flow control and non-flow control serial lines. I have tried this at 9600 and 19200. On the 3b1 side I've tried not running any program except cu (so that presence of dtr/carrier detect corresponds to activity on the line), and I've also tried it with uugetty -r active (so that there is always carrier present except to hang up). The getty will lock up, consistently, in less than a day. Right now every time I want to remote log into the NeXT I have to reboot it. This is not a livable situation for me. Since the machine is a student discount, NeXT will not help me with tech support. Any ideas? Has anyone else seen this situation? Is everyone else using Ethernet to hook NeXT's to other computers? Do I have broken hardware? Michael o.s. is 2.0. 2.1 is on order, not received yet. Additional note: When the getty locks up and will not die, the system will not reboot properly. If I try the reboot command, or if I bring up the reboot window and select r, I get some disk activity, then silence; I can still bring up any of the special windows, and if I try the reboot window twice in a row, the second one does reboot, but does not mark the file system clean.
Date: Sun 13-Jul-1991 08:05:45 From: masaru@media-lab.media.mit.edu (Masaru Sugai) Subject: Re: Help: Getty lock ups on serial lines In article <1991Jul13.022337.7353@cs.ucla.edu> michael@makaha.cs.ucla.edu (michael gersten) writes: > >Help. My getty's are locking up on my serial lines. By >locking up, I mean not doing anything, even if I do >a kill -9 (they don't die). > >Condition: I have two machines connected by a 8pin to 25 >pin cable, a null modem adapter, and then another 25 to 25 >pin cable (the second machine is a 3b1). I have tried this >with the NeXT running a getty, on both the flow control and >non-flow control serial lines. I have tried this at 9600 and >19200. On the 3b1 side I've tried not running any program except >cu (so that presence of dtr/carrier detect corresponds to activity >on the line), and I've also tried it with uugetty -r active (so >that there is always carrier present except to hang up). I experienced a similar situation when I was writing a 3-d program which used a 3d input device (3D ISO-CUBE) over serial line. My program was launched by inetd server as soon as connection request arrived from remote machine. For debugging purpose, I used telnet to check if it was working, and sometimes my 3d server program became an immortal zombie. I used Mac cable, and input device does not use RTS/CTS. I tried several ioctl calls, but problem has remained unsolved. >This is not a livable situation for me. Since the machine is a >student discount, NeXT will not help me with tech support. Really ? I don't think they discriminate you due to the academic discount. Rather it's quite difficult to isolate the problem from surroudings though. >Any ideas? Has anyone else seen this situation? Is everyone else >using Ethernet to hook NeXT's to other computers? Do I have >broken hardware? > > Michael >o.s. is 2.0. 2.1 is on order, not received yet. Here are my configurations. NeXTslab 8MB/400 SYSTEM 2.0 I have 2.1 upgrade package handy, but i haven't tried as of yet. >Additional note: When the getty locks up and will not die, the >system will not reboot properly. If I try the reboot command, or >if I bring up the reboot window and select r, I get some disk >activity, then silence; I can still bring up any of the special >windows, and if I try the reboot window twice in a row, the second >one does reboot, but does not mark the file system clean. I was obliged to enter ROM monitor as /etc/shutdown waited for the death of that process indefinetely. I simply gave up inetd implementations, but some guys might have encountered the same situlation while using SLIP.
Date: Sun 13-Jul-1991 14:47:49 From: louie@sayshell.umd.edu (Louis A. Mamakos) Subject: Re: Help: Getty lock ups on serial lines In article <1991Jul13.080545.13744@news.media.mit.edu> masaru@media-lab.media.mit.edu (Masaru Sugai) writes: >Here are my configurations. > NeXTslab 8MB/400 SYSTEM 2.0 >I have 2.1 upgrade package handy, but i haven't tried as of yet. You really should upgrade to Release 2.1, as I understand that there were fixes to the serial driver in that version which fixed some serious bugs. Perhaps you're experiencing one of those bugs? louie
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.