Re: [hylafax-users] Solaris x86 "T.30 T2 timeout, expected page not received" or "Missing EOL after 5 seconds" problem

[Ertan Küçükoğlu <ek@xxxxxxxxxxxxxxxx>]

Ok, I made some search and found following.

1- Solaris for x86 platform uses asy driver for COM ports.

bash-3.00# ls -l /dev/cua0
lrwxrwxrwx   1 root     root          29 Aug  9 15:25 /dev/cua0 ->
../devices/isa/asy@1,3f8:a,cu
bash-3.00#

2- asy driver manual page have following entry in it:

     Note -  This module is affected by the  setting  of  certain
             eeprom  variables,  ttya-ignore-cd and ttya-rts-dtr-
             off (and  similarly  for  ttyb-,  ttyc-,  and  ttyd-
             parameters).  For  information  on these parameters,
             see the eeprom(1M) man page.

     Note -  For serial ports on the standard COM1  to  COM4  I/O
             addresses  above,  the  default  setting  for  ttya-
             ignore-cd and ttya-rts-dtr-off is true.  If  any  of
             these ports are connected to a modem, these settings
             should be changed to  false.  For  serial  ports  on
             non-standard  I/O addresses, the default setting for
             ttya-ignore-cd and ttya-rts-dtr-off is false.

What I did now is as follows:

bash-3.00# eeprom ttya-ignore-cd
ttya-ignore-cd=true
bash-3.00# eeprom ttya-ignore-cd=false
bash-3.00# eeprom ttya-ignore-cd
ttya-ignore-cd=false
bash-3.00# eeprom ttya-rts-dtr-off
ttya-rts-dtr-off=false
bash-3.00# reboot

Since ttya-rts-dtr-off was false. I did not touch it. I will observe the
behavior for next week and provide a feedback to the list.

Regards,
Ertan

> -----Original Message-----
> From: hylafax-users-bounce@xxxxxxxxxxx [mailto:hylafax-users-
> bounce@xxxxxxxxxxx] On Behalf Of Ertan Küçükoğlu
> Sent: Friday, August 29, 2008 2:48 PM
> To: 'Lee Howard'
> Cc: hylafax-users@xxxxxxxxxxx
> Subject: Re: [hylafax-users] Solaris x86 "T.30 T2 timeout, expected
> page not received" or "Missing EOL after 5 seconds" problem
> 
> > -----Original Message-----
> > From: hylafax-users-bounce@xxxxxxxxxxx [mailto:hylafax-users-
> > bounce@xxxxxxxxxxx] On Behalf Of Lee Howard
> > Sent: Thursday, August 28, 2008 6:17 AM
> > To: Ertan Küçükoğlu
> > Cc: hylafax-users@xxxxxxxxxxx
> > Subject: Re: [hylafax-users] Solaris x86 "T.30 T2 timeout, expected
> > page not received" or "Missing EOL after 5 seconds" problem
> >
> > Ertan Küçükoğlu wrote:
> > >
> > > I have frequent hang of modem after switching to Solaris 10 Update
> 5
> > > (7/08) x86 OS.
> > >
> > >
> > >
> > > I recently switched my system from FreeBSD 7.0 to Solaris x86. All
> > > patches are applied to Solaris system. After this switch I got a
> lot
> > > of trouble because of hanging of the modem. My old MultiTech 56K
> ZDX
> > > modem started to freeze for some jobs. Below is a sample log from
> one
> > > of them. All available classes are tried until now. Modem is set as
> > > Class1 as this is the long lasting class before freezing.
> > >
> >
> > So this very same hardware was working fine with the very same
> version
> > of HylaFAX under FreeBSD before switching to Solaris where the
> problems
> 
> Actually, there is a new hardware in terms of Computer. I have a new HP
> Proliant ML110 G5 server for Solaris. Unfortunately, I do not have the
> chance to make a trial with FreeBSD on this hardware soon. Since this
> is a
> production server right now. My earliest trial time may be 13th
> September.
> However, I do not hit this error always. Only some systems sending fax
> to me
> is not completing properly (as shown in my first e-mail with the
> subject).
> Right after this not completion, modem stays On Hook.
> 
> > started?  If so, it would seem to be either a bug in the Solaris
> serial
> > driver or a problem in how HylaFAX handles the serial port on Solaris
> > (that doesn't always cause the modem to lock up).
> 
> I have seen DTR delay related pages related to Solaris SPARC versions.
> It
> seems that Solaris SPACR serial driver used to have default 3 seconds
> delay
> on DTR. I am in progress to find related driver and set parameter to
> pass to
> the kernel in order to reduce this delay for Solaris X86 version.
> However,
> this delay problem seems to be a problem long ago. Anyway, I am
> checking if
> this is still an issue.
> 
> >
> > If you power-cycle the modem (it's external, after all) does it wake
> > up?  I suspect not, which would mean that the problem is in the
> serial
> > interfacing.
> 
> If I do not reboot the Solaris system, only power-cycle modem which is
> an
> external one problem continues. Only solution is to reboot, or power-
> cycle
> the Solaris system.
> 
> >
> > There is an unlikely possibility that the slightly different modem
> > reset
> > procedure (which only comes into play in potential wedged conditions)
> > in
> > HylaFAX+ would be able to recover modem connectivity.  You may want
> to
> > give that a try.  Assuming that does not work you'll need to get
> 
> Is it possible to learn this procedure? I do not know how to do this.
> 
> > debugging information out of the Solaris kernel serial driver in
> order
> > to proceed with any predictability.
> >
> > Thanks,
> >
> > Lee.
> 
> Regards,
> Ertan
> 
> 
> ____________________ 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*