Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!uunet!jarthur!elroy.jpl.nasa.gov!sdd.hp.com!caen!uwm.edu!ogicse!zephyr.ens.tek.com!tektronix!percy!nerd From: nerd@percy.rain.com (Michael Galassi) Newsgroups: comp.sys.next Subject: Re: uucico lock-ups under 2.0 Keywords: uucp, uucico, support Message-ID: <1991Feb26.160009.3836@percy.rain.com> Date: 26 Feb 91 16:00:09 GMT References: <1481@cgh.UUCP> <434@heaven.woodside.ca.us> Organization: Percy's UNIX, Portland, OR. Lines: 27 In article <434@heaven.woodside.ca.us> glenn@heaven.woodside.ca.us (Glenn Reid) writes: >In article <1481@cgh.UUCP> paul@cgh.uucp (Paul Homchick) writes: >>I am having an intermittent problem with uucico lock-ups. Three times >>since installing version 2.0 of Nextstep, I have had uucico lock up >>the serial port. > >> ...Nor does cycling the modem power help. The only way I've >>found to get the port back is to reboot the machine. > >There is a serious bug in the serial driver in 2.0 related to >incoming calls (and uucico). You basically can't receive calls >without wedging the serial port. If you restrict your UUCP traffic >to call-only until this bug is fixed, you shouldn't have any problems >with it locking up. Here is a bit more detail, I was preparing a message for bug_next but since they already know of it... The problem only shows up if you actualy send something to the next in the uucico session, if you poll with nothing to xmit all is OK. Also, in most cases (but not all) you can turn the port off (in /etc/ttys) kill -1 1, turn the port back on and kill -1 1, to have things work again. Not pretty but it sure beats power cycling the machine. -michael -- Michael Galassi | nerd@percy.rain.com MS-DOS: The ultimate PC virus. | ...!tektronix!percy!nerd Brought to you by Super Global Mega Corp .com