On a SMP slink system with a 2.2.10 kernel I am logging the following from mgetty. The "Interrupted system call" makes me think this is not just a chat script problem.
I am not sure what I should be looking at to fix the problem. If mgetty is not run minicom works fine to dial out. /var/log/mgetty/mg_ttyS1.log -- 08/12 19:31:33 yS1 mgetty: experimental test release 1.1.20-Jan17 08/12 19:31:33 yS1 check for lockfiles 08/12 19:31:33 yS1 locking the line 08/12 19:31:33 yS1 lowering DTR to reset Modem 08/12 19:31:34 yS1 send: \d\da\da\daatz[0d] 08/12 19:31:36 yS1 waiting for ``OK'' 08/12 19:31:56 yS1 timeout in chat script, waiting for `OK' 08/12 19:31:56 yS1 init chat timed out, trying force-init-chat 08/12 19:31:56 yS1 send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d] 08/12 19:32:00 yS1 waiting for ``OK'' 08/12 19:32:20 yS1 timeout in chat script, waiting for `OK' 08/12 19:32:20 yS1 init chat failed, exiting...: Interrupted system call 08/12 19:32:20 ##### failed in mg_init_data, dev=ttyS1, pid=350 -- 08/12 19:32:20 yS1 mgetty: experimental test release 1.1.20-Jan17 08/12 19:32:20 yS1 check for lockfiles 08/12 19:32:20 yS1 locking the line 08/12 19:32:21 yS1 lowering DTR to reset Modem 08/12 19:32:21 yS1 send: \d\da\da\daatz[0d] 08/12 19:32:23 yS1 waiting for ``OK'' 08/12 19:32:43 yS1 timeout in chat script, waiting for `OK' 08/12 19:32:43 yS1 init chat timed out, trying force-init-chat 08/12 19:32:43 yS1 send: \d[10][03]\d\d 08/12 19:32:45 ##### failed dev=ttyS1, pid=351, got signal 15, exiting rob [EMAIL PROTECTED]
