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

[Bill Binko <bill-sender-4b2fd6@xxxxxxxxx>]

Mike,
We have three of these running in production in one box with no issues 
with wedging.  As I mentioned, they are the -PCI not the -U versions, but 
that seems to be a small difference.

I thought I'd give you some info to compare to:

Here is what they look like in lspci -vv (note that mine get mapped into
high IRQs.  The fact that yours are on 5 and 9 bother me.  I know that 5
is often used for printers, and I thought that 2 and 9 were used to shift
registers, but this is very old data in the depths of a buggy mind.


If you want other examples, just ask.

Bill


01:07.0 Communication controller: Lucent Microelectronics Venus Modem (V90, 56KFlex)
        Subsystem: Lucent Microelectronics: Unknown device 5656
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0 (63000ns min, 3500ns max)
        Interrupt: pin A routed to IRQ 18
        Region 0: Memory at ec001000 (32-bit, non-prefetchable) [size=256]
        Region 1: I/O ports at a400 [size=256]
        Region 2: I/O ports at a800 [size=256]
        Region 3: I/O ports at ac00 [size=8]
        Capabilities: [f8] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2+,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

01:0b.0 Communication controller: Lucent Microelectronics Venus Modem (V90, 56KFlex)
        Subsystem: Lucent Microelectronics: Unknown device 5656
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0 (63000ns min, 3500ns max)
        Interrupt: pin A routed to IRQ 17
        Region 0: Memory at ec002000 (32-bit, non-prefetchable) [size=256]
        Region 1: I/O ports at b000 [size=256]
        Region 2: I/O ports at b400 [size=256]
        Region 3: I/O ports at b800 [size=8]
        Capabilities: [f8] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2+,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

01:0c.0 Communication controller: Lucent Microelectronics Venus Modem (V90, 56KFlex)
        Subsystem: Lucent Microelectronics: Unknown device 5656
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0 (63000ns min, 3500ns max)
        Interrupt: pin A routed to IRQ 19
        Region 0: Memory at ec003000 (32-bit, non-prefetchable) [size=256]
        Region 1: I/O ports at bc00 [size=256]
        Region 2: I/O ports at c000 [size=256]
        Region 3: I/O ports at c400 [size=8]
        Capabilities: [f8] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2+,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-



On Fri, 18 Feb 2005, Mike McMullen wrote:

> 
> > 
> > Mike,
> > 
> > My HylaFAX server configuration is very similar to yours.  Although it
> > sounds like whatever is causing your LSR safety check engaged message is
> > different than what was causing mine (see the threads Lee referenced).
> > Since upgrading to 1.32i I have not seen the LSR safety check engaged
> > message on my server which is only running one modem instead of two.  I
> > wonder if this problem is related to running two modems at the same
> > time?  Can you remove one of the modem cards from the server and
> > reconfigure HylaFAX to see if the problem goes away?
> > 
> > Kris
> > 
> Hi Kris,
> 
> Boy I hope it's not related to having two modems in the same box. I have
> them both in my company mail server right now so when I have to reboot
> the employees greet me with surly glares. I mean evern surlier than the
> ones I usually get. ;-)
> 
> I'd have to come up with a spare box to put the other one in unless I
> used our company web server but if one wedges in there and I have to
> reboot that means I get surly customers. I can handle surly employees
> but not surly customers.
> 
> I'll have to do some thinking and dinking over that this weekend.
> 
> Mike
> 
> 
> ____________________ 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*