Modem Manager setting bad baud rate, breaking pppd connections.

The kernel crash has not reproduced today since the new 2.6.31-6-generic kernel.

Based on the dpkg logs, I am pretty convinced that this was broken on August 7th by:

  network-manager 0.7.1.git.5.272c6a626-0ubuntu1 0.8~a~git.20090804t185522.4bab334-0ubuntu1
  network-manager-gnome 0.7.1.git.3.0461fff8-0ubuntu2 0.8~a~git.20090805t131328.d1edfce-0ubuntu1

because it was working previously that week, which included an upgrade on August 4th.

Let's just take the kernel trap off this bug report, so that ASAC can focus on the defect that needs to be fixed.

Still broken after today's updates:

modemmanager 0.2.git.20090806t105932.354a4cb-0ubuntu3
network-manager 0.8~a~git.20090820t182117.cb60390-0ubuntu2

Having seen Bug 412570 and Bug 413333, here is some additional data (first the modem-manager trace and the syslog output from the broken Karmic, followed by syslog output from still functioning Jaunty):

-------------------------------------------------------------------------
BROKEN WITH KARMIC:

root@karmic:~# killall -9 modem-manager NetworkManager
root@karmic:~# modem-manager --debug
  [NetworkManager is restarted in another tab, followed by several connect attempts]
** Message: Loaded plugin Huawei
** Message: Loaded plugin Sierra
** Message: Loaded plugin Option High-Speed
** Message: Loaded plugin MotoC
** Message: Loaded plugin Gobi
** Message: Loaded plugin Novatel
** Message: Loaded plugin Option
** Message: Loaded plugin Ericsson MBM
** Message: Loaded plugin Nokia
** Message: Loaded plugin Generic
** Message: Loaded plugin ZTE
** Message: (ttyACM0) opening serial device...
** (modem-manager:4928): DEBUG: (ttyACM0): probe requested by plugin 'Generic'
** (modem-manager:4928): DEBUG: (ttyACM0): --> 'AT+GCAP<CR>'
** (modem-manager:4928): DEBUG: (ttyACM0): <-- '<CR><LF>+GCAP: +CIS707-A, CIS-856, CIS-856-A<CR><LF><CR><LF>OK<CR><LF>'
** Message: (ttyACM0) closing serial device...
** Message: (Generic): CDMA modem /sys/devices/pci0000:00/0000:00:1a.1/usb4/4-1 claimed port ttyACM0
** (modem-manager:4928): DEBUG: Added modem /sys/devices/pci0000:00/0000:00:1a.1/usb4/4-1
** (modem-manager:4928): DEBUG: Exported modem /sys/devices/pci0000:00/0000:00:1a.1/usb4/4-1 as /org/freedesktop/ModemManager/Modems/0
** Message: (ttyACM0) opening serial device...
** (modem-manager:4928): DEBUG: (ttyACM0): --> 'ATZ E0 V1 X4 &C1<CR>'
** (modem-manager:4928): DEBUG: (ttyACM0): <-- '<CR><LF>OK<CR><LF>'
** (modem-manager:4928): DEBUG: (ttyACM0): --> 'AT+CMEE=1<CR>'
** (modem-manager:4928): DEBUG: (ttyACM0): <-- '<CR><LF>ERROR<CR><LF>'
** (modem-manager:4928): DEBUG: Got failure code 100: Unknown error

** (modem-manager:4928): WARNING **: Your CDMA modem does not support +CMEE command
** (modem-manager:4928): DEBUG: (ttyACM0): --> 'ATDT#777<CR>'
** (modem-manager:4928): DEBUG: (ttyACM0): <-- '<CR><LF>NO CARRIER<CR><LF>'
** (modem-manager:4928): DEBUG: (ttyACM0): --> 'ATZ E0 V1 X4 &C1<CR>'
** (modem-manager:4928): DEBUG: (ttyACM0): <-- '<CR><LF>OK<CR><LF>'
** (modem-manager:4928): DEBUG: (ttyACM0): --> 'AT+CMEE=1<CR>'
** (modem-manager:4928): DEBUG: (ttyACM0): <-- '<CR><LF>ERROR<CR><LF>'
** (modem-manager:4928): DEBUG: Got failure code 100: Unknown error

** (modem-manager:4928): WARNING **: Your CDMA modem does not support +CMEE command
** (modem-manager:4928): DEBUG: (ttyACM0): --> 'ATDT#777<CR>'
** (modem-manager:4928): DEBUG: (ttyACM0): --> 'ATZ E0 V1 X4 &C1<CR>'
** (modem-manager:4928): DEBUG: (ttyACM0): <-- '<CR><LF>NO CARRIER<CR><LF>'
** (modem-manager:4928): DEBUG: Got failure code 3: No carrier
** (modem-manager:4928): DEBUG: (ttyACM0): --> 'ATZ E0 V1 X4 &C1<CR>'
** (modem-manager:4928): DEBUG: (ttyACM0): <-- '<CR><LF>OK<CR><LF>'
** (modem-manag...

This is probably a duplicate of Bug 410386.

> Aug 20 18:41:24 jaunty NetworkManager: nm_ip4_config_add_nameserver: assertion `nameserver != s' failed

This should be fixed in latest available in karmic. Please check if that helps to get the final connection. otherwise post an updated log with all packages up-to-date. (ensure that modemmanager is the one from today - might take a bit to get to your mirror)

Still not working after modemmanager 0.2.git.20090820t183237.cd75023-0ubuntu1, which installed this morning.

$ tail -n 0 -F /var/log/syslog
Aug 21 09:51:28 karmic NetworkManager: <info> Activation (ttyACM0) starting connection 'Auto Mobile Broadband (CDMA) connection'
Aug 21 09:51:28 karmic NetworkManager: <info> (ttyACM0): device state change: 3 -> 4 (reason 0)
Aug 21 09:51:28 karmic NetworkManager: <info> Activation (ttyACM0) Stage 1 of 5 (Device Prepare) scheduled...
Aug 21 09:51:28 karmic NetworkManager: <info> Activation (ttyACM0) Stage 1 of 5 (Device Prepare) started...
Aug 21 09:51:29 karmic NetworkManager: <info> Activation (ttyACM0) Stage 1 of 5 (Device Prepare) complete.
Aug 21 09:51:29 karmic modem-manager: Got failure code 100: Unknown error
Aug 21 09:51:29 karmic modem-manager: Your CDMA modem does not support +CMEE command
Aug 21 09:51:30 karmic NetworkManager: <info> Activation (ttyACM0) Stage 2 of 5 (Device Configure) scheduled...
Aug 21 09:51:30 karmic NetworkManager: <info> Activation (ttyACM0) Stage 2 of 5 (Device Configure) starting...
Aug 21 09:51:30 karmic NetworkManager: <info> (ttyACM0): device state change: 4 -> 5 (reason 0)
Aug 21 09:51:30 karmic NetworkManager: <info> Activation (ttyACM0) Stage 2 of 5 (Device Configure) successful.
Aug 21 09:51:30 karmic NetworkManager: <info> Activation (ttyACM0) Stage 3 of 5 (IP Configure Start) scheduled.
Aug 21 09:51:30 karmic NetworkManager: <info> Activation (ttyACM0) Stage 2 of 5 (Device Configure) complete.
Aug 21 09:51:30 karmic NetworkManager: <info> Activation (ttyACM0) Stage 3 of 5 (IP Configure Start) started...
Aug 21 09:51:30 karmic NetworkManager: <info> (ttyACM0): device state change: 5 -> 7 (reason 0)
Aug 21 09:51:30 karmic NetworkManager: <info> Starting pppd connection
Aug 21 09:51:30 karmic NetworkManager: <debug> [1250862690.253554] nm_ppp_manager_start(): Command line: /usr/sbin/pppd nodetach lock nodefaultroute user **********@alltel.net ttyACM0 noipdefault noauth usepeerdns lcp-echo-failure 0 lcp-echo-interval 0 ipparam /org/freedesktop/NetworkManager/PPP/4 plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so
Aug 21 09:51:30 karmic pppd[4296]: Plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so loaded.
Aug 21 09:51:30 karmic NetworkManager: <debug> [1250862690.265510] nm_ppp_manager_start(): ppp started with pid 4296
Aug 21 09:51:30 karmic NetworkManager: <info> Activation (ttyACM0) Stage 4 of 5 (IP6 Configure Get) scheduled...
Aug 21 09:51:30 karmic NetworkManager: <info> Activation (ttyACM0) Stage 3 of 5 (IP Configure Start) complete.
Aug 21 09:51:30 karmic NetworkManager: <info> Activation (ttyACM0) Stage 4 of 5 (IP6 Configure Get) started...
Aug 21 09:51:30 karmic NetworkManager: <info> Activation (ttyACM0) Stage 4 of 5 (IP6 Configure Get) complete.
Aug 21 09:51:30 karmic pppd[4296]: pppd 2.4.5 started by root, uid 0
Aug 21 09:51:30 karmic pppd[4296]: Baud rate for /dev/ttyACM0 is 0; need explicit baud rate
Aug 21 09:51:31 karmic pppd[4296]: Exit.
Aug 21 09:51:31 karmic NetworkManager: <WARN> ppp_exit_code(): ppp pid 4296 exited with error: Fatal pppd error
Aug 21 09:51:31 karmic NetworkManager: <debug> [1250862691.271284] ppp_watch_cb(): ppp pid 4...

Alexander, do you want for me to add the NetworkManager PPA (https://launchpad.net/~network-manager/+archive/trunk)?

*Something* changed today (or since the weekend, since I've been testing Jaunty for a few days), and the UM-175 works today.

No changes to NM, so I don't know what it was that was fixed. I saw udev changes related to modems, but I don't see one that applies. In fact, we need a udev change for this modem, but that will be for a separate bug.

:-( After a reboot, we were back to the previous, failing, behavior.

I have enabled the NetworkManager PPA, but it does not help. PLEASE ADVISE -- this is the current Verizon 3G modem, and we really do want it working.

Alexander, I just gort it working. I'll have to play to see how reproducible this is, but this is what I am seeing ...

I insert the device. It is configured on ttyACM0, but does not work. I remove the device and replug it. It still does not work, BUT I now have ttyACM0 and ttyACM1. NM is trying to use ttyACM0, but the device has apparently now been moved to ttyACM1. I remove ttyACM0 and symlink it to ttyACM1, and the modem starts working.

Got a clue?

Alexander, just confirming that this behavior is consistent.

On the initial recognition, it is assigned ttyACM0, but NetworkManager can't use it (I don't know why not). After removing the device, and even if removing /dev/ttyACM0, reinserting the device it gets /dev/ttyACM1, which NetworkManager doesn't want to use. Creating the symlink makes it work.

So we have a workaround, but also a reproducible situation that should be fixed.

I experience the same behaviour when trying to connect to my Nokia E71 through USB.

As requested by Alexander, I am attaching an annotated log of modem-manager output, along with that of related commands, from a complete series of tests, starting with clean reboot, working through failures and finally working after creating the ttyACM0 symlink.

please try the latest daily modemmanager packages: https://edge.launchpad.net/~network-manager/+archive/trunk

Not fixed, yet, but actively being worked on. There are a couple of outstanding issues. The primary remaing cause of THIS bug is shown by:

Aug 21 09:51:30 karmic pppd[4296]: pppd 2.4.5 started by root, uid 0
Aug 21 09:51:30 karmic pppd[4296]: Baud rate for /dev/ttyACM0 is 0; need explicit baud rate
Aug 21 09:51:31 karmic pppd[4296]: Exit.

We think we know what causes it, and are investigating a fix on #nm.

Another issue does come from NetworkManager, but is not the primary cause of THIS bug.

On Fri, Sep 04, 2009 at 09:13:54PM -0000, Noel J. Bergman wrote:
> Not fixed, yet, but actively being worked on. There are a couple of
> outstanding issues. The primary remaing cause of THIS bug is shown by:
>
> Aug 21 09:51:30 karmic pppd[4296]: pppd 2.4.5 started by root, uid 0
> Aug 21 09:51:30 karmic pppd[4296]: Baud rate for /dev/ttyACM0 is 0; need explicit baud rate
> Aug 21 09:51:31 karmic pppd[4296]: Exit.
>
> We think we know what causes it, and are investigating a fix on #nm.
>
> Another issue does come from NetworkManager, but is not the primary
> cause of THIS bug.
>

from what i understood the underlying issue is that modemmanager does
not serialize disconnects (and probably other operations that modify
the baud rate of the tty).

This sounds easy to fix by dropping (or queuing) incoming disconnect
requests if there is another operation running.

Not sure what dan thinks about this approach though ;).

 - Alexander

fixed upstream 14e5c52f78e7ad23b18b111e3271cbecad6acf3f

I have this same issue on a dell mini 9 with its inbuilt 3G modem. Pretty much the same error.
After updating with the latest PPA i can now connect when in a 3G area, but if the signal is marginal or GPRS it will not connect in Koala.

I can connect with the 9.04 machine but it gives the same error as above when trying it on Koala.

I have updated again last night and will give it a try from a few different locations today.
I also have a E220 HSDPA USB modem, so i will try that as well as the inbuilt modem.

On Thu, Sep 10, 2009 at 08:14:32PM -0000, drew wrote:
> I have this same issue on a dell mini 9 with its inbuilt 3G modem. Pretty much the same error.
> After updating with the latest PPA i can now connect when in a 3G area, but if the signal is marginal or GPRS it will not connect in Koala.
>

isnt this a mbm modem? can you please open a new bug against
modemmanager. most errors look similar, but usually they are different
bug.s

Also try the latest daily packages which fix a number of bugs:

  https://edge.launchpad.net/~network-manager/+archive/trunk

>
> I have updated again last night and will give it a try from a few different locations today.
> I also have a E220 HSDPA USB modem, so i will try that as well as the inbuilt modem.
>

Please open individual bugs with the model name of the modem in the
bug title for different modems. Thanks!

 - Alexander

This bug was fixed in the package modemmanager - 0.2.git.20090909t142854.64b7be7-0ubuntu1

---------------
modemmanager (0.2.git.20090909t142854.64b7be7-0ubuntu1) karmic; urgency=low

  New upstream snapshot 2009-09-09 14:28:54 (GMT)
  + commit: 64b7be7460c3a9dbb3c9981de5754b330a8d2cdd
  + fix LP: #414604 - Modem Manager setting bad baud rate, breaking pppd
    connections.
  + fix LP: #416418 - First connection attempt via F3507g fails
  + fix LP: #424603 - Not closing modems when disconnected

  [ Alexander Sack <email address hidden> ]
  * address MIR comments (LP: #410259)
    + cleanup debian/copyright
    + set debhelper compat level to 5, matching debian/control
      - add debian/compat
    + remove not used patches
      - delete debian/patches/ftbfs_hardy_glib_include_signal_h.patch
    + use proper automake lower and upper version bounds matching the
      versions referred to in debian/rules
      - update debian/control
    + don't redefine cdbs variables DEB_SOURCE, DEB_VERSION and
      DEB_UPSTREAM_VERSION; in turn move DEB_MAJOR_VERSION definition
      below the cdbs includes and use DEB_SOURCE_PACKAGE in GET_SOURCE
      function
      - update debian/rules
    + document why we touch aclocal.m4 in pre-build::
      - update debian/rules
    + use Ubuntu Network Manager Team as Maintainer and add <email address hidden>
      to Uploaders
      - update debian/control

 -- Alexander Sack <email address hidden> Mon, 14 Sep 2009 11:38:05 +0200

Hi Alexander,
I did a network upgrade from 9.04 to 9.10 on the release day and I am facing this issue with mobile broadband connection after the upgrade. The bug is in fixed state, but I couldn't find any fix-version info. Is the fix already incorporated in the release tree or does it require a separate upgrade after installing 9.10?

My CDMA modem support is also broken in Karmic. worked well in 9.04. I didn't upgrade, made clean install...

Nov 3 13:39:38 invader modem-manager: (ttyUSB0) opening serial device...
Nov 3 13:39:38 invader modem-manager: Got failure code 100: Unknown error
Nov 3 13:39:38 invader modem-manager: Your CDMA modem does not support +CMEE command

lsusb:
Bus 005 Device 006: ID 16d5:6502 AnyDATA Corporation

Updated network manager from trunk - 0.8~a~git.20091103t012953.dccdf5e-0ubuntu1~nmt1
bug isn't fixed

> modem-manager: (ttyUSB0) opening serial device...
> modem-manager: Got failure code 100: Unknown error
> modem-manager: Your CDMA modem does not support +CMEE command

Diagnostic messages that have nothing to do with functionality. I get those, too, and my UM-175 works (if it didn't, I wouldn't be posting this message).

> modem-manager: (ttyUSB0) opening serial device...
> modem-manager: Got failure code 100: Unknown error
> modem-manager: Your CDMA modem does not support +CMEE command

i have some problem.
This problem is in Network manager. From upgrading ubuntu 9.10 Karmic start not working connect to internet via cmda.

I am using pppd and this is working properly.

Same problem with modem Novatel MC950D 1410:4400. This works with wvdial. It also worked with some karmic beta.

I have had the same problem with Novatel MC950D 1410:4400.
After updating the system with networkmanager from trunk ppa and with not realesed updated (2.6.31-15-generic-pae)
the problem have not dissapeared.
Following the instructions in https://wiki.ubuntu.com/DebuggingModemmanager I noticed that the call number was *99***1#***1#
instead of what I have inserted in knetworkmanager config (*99***1#), I changed the number to *99#, and now it works.
I have had also problems with usb-switch, following this instructions "http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?t=247&view=next&sid=4e40a70b2235b2e73caaa95451ca898b" now it works. In kubuntu 9.10 the problem seems to be /lib/udev/rules.d/61-modem-switch.rules file.

This bug is fixed release ... please open new bugs against modemmanager if you
still have problemsn ... checkout https://wiki.ubuntu.com/DebuggingModemmanager
and get the logs as suggested there.

 - Alexander