mgetty-failed in mg_init_data

[Juraj Koppel]

Srdecne zdravim zo zasnezenych Kosic,

mam urcity problem s modemami. Asi raz za mesiac ostanu visiet a neda sa
na nich dovolat, musim ich manualne vypnut a zapnut, aby nabehli.
Experimentoval som s inicializaciou, force-init, dtr on, ale nepomohlo
to. Problemy su rovnake aj po upgrade z RH 4.2 na 5.2. Prikladam vypis z
konfiguracie a prislusnu cast log.
Dakujem vopred za pomoc
Juraj Koppel


# Microcom DeskPorte 28.8P
port ttyS0
  debug 3
  rings 2
  speed 115200
  data-only y
  init-chat "" AT&F OK AT%E1X3S0=0 OK
  force-init-chat "" AT&D3 OK ATZ OK
-----------------
# Welltronix WM-3314ARM
port ttyS1
  debug 3
  speed 115200
  rings 2
  data-only y
  init-chat "" ATZ1 OK AT%E2X3W1S0=0 OK
  force-init-chat "" ATZ "" ATZ1 ""

log:
01/25 08:53:16 yS0  mgetty: experimental test release 1.1.14-Apr02
01/25 09:12:47 yS0  timeout in chat script, waiting for `RING'
01/25 09:12:47 yS0  huh? Junk on the line?
--
01/25 09:12:47 yS0  mgetty: experimental test release 1.1.14-Apr02
01/25 09:13:08 yS0  timeout in chat script, waiting for `OK'
01/25 09:13:08 yS0  init chat timed out, trying force-init-chat
01/25 09:13:28 yS0  timeout in chat script, waiting for `OK'
01/25 09:13:28 yS0  init chat failed, exiting...: Interrupted system
call
01/25 09:13:28 ##### failed in mg_init_data, dev=ttyS0, pid=32433
-------------------------------
01/25 08:22:43 yS1  mgetty: experimental test release 1.1.14-Apr02
01/25 09:22:55 yS1  Warning: got alarm signal!
01/25 09:22:55 yS1  mdm_read_byte: read returned -1: Interrupted system
call
01/25 09:22:55 yS1  mdm_get_line: cannot read byte, return: Interrupted
system call
01/25 09:23:05 yS1  Warning: got alarm signal!
01/25 09:23:05 yS1  mdm_read_byte: read returned -1: Interrupted system
call
01/25 09:23:05 yS1  mdm_get_line: cannot read byte, return: Interrupted
system call
01/25 09:23:05 yS1  modem on dev=ttyS1 doesn't react!: Interrupted
system call
--
01/25 09:23:05 yS1  mgetty: experimental test release 1.1.14-Apr02
01/25 09:23:27 yS1  timeout in chat script, waiting for `OK'
01/25 09:23:27 yS1  init chat timed out, trying force-init-chat
01/25 09:23:47 yS1  timeout in chat script, waiting for `OK'
01/25 09:23:47 yS1  init chat failed, exiting...: Interrupted system
call
01/25 09:23:47 ##### failed in mg_init_data, dev=ttyS1, pid=32449