Re: [hylafax-users] Modem wedged. A hardware problem? (fixed email)

["andrew rinaldi" <andrew.rinaldi@xxxxxxxxxxxx>]

Hi Paul.

I'm not sure whether your fixed email refers to the 'signed email' or the
'modem wedged' problem.... 

If the 'modem wedged' problem remains (or reoccurs) then it may help to know
that the Agere firmware that is used in the MT5634 contains a number of
flaws.  These manifest themselves in various ways but eventually lead to a
DSP and/or Controller crash which results in the modem becoming unresponsive
('wedged').  Unfortunately, because the MT5634 is an internal modem the only
way to reliably recover from this state is to reboot the server and force a
hardware reset (unless of course your modem features a software controlled
reset - aka a mainpine modem [end of sales pitch -:) ]).

If the 'wedged' state is rare then you could just live with it.  If not,
then a change of OS version, HylaFAX version, server hardware, or even PCI
slot may (or may not) change the frequency that the modem crashes.... all
these factors (and more) have a bearing on it.

Regards

ANDREW RINALDI
Mainpine Support
USA +1 718 701 2422 | Asia/Europe +44 1225 436137 
andrew.rinaldi@xxxxxxxxxxxx | www.mainpine.com

-----Original Message-----
From: hylafax-users-bounce@xxxxxxxxxxx
[mailto:hylafax-users-bounce@xxxxxxxxxxx] On Behalf Of Paul Smith
Sent: 25 January 2006 19:45
To: hylafax-users@xxxxxxxxxxx
Subject: [hylafax-users] Modem wedged. A hardware problem? (fixed email)

[Sorry about that last signed email.  All fixed now.]

I've had hylafax 4.2.2 running just fine, sending and receiving, on a debian
etch box for around 6 weeks.  The modem is a "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/"

Yesterday people were having sporadic sending problems ("Busy signal
detected", "No carrier detected") and today I've started getting "modem
wedged" emails and this kind of thing in the logs:

Jan 25 12:03:01 faxsvr FaxGetty[3215]: Unable to setup modem on /dev/ttyS14;
giving up after 2 attempts Jan 25 12:03:01 faxsvr FaxGetty[3215]: CLOSE
/dev/ttyS14 Jan 25 12:03:01 faxsvr FaxQueuer[1990]: MODEM /dev/ttyS14
appears to be wedged Jan 25 12:03:01 faxsvr FaxQueuer[1990]: MODEM WEDGED:
bin/wedged "ttyS14"
"/dev/ttyS14"
Jan 25 12:03:01 faxsvr FaxGetty[3843]: OPEN /dev/ttyS14  HylaFAX (tm)
Version 4.2.4 Jan 25 12:03:10 faxsvr FaxGetty[3843]: /dev/ttyS14: Can not
initialize modem.

I've restarted the services, rebooted and cold booted the machine all to no
avail.  I even upgraded Hylafax to the latest available 4.2.4 in the hope
that might fix the problem but nothing I do seems to make much difference.
Some previous discussions on this list pointed me towards cu but that
disconnects as soon as I start typing.

faxsvr:~# cu -l ttyS14
cu: ttyS14: Line in use
faxsvr:~# cu -l ttyS14
Connected.
t
Disconnected.
faxsvr:~# ti3

Are there any other tests I can do?  Is the modem faulty?

Thanks

Paul

____________________ 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*




____________________ 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*