mwavem crashes on Thinkpad 600E when trying to dial

Bug #152724 reported by Heinz Werner Kramski
4
Affects Status Importance Assigned to Milestone
mwavem (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: mwavem

I have problems with the ACP Modem (mwave) in an old ThinkPad 600E.

I don't know if this is a problem with my specific hardware setup or if it really is a bug in the mwavem package itself, so I'm reporting it here just to let the maintainers know.

The mwave module loads fine. The mwavem daemon (2.0-2) starts successfully, too.

However, I am unable to make any calls to an internet provider. Every time the modem tries to dial
a number, the mwavem process crashes. On the other hand, the modem replies to simple commands like ATZ
or ATI3, so the general (serial) setup seems to be ok.

When I start mwavem manually (not using /etc/init.d/mwavem) to better see the error messages, all looks well:

   root@grandl:~# /usr/sbin/mwavem /etc/mwavem/mwavem.conf
   Initializing mwave manager...
   Initializing modem specific code...
   Got configured startup speed: 64000...

   Checking configured speed...
   Setting modem speed...
   Loading modem DSP...
   mwave modem, STARTED...

In another terminal, I can now use minicom to successfully talk to the modem...

   Welcome to minicom 2.2

   OPTIONS: I18n
   Compiled on Mar 7 2007, 15:10:03.
   Port /dev/ttyS1

                  Press CTRL-A Z for help on special keys

   AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
   OK
   ati3
   ThinkPad Modem v4.0
   OK
   atz
   OK

... until I try for example

   atdt1234

which immediately leads to

   Segmentation fault (core dumped)

on my first terminal.

(With some tracing enabled via mwavem.conf, the last lines read:

    mwmload::mwmLoadDialToModem entry
    mwmpool::mwmPoolAllocateCoreChunk entry
    mwmpool::mwmPoolTransferControlBlock entry
    mwmpool::mwmPoolTransferControlBlock exit
    mwmcntnd::mwmCntndAllocSegment entry
    mwmcntnd::mwmCntndAllocSegment exit
    mwmpool::mwmPoolTransferControlBlock entry
    mwmpool::mwmPoolTransferControlBlock exit
    mwmpool::mwmPoolTransferControlBlock entry
    mwmpool::mwmPoolTransferControlBlock exit
    mwmpool::mwmPoolTransferControlBlock entry
    mwmpool::mwmPoolTransferControlBlock exit
    mwmpool::mwmPoolAllocateCoreChunk exit
    mwmload::mwmLoadDialToModem ulFeaturesToLoad 1912d4ea hmodV34 0
    mwmload::mwmLoadV34 entry

    Segmentation fault (core dumped)

Looks like mwavem dies when loading something like /usr/share/mwavem/v34.dsp into memory.)

Things I tried so far:

  - checked for hardware conflicts using the bios configuration utility ps2.exe
  - tried a non-default hardware (irq etc.) setup for serial-a and modem (IR port is disabled)
  - excluded irq 3 and 10 in /etc/pcmcia/config.opts, so the pcmcia handler does not touch them
  - disabled all sound related modules
  - compiled and tried my own "ACP Modem (Mwave) Driver for Linux" (mwavem-2.0.tar.gz) from Sourgeforge
    without luck.

I'm running the latest firmware available (INET36WW = 1.16, 11/20/99) and feisty (7.04). My boot options include "acpi=off pci=noacpi pnpbios=off vga=0x317".

Regards
   Heinz

Revision history for this message
Heinz Werner Kramski (kramski) wrote :
Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10?

Changed in mwavem:
status: New → Incomplete
Revision history for this message
Heinz Werner Kramski (kramski) wrote :

Sorry, Daniel, I don't have access to this machine any more.

Regards,
   Heinz

Revision history for this message
Victor Vargas (kamus) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in mwavem (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.