From owner-freebsd-hackers Wed Feb 5 21:21:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA09963 for hackers-outgoing; Wed, 5 Feb 1997 21:21:01 -0800 (PST) Received: from whale.gu.kiev.ua (proxy.gu.kiev.ua [194.93.190.4]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA09907; Wed, 5 Feb 1997 21:20:49 -0800 (PST) Received: from creator.gu.kiev.ua (stesin@creator.gu.kiev.ua [194.93.190.3]) by whale.gu.kiev.ua (8.8.5/8.7.3) with SMTP id HAA34766; Thu, 6 Feb 1997 07:20:42 +0200 Date: Thu, 6 Feb 1997 07:20:42 +0200 (EET) From: Andrew Stesin X-Sender: stesin@creator.gu.kiev.ua To: questions@freebsd.org, hackers@freebsd.org Subject: Strange(!!) sio callin/callout behaviour in 2.1.6 Message-ID: X-NCC-RegID: ua.gu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, sorry if I'm way too outdated with this, but here the question goes... the system is FreeBSD 2.1.6-RELEASE, installed back in mid-November. sio devices are: com1, com2, and a MOXA 4-port multiport board. I observe the following misbehaviours with regard to sio driver: 1. pppd never seems to receive/handle a SIGHUP from modem. 2. Callout devices behavior screwed... example: say I take the sio unit 5, getty active on ttyd5, TR LED on modem is on, then: # stty -a -f /dev/ttyd5 [...a screen of stty's output goes here, Ok...] # stty -a -f /dev/cuaa5 stty: /dev/cuaa5: Device busy # cu -l /dev/cuaa5 -s 57600 cu: /dev/cuaa5: Line in use # Is it just me so stupid or tired, or a problem _do_ exist with either software or hardware? Would anyone be so keen to suggest a fix? (The above makes the system virtually unusable for the purpose it was installed for...) Thanks! -- Best, Andrew Stesin nic-hdl: ST73-RIPE