interesting behavior/problem

David Vrona (dave@sashimi.wwa.com)
Sun, 20 Mar 1994 00:44:55 +0100


Hi all,

I recently got a call from a user that reported that the dialup lines kept
ringing with no answer.  I checked the situation and found that the first 4
lines were being used by inbound calls but the 5th line wasn't answering the
phone.  It just kept ringing.....

Here is the associated section of the mgetty log file.  This is v0.18 with
8 1496E modems at 6.10, and Dell SVR4.


03/19 03:12:17  ioctl TCGETX: Bad address
03/19 12:16:40 ##### data dev=termi1E, pid=16584, caller=none, conn='14400/ARQ/V42b', name='', cmd='/bin/login', user='unagual'

--
03/19 12:17:29  ioctl TCGETX: Bad address
--
03/19 12:49:09  ioctl TCGETX: Bad address
03/19 12:50:13  timeout in chat script, waiting for `OK': Interrupted system call
--
03/19 12:50:15  ioctl TCGETX: Bad address
03/19 12:51:19  timeout in chat script, waiting for `OK': Interrupted system call
--
03/19 12:51:21  ioctl TCGETX: Bad address
03/19 12:52:25  timeout in chat script, waiting for `OK': Interrupted system call



This basically goes on forever.  I fixed it by cycling modem power.

Oh, BTW, the ioctl TCGETX message seems to be "normal".  In other words, I have
been using v0.18 on 8 lines for quite a while like this.

Any ideas?  Are the 1496E modems known to lock up once in a while?

dave

-- 
 David Vrona N9QNZ           +1 708 367 1870 (voice)  Internet: dave@wwa.com
 Computing Engineers Inc.    +1 708 367 1871 (data)  +1 708 367 1872 (fax)
 Home of WorldWide Access (SM), Internet services for the Chicagoland area.
 Send e-mail to info@wwa.com for information, or call +1 708 367 1871 (data).