init chat failed, exiting...: Interrupted system

Marcus Mascari (mascarim@yahoo.com)
Mon, 14 Sep 1998 17:07:24 +0200
Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hello,

We have been using mgetty+sendfax official release
1.0.0 for some time now without flaw.  mgetty is being
used for both dialin (CSLIP), fax in, and fax out
services.  However, dialin services have started to
leave the modem in a non-recoverable state since we
upgraded the Linux Kernel from 2.0.33 to 2.0.35 to
support other hardware (Adaptec SCSI II UltraWide
contoller).  Since that time, the following activity
has occurred with the modem:

...
09/12 09:20:51 yS3  send: ATA[0d]
09/12 09:20:51 yS3  waiting for ``CONNECT'' ** found **
09/12 09:21:08 yS3  send:
09/12 09:21:08 yS3  waiting for ``
'' ** found **
09/12 09:21:10 ##### data dev=ttyS3, pid=12483, caller=none,
conn='38400', name=
'', cmd='/bin/login', user='dialin'

--
09/12 10:48:38 yS3  mgetty: official release 1.0.0
09/12 10:48:38 yS3  check for lockfiles
09/12 10:48:38 yS3  locking the line
09/12 10:48:39 yS3  lowering DTR to reset Modem
09/12 10:48:39 yS3  send: \dATQ0V1H0[0d]
09/12 10:48:40 yS3  waiting for ``OK''
09/12 10:49:00 yS3  timeout in chat script, waiting for `OK'
09/12 10:49:00 yS3  init chat timed out, trying force-init-chat
09/12 10:49:00 yS3  send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
09/12 10:49:04 yS3  waiting for ``OK''
09/12 10:49:24 yS3  timeout in chat script, waiting for `OK'
09/12 10:49:24 yS3  init chat failed, exiting...: Interrupted system
call
09/12 10:49:24 ##### failed in mg_init_data, dev=ttyS3, pid=12761     
    
...

Naturally, with mgetty dying, unable to talk to the
modem, init determines that it is respawning too
rapidly:

Sep 14 09:39:33 sdserver init: Id "s4" respawning too fast: disabled
for 5 minut
es
Sep 14 09:57:23 sdserver init: Id "s4" respawning too fast: disabled
for 5 minut
es
Sep 14 10:15:13 sdserver init: Id "s4" respawning too fast: disabled
for 5 minut
es

mgetty is capable of talking to the device
(/dev/ttyS3) for several incoming and outgoing calls
BEFORE the modem dies:

09/10 22:58:51 yS3  mgetty: official release 1.0.0
09/10 22:58:51 yS3  check for lockfiles
09/10 22:58:51 yS3  locking the line
09/10 22:58:52 yS3  lowering DTR to reset Modem
09/10 22:58:52 yS3  send: \dATQ0V1H0[0d]
09/10 22:58:53 yS3  waiting for ``OK'' ** found **
09/10 22:58:53 yS3  send: AT &F S0=0 &D3 &K3 &C1\N2[0d]
09/10 22:58:53 yS3  waiting for ``OK'' ** found **
09/10 22:58:53 yS3  mdm_send: 'AT+FCLASS=2.0' -> ERROR
09/10 22:58:54 yS3  mdm_send: 'AT+FCLASS=2' -> OK
09/10 22:58:54 yS3  mdm_send: 'AT+FCLASS=0' -> OK
09/10 22:58:54 yS3  mdm_send: 'AT+FAA=1;+FCR=1' -> OK
09/10 22:58:54 yS3  mdm_send: 'AT+FBOR=0' -> OK
09/10 22:58:54 yS3  mdm_send: 'AT+FLID="49 30 12345678"' -> OK
09/10 22:58:55 yS3  mdm_send: 'AT+FDCC=1,5,0,2,0,0,0,0' -> OK
09/10 22:58:55 yS3  waiting...
09/10 23:58:55 yS3  checking if modem is still alive
09/10 23:58:55 yS3  mdm_send: 'AT' -> OK

Once the modem dies, however, it cannot be recovered.
However, it does respond to stty:

sdserver:/tmp# stty -a < /dev/ttyS3
speed 38400 baud; rows 0; columns 0; line = 0;
intr = <undef>; quit = ^\; erase = <undef>; kill = ^U; eof = ^D; eol =
<undef>;
eol2 = <undef>; start = ^Q; stop = ^S; susp = <undef>; rprnt = <undef>;
werase = <undef>; lnext = <undef>; flush = <undef>; min = 1; time = 0;
-parenb -parodd cs8 hupcl -cstopb cread clocal crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl
-ixon
-ixoff -iuclc -ixany -imaxbel
-opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0
bs0 vt0
ff0
-isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop
-echoprt -echoctl -echoke

When running seyon against the terminal, seyon doesn't
compain about any I/O errors, but takes about 10
seconds before responsing that it has located the modem.
Seyon reports DSR/DTR/CTS/RTS all on, with Carrier
Detect off.  However, we are unable to talk to the
modem in any way: ATZ does nothing (no echoing of 
characters), +++ does nothing, etc.

Finnaly, when we dial the phone number of the modem,
either via modem, fax, or simply a phone, the line
reports a BUSY signal.  This includes dialing the modem
with the SAME line as the last good CSLIP connection.

Here is our configuration in detail:

Linux 2.0.35
mgetty+sendfax: mgetty: official release 1.0.0

mgetty.config:
debug 4
fax-id 49 30 12345678
speed 38400

(I will up the debug level to 5 before the next reboot)

inittab:

s4:345:respawn:/usr/local/sbin/mgetty ttyS3 vt100

The CSLIP connection is usually dropped by a signal
to DIP on the dialin client:

kill -HUP <dip's pid>

The modem is a Zoom V.32bis faxmodem on /dev/ttyS3 in
a Pentium 200Mhz, 32 MB of RAM, 2 Gig HD, etc.

2 things changed between a perfectly running mgetty
and one which leaves the modem in an unusable state
until the next reboot:

1. Adding of the Adaptec SCSCI II UltraWide controller
2. Upgrade of the Linux Kernel to 2.0.35 from 2.0.33

Any help in this matter would be GREATLY appreciated, 
as the drive to the remote installation is quite a long
one.

Marcus Mascari



_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com