Hylafax Mailing List Archives

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

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






The "LSR safety check" kernel error means that the serial driver thinks
something 'bad' happened with the port that it was talking to. My
understanding is that the UART returned something invalid when it wasn't
supposed to. When this happens, the kernel gives up on the port and you're
pretty well dead in the water.

Some documentation is in the Modem HOWTO at (this specific error is
mentioned):

http://www.tldp.org/HOWTO/Modem-HOWTO.html

You might also search the hylafax archives, as I believe Lee has fielded
this issue before (earlier last year):

http://www.hylafax.org/archive/2004-04/msg00040.html


Bottom line is that something flaky is going on between the kernel serial driver and your modem ... possibly IRQ sharing, I/O conflict or something isn't plugged in quite right, that type of thing.

Christian


Hi Christian,


Both cards are firmly seated and screwed. Which seems to describe me at
the moment.

It appears the PCI modems have their correct IRQs.

From dmesgs I get the following for serial ports.

ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A   - serial port used by old external modem 1
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A   - serial port used by old external modem 2
ttyS14 at I/O 0xcc00 (irq = 9) is a 16550A - device PCI "modem" device is symlinked to
ttyS15 at I/O 0xe000 (irq = 5) is a 16550A - device PCI "modem1" device is symlinked to

lspci -vv shows:

00:09.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 9
Region 0: Memory at dc000000 (32-bit, non-prefetchable)
Region 1: I/O ports at cc00 [size=256]
Region 2: I/O ports at d000 [size=256]
Region 3: I/O ports at d400 [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-


00:11.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 5
Region 0: Memory at dc003000 (32-bit, non-prefetchable)
Region 1: I/O ports at e000 [size=256]
Region 2: I/O ports at e400 [size=256]
Region 3: I/O ports at e800 [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-


I do a VGA controller routed to IRQ 5 as well as one of the PCI modems. However, wedging has appeared
on both modems so I don't think that is an issue.


However, the modems are being reported as Lucent Microelectronics Venus Modem (V90, 56KFlex).
Could that be the issue? Wrong drivers?

Sorry if I appear a little dim on this. I haven't had to hand install any drivers in linux. When I put the modems
in, the system foudn teh drivers and came up.


TIA,

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*



Home
Report any problems to webmaster@hylafax.org

HylaFAX is a trademark of Silicon Graphics Corporation.
Internet connectivity for hylafax.org is provided by:
VirtuALL Private Host Services