very rare problem with mgetty...
Ramon Fernandez (woody@ieeesb.etsit.upm.es)
Tue, 24 Aug 1999 13:28:34 +0200
After reading the FAQ, I haven't been able to solve my problem.
"mgetty" won't answer the phone (the modem works!), and I get
whese weird messages on the "syslog" console:
Aug 24 12:54:58 filemon mgetty[6483]: init chat failed, exiting...: Interrupted system call
Aug 24 12:54:58 filemon mgetty[6483]: failed in mg_init_data, dev=ttyS1, pid=6483
And this is what I get with debug level 9 in /var/log/mgetty/mg_ttyS1.log
08/24 12:56:30 yS1 mgetty: experimental test release 1.1.20-Jan17
08/24 12:56:30 yS1 mgetty.c compiled at Apr 5 1999, 18:57:40
08/24 12:56:30 yS1 user id: 0, parent pid: 1
08/24 12:56:30 yS1 reading configuration data for port 'ttyS1'
08/24 12:56:30 yS1 reading /etc/mgetty/mgetty.config...
08/24 12:56:30 yS1 conf lib: read: 'debug 9'
08/24 12:56:30 yS1 conf lib: read: 'speed 38400'
08/24 12:56:30 yS1 conf lib: read: 'port ttyS1'
08/24 12:56:30 yS1 section: port ttyS1, **found**
08/24 12:56:30 yS1 conf lib: read: 'speed 57600'
08/24 12:56:30 yS1 conf lib: read: 'switchbd 19200'
08/24 12:56:30 yS1 key: 'speed', type=0, flags=2, data=38400
08/24 12:56:30 yS1 key: 'switchbd', type=0, flags=3, data=19200
08/24 12:56:30 yS1 key: 'direct', type=3, flags=1, data=FALSE
08/24 12:56:30 yS1 key: 'blocking', type=3, flags=1, data=FALSE
08/24 12:56:30 yS1 key: 'port-owner', type=1, flags=1, data=root
08/24 12:56:30 yS1 key: 'port-group', type=1, flags=1,
data=dialout
08/24 12:56:30 yS1 key: 'port-mode', type=0, flags=1, data=432
08/24 12:56:30 yS1 key: 'toggle-dtr', type=3, flags=1, data=TRUE
08/24 12:56:30 yS1 key: 'toggle-dtr-waittime', type=0, flags=1,
data=500
08/24 12:56:30 yS1 key: 'data-only', type=3, flags=1, data=FALSE
08/24 12:56:30 yS1 key: 'fax-only', type=3, flags=1, data=FALSE
08/24 12:56:30 yS1 key: 'modem-type', type=1, flags=1, data=auto
08/24 12:56:30 yS1 key: 'modem-quirks', type=0, flags=0,
data=(empty)
08/24 12:56:30 yS1 key: 'init-chat', type=2, flags=1, data=
\dATQ0V1H0 OK AT O
K
08/24 12:56:30 yS1 key: 'force-init-chat', type=2, flags=1, data=
\d^P^C\d\d\d
+++\d\d\d^M\dATQ0V1H0 OK
08/24 12:56:30 yS1 key: 'post-init-chat', type=2, flags=0,
data=(empty)
08/24 12:56:30 yS1 key: 'modem-check-time', type=0, flags=1,
data=3600
08/24 12:56:30 yS1 key: 'rings', type=0, flags=2, data=1
08/24 12:56:30 yS1 key: 'msn-list', type=2, flags=0, data=(empty)
08/24 12:56:30 yS1 key: 'get-cnd-chat', type=2, flags=0,
data=(empty)
08/24 12:56:30 yS1 key: 'cnd-program', type=1, flags=0,
data=(empty)
08/24 12:56:30 yS1 key: 'answer-chat', type=2, flags=1, data= ATA
CONNECT \c
08/24 12:56:30 yS1 key: 'answer-chat-timeout', type=0, flags=1,
data=80
08/24 12:56:30 yS1 key: 'autobauding', type=3, flags=1, data=FALSE
08/24 12:56:30 yS1 key: 'ringback', type=3, flags=1, data=FALSE
08/24 12:56:30 yS1 key: 'ringback-time', type=0, flags=1, data=30
08/24 12:56:30 yS1 key: 'ignore-carrier', type=3, flags=1,
data=FALSE
08/24 12:56:30 yS1 key: 'issue-file', type=1, flags=2,
data=/etc/issue.modem
.
.
.
08/24 12:56:30 yS1 check for lockfiles
08/24 12:56:30 yS1 checklock: stat failed, no file
08/24 12:56:30 yS1 locking the line
08/24 12:56:30 yS1 makelock(ttyS1) called
08/24 12:56:30 yS1 do_makelock: lock='/var/lock/LCK..ttyS1'
08/24 12:56:30 yS1 lock made
08/24 12:56:30 yS1 tio_get_rs232_lines: status: RTS CTS DSR DTR
08/24 12:56:30 yS1 lowering DTR to reset Modem
08/24 12:56:31 yS1 tss: set speed to 38400 (017)
08/24 12:56:31 yS1 tio_set_flow_control( HARD )
08/24 12:56:31 yS1 waiting for line to clear (VTIME), read:
08/24 12:56:31 yS1 send: \dATQ0V1H0[0d]
08/24 12:56:31 yS1 waiting for ``OK''
08/24 12:56:31 yS1 got: AT0
08/24 12:56:51 yS1 timeout in chat script, waiting for `OK'
08/24 12:56:51 yS1 init chat timed out, trying force-init-chat
08/24 12:56:51 yS1 send:
\d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
08/24 12:56:55 yS1 waiting for ``OK''
08/24 12:56:55 yS1 got: [10][03]++[0d]
08/24 12:56:55 yS1 CND: AT0__++4[0d]
08/24 12:56:55 yS1 CND: 4
08/24 12:56:55 yS1 CND: ELink caller ID: '4'ATV
I've tried to downgrade mgetty to 1.1-18, but doesn't work either.
Any idea?
Thanks in advance
--
Ramón Fernández Marina <r.fernandez@ieee.org>
IEEE Student Member
1999 Vice-Chair at ETSIT-Madrid IEEE Student Branch