Re: [hylafax-users] MultiTech MT5634ZPX-PCI-V92 and Wedging

["Mike McMullen" <mlm@xxxxxxxxxxxxxxxxxx>]

Top posting moved to bottom:
> On 2005.02.18 12:50 Steve Tuckner wrote:
> > Not being a hylafax expert it makes me wonder about how that call
> > ended.
> > There was a problem earlier with the ZPX-PCI and Hylafax where Hylafax
> > would
> > drop DTR instead of hanging up with an ATH. Could this be the issue
> > here?
> >
> > Steve Tuckner
> > Multi-Tech Systems
> >
> > > -----Original Message-----
> > > From: hylafax-users-bounce@xxxxxxxxxxx
> > > [mailto:hylafax-users-bounce@xxxxxxxxxxx]On Behalf Of Mike McMullen
> > > Sent: Friday, February 18, 2005 2:11 PM
> > > To: hylafax-users@xxxxxxxxxxx
> > > Subject: Re: [hylafax-users] MultiTech MT5634ZPX-PCI-V92 and Wedging
> > >
> > >
> > >
> > > ----- Original Message -----
> > > From: "Lee Howard" <faxguy@xxxxxxxxxxxxxxxx>
> > > To: "Mike McMullen" <mlm@xxxxxxxxxxxxxxxxxx>
> > > Cc: <hylafax-users@xxxxxxxxxxx>
> > > Sent: Wednesday, February 16, 2005 9:50 AM
> > > Subject: Re: [hylafax-users] MultiTech MT5634ZPX-PCI-V92 and Wedging
> > >
> > >
> > > > On 2005.02.16 09:35 Mike McMullen wrote:
> > > >
> > > >> I have noticed that right before the wedging occurs, a fax was
> > > >> received
> > > >> that failed with the following message:
> > > >
> > > >>    Received premature V.34 termination.
> > > >>
> > > >> I'm also seeing as I posted yesterday:
> > > >>
> > > >> "Failed to properly detect hight-speed data carrier"
> > > >>
> > > >> And sometimes the modem wedges after that.
> > > >>
> > > >> I've attached the config file for one of the modems. Wedging
> > errors
> > > >> appear with equal frequency on either modem.
> > > >>
> > > >> I can supply logs if someone thinks that would help.
> > > >>
> > > >> Any insight appreciated!
> > > >
> > > > The thing to do would be to see if the modem really is
> > > wedged.  So when
> > > > the modem wedges, without power-cycling the modem or
> > > otherwise changing
> > > > things, run 'minicom -o' on it and see if you can get it to
> > respond
> > > > after a few ATZs or something.  If that doesn't work, then
> > > maybe let
> > > > minicom initialize it (by omitting the -o).  If you can get it to
> > > > respond, then HylaFAX needs some improvement with the
> > > "reset" routine.
> > > > If you can't, then the modem really is hung, and it's
> > > likely a firmware
> > > > issue that MultiTech will need to examine.
> > > >
> > > > The session log that causes the modem to hang/wedge would
> > > be useful in
> > > > assisting you.
> > > >
> > > > Lee.
> > >
> > > Hi Lee/Bill and all other interested parties,
> > >
> > > One of the modems wedged this morning and per your
> > > suggestion,  I turned off
> > > the faxgetty on the modem and removed it from hylafax and ran
> > minicom
> > > on it. Using the speed in the conf.modem file of 56K I was
> > > unable to get
> > > any response at all from the modem.
> > >
> > > I ran it at 38.4K just to cover the bases and no response at
> > > all. So I had to remove the
> > > phone lines, reboot and everything was back to normal.
> > >
> > > An incoming fax attempt failed about 5 times before the modem
> > > wedged. After the
> > > last failed attempt it appears the modem wedged. I've
> > > attached the com log if that
> > > can provide any help.
> > >
> > > Any insight appreciated!
> > >
> > > Mike
> > >
> > >

> Steve,
>
> On both SuperG3 and non-SuperG3 calls HylaFAX sends ATH0 before dropping DTR.  Mike would need to 
> examine his server logs to make sure that it happened in that particular instance, but that's what 
> it's *supposed* to do in 4.2.1, at least.
>
> However, if for some reason ATH0 results with ERROR or no response at all, then it will just move 
> on after 5 seconds.
>
> Lee.

Ok. Different modem wedged this time. For all trying to keep up I have two
ZPX-PCIs. I set server to 0xFFF. A fax came in and got a timeout and failed.
Right after that modem1 wedged. While the com log didn't show anything, looking
at /var/log/messages showed some errors.

First I got a kernel error "LSR safety check engaged!" before FaxGetty reports
"MODEM setBaudRate::tcgetattr: Input/output error".

I assume that is the root of the problem but I have no idea what the kernel error
is stating.

The trace is below. This is a FC2 system running on an a 700 MHZ Athlon circa
2000. Thats when I bought it.

Mike


Feb 18 14:18:14 mail FaxGetty[3343]: MODEM LT V.92 1.0 MT5634ZPX-PCI-U INTERNAL DATA/FAX/VOICE MODEM 
VERSION 1.32I LT V.92 1.0 MT5634ZPX-PCI-U Internal Data/Fax/Voice Modem Version 1.32i/
Feb 18 14:18:14 mail FaxGetty[3343]: <-- [7:ATL0M1\r]
Feb 18 14:18:14 mail FaxGetty[3343]: --> [2:OK]
Feb 18 14:18:14 mail FaxGetty[3343]: <-- [14:AT+F34=14,1,2\r]
Feb 18 14:18:14 mail FaxGetty[3343]: --> [2:OK]
Feb 18 14:18:14 mail FaxGetty[3343]: STATE CHANGE: RECEIVING -> RUNNING (timeout 30)
Feb 18 14:18:14 mail FaxGetty[3343]: MODEM input buffering disabled
Feb 18 14:18:50 mail FaxGetty[3343]: STATE CHANGE: RUNNING -> LISTENING
Feb 18 14:18:50 mail FaxGetty[3343]: MODEM input buffering enabled
Feb 18 14:18:51 mail FaxGetty[3343]: --> [4:RING]
Feb 18 14:18:57 mail FaxGetty[3343]: --> [4:RING]
Feb 18 14:18:57 mail FaxGetty[3343]: STATE CHANGE: LISTENING -> ANSWERING
Feb 18 14:18:57 mail FaxGetty[3343]: MODEM input buffering enabled
Feb 18 14:19:09 mail FaxGetty[3343]: ANSWER: FAX CONNECTION  DEVICE '/dev/modem1'
Feb 18 14:19:53 mail FaxGetty[3343]: <-- [5:ATH0\r]
Feb 18 14:19:53 mail FaxGetty[3343]: --> [2:OK]
Feb 18 14:19:53 mail FaxGetty[3343]: MODEM set DTR OFF
Feb 18 14:19:54 mail FaxGetty[3343]: MODEM set DTR OFF
Feb 18 14:19:54 mail FaxGetty[3343]: DELAY 75 ms
Feb 18 14:19:54 mail FaxGetty[3343]: MODEM set DTR ON
Feb 18 14:19:54 mail FaxGetty[3343]: DELAY 2600 ms
Feb 18 14:19:58 mail FaxGetty[3343]: MODEM set baud rate: 57600 baud, input flow RTS/CTS, output 
flow RTS/CTS
Feb 18 14:19:58 mail FaxGetty[3343]: DELAY 10 ms
Feb 18 14:19:58 mail FaxGetty[3343]: MODEM flush i/o
Feb 18 14:19:58 mail FaxGetty[3343]: <-- [4:ATZ\r]
Feb 18 14:20:00 mail FaxGetty[3343]: --> [2:OK]
Feb 18 14:20:00 mail FaxGetty[3343]: DELAY 3000 ms
Feb 18 14:20:03 mail FaxGetty[3343]: MODEM flush i/o
Feb 18 14:20:03 mail FaxGetty[3343]: <-- [10:AT+VCID=1\r]
Feb 18 14:20:03 mail FaxGetty[3343]: --> [9:AT+VCID=1]
Feb 18 14:20:03 mail FaxGetty[3343]: --> [2:OK]
Feb 18 14:20:03 mail FaxGetty[3343]: <-- [7:ATS0=0\r]
Feb 18 14:20:03 mail FaxGetty[3343]: --> [6:ATS0=0]
Feb 18 14:20:03 mail FaxGetty[3343]: --> [2:OK]
Feb 18 14:20:03 mail FaxGetty[3343]: <-- [5:ATE0\r]
Feb 18 14:20:03 mail FaxGetty[3343]: --> [4:ATE0]
Feb 18 14:20:03 mail FaxGetty[3343]: --> [2:OK]
Feb 18 14:20:03 mail FaxGetty[3343]: <-- [5:ATV1\r]
Feb 18 14:20:03 mail FaxGetty[3343]: --> [2:OK]
Feb 18 14:20:03 mail FaxGetty[3343]: <-- [5:ATQ0\r]
Feb 18 14:20:03 mail FaxGetty[3343]: --> [2:OK]
Feb 18 14:20:03 mail FaxGetty[3343]: <-- [7:ATS8=2\r]
Feb 18 14:20:03 mail FaxGetty[3343]: --> [2:OK]
Feb 18 14:20:03 mail FaxGetty[3343]: <-- [8:ATS7=60\r]
Feb 18 14:20:03 mail FaxGetty[3343]: --> [2:OK]
Feb 18 14:20:03 mail FaxGetty[3343]: <-- [12:AT+FCLASS=?\r]
Feb 18 14:20:03 mail FaxGetty[3343]: --> [19:0,1,1.0,2,2.0,2.1,8]
Feb 18 14:20:03 mail FaxGetty[3343]: --> [2:OK]
Feb 18 14:20:03 mail FaxGetty[3343]: MODEM Supports "Data"
Feb 18 14:20:03 mail FaxGetty[3343]: MODEM Supports "Class 1"
Feb 18 14:20:03 mail FaxGetty[3343]: MODEM Supports "Class 2"
Feb 18 14:20:03 mail FaxGetty[3343]: MODEM Supports "Class 2.0"
Feb 18 14:20:03 mail FaxGetty[3343]: MODEM Supports "Class 1.0"
Feb 18 14:20:03 mail FaxGetty[3343]: MODEM Supports "Class 2.1"
Feb 18 14:20:03 mail FaxGetty[3343]: MODEM Supports "Voice"
Feb 18 14:20:03 mail FaxGetty[3343]: <-- [14:AT+FCLASS=1.0\r]
Feb 18 14:20:03 mail FaxGetty[3343]: --> [2:OK]
Feb 18 14:20:03 mail FaxGetty[3343]: <-- [5:ATI3\r]
Feb 18 14:20:33 mail FaxGetty[3343]: MODEM TIMEOUT: reading line from modem
Feb 18 14:20:33 mail FaxGetty[3343]: <-- [5:ATI0\r]
Feb 18 14:21:03 mail FaxGetty[3343]: MODEM TIMEOUT: reading line from modem
Feb 18 14:21:03 mail FaxGetty[3343]: <-- [9:AT+FTM=?\r]
Feb 18 14:21:33 mail FaxGetty[3343]: MODEM TIMEOUT: reading line from modem
Feb 18 14:21:33 mail FaxGetty[3343]: Error parsing "+FTM" query response: ""
Feb 18 14:21:33 mail FaxGetty[3343]: MODEM set DTR OFF
Feb 18 14:22:03 mail FaxGetty[3343]: /dev/modem1: Can not initialize modem.
Feb 18 14:22:03 mail FaxGetty[3343]: STATE CHANGE: RECEIVING -> MODEMWAIT (timeout 30)
Feb 18 14:22:33 mail kernel: ttyS15: LSR safety check engaged!
Feb 18 14:22:34 mail FaxGetty[3343]: MODEM set DTR OFF
Feb 18 14:22:34 mail FaxGetty[3343]: MODEM set baud rate: 0 baud (flow control unchanged)
Feb 18 14:22:34 mail FaxGetty[3343]: MODEM setBaudRate::tcgetattr: Input/output error
Feb 18 14:22:34 mail FaxGetty[3343]: DELAY 75 ms
Feb 18 14:22:34 mail FaxGetty[3343]: MODEM set DTR ON
Feb 18 14:22:34 mail FaxGetty[3343]: DELAY 2600 ms
Feb 18 14:22:37 mail kernel: ttyS15: LSR safety check engaged!
Feb 18 14:22:38 mail FaxGetty[3343]: MODEM set baud rate: 57600 baud, input flow RTS/CTS, output 
flow RTS/CTS
Feb 18 14:22:38 mail FaxGetty[3343]: MODEM setBaudRate::tcgetattr: Input/output error
Feb 18 14:22:38 mail FaxGetty[3343]: MODEM set DTR OFF
Feb 18 14:22:38 mail FaxGetty[3343]: MODEM set baud rate: 0 baud (flow control unchanged)
Feb 18 14:22:38 mail FaxGetty[3343]: MODEM setBaudRate::tcgetattr: Input/output error
Feb 18 14:22:38 mail FaxGetty[3343]: DELAY 75 ms
Feb 18 14:22:38 mail FaxGetty[3343]: MODEM set DTR ON
Feb 18 14:22:38 mail FaxGetty[3343]: DELAY 2600 ms
Feb 18 14:22:40 mail kernel: ttyS15: LSR safety check engaged!
Feb 18 14:22:41 mail FaxGetty[3343]: MODEM set baud rate: 57600 baud, input flow RTS/CTS, output 
flow RTS/CTS
Feb 18 14:22:41 mail FaxGetty[3343]: MODEM setBaudRate::tcgetattr: Input/output error
Feb 18 14:22:41 mail FaxGetty[3343]: MODEM set DTR OFF
Feb 18 14:22:41 mail FaxGetty[3343]: MODEM set baud rate: 0 baud (flow control unchanged)
Feb 18 14:22:41 mail FaxGetty[3343]: MODEM setBaudRate::tcgetattr: Input/output error
Feb 18 14:23:11 mail kernel: ttyS15: LSR safety check engaged!
Feb 18 14:23:12 mail FaxGetty[3343]: MODEM set DTR OFF
Feb 18 14:23:12 mail FaxGetty[3343]: MODEM set baud rate: 0 baud (flow control unchanged)
Feb 18 14:23:12 mail FaxGetty[3343]: MODEM setBaudRate::tcgetattr: Input/output error
Feb 18 14:23:12 mail FaxGetty[3343]: DELAY 75 ms
Feb 18 14:23:12 mail FaxGetty[3343]: MODEM set DTR ON
Feb 18 14:23:12 mail FaxGetty[3343]: DELAY 2600 ms
Feb 18 14:23:15 mail kernel: ttyS15: LSR safety check engaged!
Feb 18 14:23:16 mail FaxGetty[3343]: MODEM set baud rate: 57600 baud, input flow RTS/CTS, output 
flow RTS/CTS
Feb 18 14:23:16 mail FaxGetty[3343]: MODEM setBaudRate::tcgetattr: Input/output error
Feb 18 14:23:16 mail FaxGetty[3343]: MODEM set DTR OFF
Feb 18 14:23:16 mail FaxGetty[3343]: MODEM set baud rate: 0 baud (flow control unchanged)
Feb 18 14:23:16 mail FaxGetty[3343]: MODEM setBaudRate::tcgetattr: Input/output error
Feb 18 14:23:16 mail FaxGetty[3343]: DELAY 75 ms
Feb 18 14:23:16 mail FaxGetty[3343]: MODEM set DTR ON
Feb 18 14:23:16 mail FaxGetty[3343]: DELAY 2600 ms
Feb 18 14:23:19 mail kernel: ttyS15: LSR safety check engaged!
Feb 18 14:23:20 mail FaxGetty[3343]: MODEM set baud rate: 57600 baud, input flow RTS/CTS, output 
flow RTS/CTS
Feb 18 14:23:20 mail FaxGetty[3343]: MODEM setBaudRate::tcgetattr: Input/output error
Feb 18 14:23:20 mail FaxGetty[3343]: MODEM set DTR OFF
Feb 18 14:23:20 mail FaxGetty[3343]: MODEM set baud rate: 0 baud (flow control unchanged)
Feb 18 14:23:20 mail FaxGetty[3343]: MODEM setBaudRate::tcgetattr: Input/output error
Feb 18 14:23:20 mail FaxGetty[3343]: Unable to setup modem on /dev/modem1; giving up after 2 
attempts
Feb 18 14:23:20 mail FaxGetty[3343]: CLOSE /dev/modem1
Feb 18 14:23:20 mail FaxQueuer[3161]: MODEM /dev/modem1 appears to be wedged
Feb 18 14:23:20 mail FaxQueuer[3161]: MODEM WEDGED: bin/wedged "modem1" "/dev/modem1"



____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*