NetworkManager fails to reconnect 3G modem after disconnect -- Huawei

instead of rebooting, does a "sudo killall modem-manager" help?

If that doesnt help also run "sudo /etc/init.d/network-manager restart"

if one of those tricks works, please paste the successful connect log.

I did try killall modem-manager, but that didn't help. I haven't tried
restarting network-manager. I'll give that a try next time I'm on the train
again :-)

Thanks
Simon

2009/9/28 Alexander Sack <email address hidden>

> instead of rebooting, does a "sudo killall modem-manager" help?
>
> If that doesnt help also run "sudo /etc/init.d/network-manager restart"
>
> if one of those tricks works, please paste the successful connect log.
>
> --
> [karmic] Network-manager fails to reconnect to 3G network
> https://bugs.launchpad.net/bugs/438150
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “network-manager” package in Ubuntu: New
>
> Bug description:
> Binary package hint: network-manager
>
> Running latest Karmic updates (but this has been happening since I first
> tested with alpha 6).
>
> First connection to the network on my 3G USB modem works perfectly.
> However, if I lose connection (if I'm moving and roam outside cell coverage)
> then I lose connection but when I come back into coverage (blue blinking
> light on modem indicates coverage) I am unable to reconnect. Each time I
> select the network from the nm-applet I just get the OSD notify that the GSM
> network disconnected. Unplugging and re-plugging in my modem does not help.
> The only way to successfully connect is by rebooting my laptop. Syslog shows
> the following:
>
> Sep 28 07:36:24 spitfire-karmic NetworkManager: <info> (ttyUSB0): device
> state change: 8 -> 9 (reason 13)
> Sep 28 07:36:24 spitfire-karmic NetworkManager: <info> Activation
> (ttyUSB0) failed.
> Sep 28 07:36:24 spitfire-karmic NetworkManager: <info> (ttyUSB0): device
> state change: 9 -> 3 (reason 0)
> Sep 28 07:36:24 spitfire-karmic NetworkManager: <info> (ttyUSB0):
> deactivating device (reason: 0).
> Sep 28 07:36:24 spitfire-karmic modem-manager: (ttyUSB0) closing serial
> device...
> Sep 28 07:36:24 spitfire-karmic NetworkManager: <WARN> monitor_cb(): Could
> not read ppp stats: No such device
> Sep 28 07:36:24 spitfire-karmic NetworkManager: flush_routes: assertion
> `iface_idx >= 0' failed
> Sep 28 07:36:24 spitfire-karmic NetworkManager: flush_addresses: assertion
> `iface_idx >= 0' failed
> Sep 28 07:36:24 spitfire-karmic NetworkManager: SCPlugin-Ifupdown:
> devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
> Sep 28 07:36:26 spitfire-karmic NetworkManager: <debug> [1254119786.002657]
> ensure_killed(): waiting for ppp pid 5661 to exit
> Sep 28 07:36:26 spitfire-karmic NetworkManager: <debug> [1254119786.002994]
> ensure_killed(): ppp pid 5661 cleaned up
> Sep 28 07:37:56 spitfire-karmic NetworkManager: <info> Activation
> (ttyUSB0) starting connection '3 Internet'
> Sep 28 07:37:56 spitfire-karmic NetworkManager: <info> (ttyUSB0): device
> state change: 3 -> 4 (reason 0)
> Sep 28 07:37:56 spitfire-karmic NetworkManager: <info> Activation
> (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
> Sep 28 07:37:56 spitfire-karmic NetworkManager: <info> Activation
> (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
> Sep 28 07:37:56 spitfire-karmic NetworkManager: <info> Activation
> (ttyUSB0) Stage 1 of 5 (Device Prepare) complete....

So, I tried out both commands this morning, without success. After killing modem-manager and checking it had restarted, I was unable to re-connect. I did a restart of network-manager and noted that my 3G internet connection was not listed when clicking on nm-applet. Syslog data over the period is attached.

Thanks
Simon

I can confirm I have the same issue, also on Karmic, with a Sierra 3G modem built into a Fujitsu Siemens laptop:

Bus 002 Device 003: ID 1199:683c Sierra Wireless, Inc.
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 2
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x1199 Sierra Wireless, Inc.
  idProduct 0x683c
  bcdDevice 0.05
  iManufacturer 3
  iProduct 2
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 198
    bNumInterfaces 7
    bConfigurationValue 1
    iConfiguration 1
    bmAttributes 0xe0
      Self Powered
      Remote Wakeup
    MaxPower 0mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 255 Vendor Specific Subclass
      bInterfaceProtocol 255 Vendor Specific Protocol
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 32
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x01 EP 1 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 32
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 1
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 255 Vendor Specific Subclass
      bInterfaceProtocol 255 Vendor Specific Protocol
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 32
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x02 EP 2 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInter...

Additional information:
I have noticed that after this problem occurs, my laptop does not suspend correctly when closing the lid. In normal circumstances suspend works correctly, this is only after I have lost GSM connectivity. I get a kernel OOPs and the attached is the detail from syslog showing a kernel issue with usbserial disconnect.

can you please run ls ls /sys/devices/virtual/tty/ before connecting the first time and before connecting after the disconnect? please post the output.

also:

please stop network-manager and killall modem-manager ... then start

sudo modem-manager --debug

and network-manager again
reproduce and provide the full log you get from modem-manager

Simon, do you always get that kernel trace when it doesn't work?

To be honest, I hadn't checked before. I think today may have been the first
time that I tried to suspend my laptop following the GSM disconnect, rather
than a shutdown. As I said, a suspend at any other time works fine. I can
check again tomorrow - the problem is that I can only recreate this when I
lose GSM connectivity which is hard to replicate apart from when I'm
travelling.

Simon

2009/9/30 Alexander Sack <email address hidden>

> Simon, do you always get that kernel trace when it doesn't work?
>
> --
> [karmic] Network-manager fails to reconnect to 3G network
> https://bugs.launchpad.net/bugs/438150
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “modemmanager” package in Ubuntu: New
> Status in “network-manager” package in Ubuntu: New
>
> Bug description:
> Binary package hint: network-manager
>
> Running latest Karmic updates (but this has been happening since I first
> tested with alpha 6).
>
> First connection to the network on my 3G USB modem works perfectly.
> However, if I lose connection (if I'm moving and roam outside cell coverage)
> then I lose connection but when I come back into coverage (blue blinking
> light on modem indicates coverage) I am unable to reconnect. Each time I
> select the network from the nm-applet I just get the OSD notify that the GSM
> network disconnected. Unplugging and re-plugging in my modem does not help.
> The only way to successfully connect is by rebooting my laptop. Syslog shows
> the following:
>
> Sep 28 07:36:24 spitfire-karmic NetworkManager: <info> (ttyUSB0): device
> state change: 8 -> 9 (reason 13)
> Sep 28 07:36:24 spitfire-karmic NetworkManager: <info> Activation
> (ttyUSB0) failed.
> Sep 28 07:36:24 spitfire-karmic NetworkManager: <info> (ttyUSB0): device
> state change: 9 -> 3 (reason 0)
> Sep 28 07:36:24 spitfire-karmic NetworkManager: <info> (ttyUSB0):
> deactivating device (reason: 0).
> Sep 28 07:36:24 spitfire-karmic modem-manager: (ttyUSB0) closing serial
> device...
> Sep 28 07:36:24 spitfire-karmic NetworkManager: <WARN> monitor_cb(): Could
> not read ppp stats: No such device
> Sep 28 07:36:24 spitfire-karmic NetworkManager: flush_routes: assertion
> `iface_idx >= 0' failed
> Sep 28 07:36:24 spitfire-karmic NetworkManager: flush_addresses: assertion
> `iface_idx >= 0' failed
> Sep 28 07:36:24 spitfire-karmic NetworkManager: SCPlugin-Ifupdown:
> devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
> Sep 28 07:36:26 spitfire-karmic NetworkManager: <debug> [1254119786.002657]
> ensure_killed(): waiting for ppp pid 5661 to exit
> Sep 28 07:36:26 spitfire-karmic NetworkManager: <debug> [1254119786.002994]
> ensure_killed(): ppp pid 5661 cleaned up
> Sep 28 07:37:56 spitfire-karmic NetworkManager: <info> Activation
> (ttyUSB0) starting connection '3 Internet'
> Sep 28 07:37:56 spitfire-karmic NetworkManager: <info> (ttyUSB0): device
> state change: 3 -> 4 (reason 0)
> Sep 28 07:37:56 spitfire-karmic NetworkManager: <info> Activation
> (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
> Sep 28 07:37:56 spitfire-karmic NetworkManager: <info> Activation
> (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
...

I am experiencing a similar bug in ubuntu Karmic Koala beta (32-bit version). However my intent has been to use GSM networking in a live CD session. After configuring the connection I could not establish any GSM connection. So, my problem is not with just reconnecting; my problem is that I even cannot get any first connection. Any time I click on the connection name I can see a message that I am disconnected or off-line or something like that.

Few details:
My machine: notebook Fujitsu-Siemens AMILO Pro V3205 (a 32-bit Intel-based machine)
My modem: Option GlobeTrotter Express 7.2
My provider: Orange Slovakia

Martin.

Exactly the same thing with my Huawei E220. Symtpoms are :

-> At 1rst insert / connection, immediate deconnection,
-> 2nd connection, the modems stays connected for a few minutes / seconds, the disconnects,
-> 3rd connection, everything works fine.

After a while, the connection always has a short stop. From this moment, it becomes impossible to reconnect. The errormessages from syslog are then the one described on the previous posts. I have to reboot to be able to use the 3G modem again.

My machine : Asus Eeepc 1008HA, 9.10 netbook remix. Everything workd perfectly with XP on the same machine, and with 9.04 on my Lenovo SL400.

I forgot to add that the suspend symptom is the same as described up there. Impossible to susped, but the screen becomes "light black" and the machine freezes (mandatory hard reboot).

Emmanuel

Emmanuel ... you have a different hardware, please don't make this bug a catch-all thing that cannot be handled :).

Simon, so does it make a difference whether you properly disconnect through NM before reconnect? Did you replug the device in between?

Can you try to reproduce your issue a few times and observe if you get different kernel dumps in syslog at some point?

I can properly disconnect and reconnect via NM normally. This only happens
when I am connected, then lose GPRS connectivity as I'm moving (I get the
OSD indicating that network connectivity has been lost). At that point I am
unable to reconnect (even though I have GPRS coverage again). Disconnecting
and reconnecting the device has no effect. And the system hang on suspend
only happens after this GPRS disconnect.

I use my netbook on the train while travelling each morning which is when I
have this problem. I must admit I haven't tried for a few days since the
problem got annoying enough that I went back to my Jaunty install (which
works perfectly so this is definitely a Karmic regression). I'll aim to give
it a try again this week and report back.
Simon

2009/10/12 Alexander Sack <email address hidden>

> Emmanuel ... you have a different hardware, please don't make this bug a
> catch-all thing that cannot be handled :).
>
> Simon, so does it make a difference whether you properly disconnect
> through NM before reconnect? Did you replug the device in between?
>
> Can you try to reproduce your issue a few times and observe if you get
> different kernel dumps in syslog at some point?
>
> ** Changed in: network-manager (Ubuntu)
> Status: New => Invalid
>
> ** Changed in: modemmanager (Ubuntu)
> Status: New => Incomplete
>
> --
> [karmic] Network-manager fails to reconnect to 3G network
> https://bugs.launchpad.net/bugs/438150
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “modemmanager” package in Ubuntu: Incomplete
> Status in “network-manager” package in Ubuntu: Invalid
>
> Bug description:
> Binary package hint: network-manager
>
> Running latest Karmic updates (but this has been happening since I first
> tested with alpha 6).
>
> First connection to the network on my 3G USB modem works perfectly.
> However, if I lose connection (if I'm moving and roam outside cell coverage)
> then I lose connection but when I come back into coverage (blue blinking
> light on modem indicates coverage) I am unable to reconnect. Each time I
> select the network from the nm-applet I just get the OSD notify that the GSM
> network disconnected. Unplugging and re-plugging in my modem does not help.
> The only way to successfully connect is by rebooting my laptop. Syslog shows
> the following:
>
> Sep 28 07:36:24 spitfire-karmic NetworkManager: <info> (ttyUSB0): device
> state change: 8 -> 9 (reason 13)
> Sep 28 07:36:24 spitfire-karmic NetworkManager: <info> Activation
> (ttyUSB0) failed.
> Sep 28 07:36:24 spitfire-karmic NetworkManager: <info> (ttyUSB0): device
> state change: 9 -> 3 (reason 0)
> Sep 28 07:36:24 spitfire-karmic NetworkManager: <info> (ttyUSB0):
> deactivating device (reason: 0).
> Sep 28 07:36:24 spitfire-karmic modem-manager: (ttyUSB0) closing serial
> device...
> Sep 28 07:36:24 spitfire-karmic NetworkManager: <WARN> monitor_cb(): Could
> not read ppp stats: No such device
> Sep 28 07:36:24 spitfire-karmic NetworkManager: flush_routes: assertion
> `iface_idx >= 0' failed
> Sep 28 07:36:24 spitfire-karmic NetworkManager: flush_addresses: assertion
> `iface_idx >= 0' failed
> Sep 28...

This bug was fixed in the package modemmanager - 0.2.git.20091014t233208.16f3e00-0ubuntu1

---------------
modemmanager (0.2.git.20091014t233208.16f3e00-0ubuntu1) karmic; urgency=low

  New upstream snapshot: 2009-10-14 21:33:52 (GMT)
  + 16f3e00f3438507aee06ffcaee560e337b8e8279
  - gsm: fix unsolicited registration by calling the statemachine callback
    info (LP: #416893)
  - mbm: use generic get_signal_quality implementation rather than our own
    CIND based one - helps to fix LP: #449037 as its less error prone
  - mbm: implement AT*ENAP polling; needed for some mbm devices, like m300 (LP: #442967)
  - gsm: don't issue CFUN=0 by default (LP: #438150)
  - mbm: fix disable after 3b19a85727458821f5df20153f8c04bc7717ba30 (LP: #447347, #438150)
  - nokia: fix class property overrides to stop modemmanager from sending AT+CFUN (LP: #450256)

 -- Alexander Sack <email address hidden> Thu, 15 Oct 2009 02:03:37 +0200

I use my laptop "Thinkpad R61" with Ubuntu 9.10 Karmic Koala.
The problem, which Simon describes still occurs and this without any roaming. After a uncertain (certainly quite long :-)) time, my vodafone websession stops working and is not willing to reconnect. The reconnection is seen together with a heavy load on my two cores, which will not stop until reconnection is manually stopped or by timeout.

I use the K3565-Z usb stick.

The problem could only be solved by restarting the computer.
Next time I will attach the latest dmesg .

Here's my dmesg log after the connection broke (I did not exactly match the moment when it broke) :

$ dmesg | tail -n 50
[ 4128.571844] sd 6:0:0:0: [sdc] Sense Key : Recovered Error [current] [descriptor]
[ 4128.571851] Descriptor sense data with sense descriptors (in hex):
[ 4128.571854] 72 01 00 1d 00 00 00 0e 09 0c 00 00 00 00 00 00
[ 4128.571865] 00 00 00 00 e0 50
[ 4128.571871] sd 6:0:0:0: [sdc] Add. Sense: ATA pass through information available
[ 4129.070249] sd 6:0:0:0: [sdc] Sense Key : Recovered Error [current] [descriptor]
[ 4129.070264] Descriptor sense data with sense descriptors (in hex):
[ 4129.070270] 72 01 00 1d 00 00 00 0e 09 0c 00 00 00 00 00 00
[ 4129.070299] 00 4f 00 c2 e0 50
[ 4129.070314] sd 6:0:0:0: [sdc] Add. Sense: ATA pass through information available
[ 4129.079873] sd 6:0:0:0: [sdc] Sense Key : Recovered Error [current] [descriptor]
[ 4129.079885] Descriptor sense data with sense descriptors (in hex):
[ 4129.079891] 72 01 00 1d 00 00 00 0e 09 0c 00 00 00 ff 00 00
[ 4129.079919] 00 00 00 00 e0 50
[ 4129.079934] sd 6:0:0:0: [sdc] Add. Sense: ATA pass through information available
[ 4129.141741] sd 6:0:0:0: [sdc] Sense Key : Recovered Error [current] [descriptor]
[ 4129.141753] Descriptor sense data with sense descriptors (in hex):
[ 4129.141758] 72 01 00 1d 00 00 00 0e 09 0c 00 00 00 00 00 00
[ 4129.141786] 00 4f 00 c2 e0 50
[ 4129.141801] sd 6:0:0:0: [sdc] Add. Sense: ATA pass through information available
[ 4129.208120] sd 6:0:0:0: [sdc] Sense Key : Recovered Error [current] [descriptor]
[ 4129.208134] Descriptor sense data with sense descriptors (in hex):
[ 4129.208140] 72 01 00 1d 00 00 00 0e 09 0c 00 00 00 00 00 00
[ 4129.208168] 00 4f 00 c2 e0 50
[ 4129.208183] sd 6:0:0:0: [sdc] Add. Sense: ATA pass through information available
[ 5928.497825] sd 6:0:0:0: [sdc] Sense Key : Recovered Error [current] [descriptor]
[ 5928.497832] Descriptor sense data with sense descriptors (in hex):
[ 5928.497835] 72 01 00 1d 00 00 00 0e 09 0c 00 00 00 00 00 00
[ 5928.497846] 00 00 00 00 e0 50
[ 5928.497852] sd 6:0:0:0: [sdc] Add. Sense: ATA pass through information available
[ 5928.979103] sd 6:0:0:0: [sdc] Sense Key : Recovered Error [current] [descriptor]
[ 5928.979118] Descriptor sense data with sense descriptors (in hex):
[ 5928.979124] 72 01 00 1d 00 00 00 0e 09 0c 00 00 00 00 00 00
[ 5928.979153] 00 4f 00 c2 e0 50
[ 5928.979168] sd 6:0:0:0: [sdc] Add. Sense: ATA pass through information available
[ 5928.988592] sd 6:0:0:0: [sdc] Sense Key : Recovered Error [current] [descriptor]
[ 5928.988606] Descriptor sense data with sense descriptors (in hex):
[ 5928.988612] 72 01 00 1d 00 00 00 0e 09 0c 00 00 00 ff 00 00
[ 5928.988641] 00 00 00 00 e0 50
[ 5928.988655] sd 6:0:0:0: [sdc] Add. Sense: ATA pass through information available
[ 5929.050711] sd 6:0:0:0: [sdc] Sense Key : Recovered Error [current] [descriptor]
[ 5929.050723] Descriptor sense data with sense descriptors (in hex):
[ 5929.050729] 72 01 00 1d 00 00 00 0e 09 0c 00 00 00 00 00 00
[ 5929.050758] 00 4f 00 c2 e...

With

$sudo /etc/init.d/networking restart
$sudo /etc/init.d/network-manager restart
$sudo restart network-manager

I can reconnect!

Is anybody watching this?

As I said, and I can constantly confirm it:

sudo restart network-manager

solves the problem! But why does it hang up? System load explodes when reconnecting without restarting network manager.
The time between the crashes can tremendously differ from each other. Sometimes it works for nearly a day, sometimes it fails after 2-3 hours, which seem to be the more often case.

I close this, because error seems to vanish with latest updates....

Error is seldom, but occurs nevertheless.

Problem persists

Ok, because this problem also exist under Windows, I assume it has nothing to do with the network manager. Maybe it is the firmware. Under Windows XP it says that the sim card detect failed.

I am sorry but thanks for the great attention and the care you all take.

I have the same probleme with huawei e22O and Meditel Morroco ; can't connect since uprade from jaunty . thanks.

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.

I have quite similar simptoms here, with minor differences, with the Huawei E272 (which I heard about as a fast E220).

First a minor issue, if the modem is connected during bootup, it is not recognised. So I disconnect it during bootup, and plug it in later. Than...

The first connection to the network works perfectly. However, either I lose connection or disconnect manually, I am unable to reconnect any more. There seems to be high CPU usage during the connection attempt. I attach the tail of the syslog, which repeats a simple pattern of messages until I cancel the connection request.

The only way to connect again to the network is to reboot my computer - first plugging out the Huawei, than rebooting, than plugging in the Huawei again, and than the connect may succeed. Any other method I tried fails.

I figured out, that if I restart network-manager ("sudo restart network-manager" does that in a terminal), I am able to connect again with the broadband modem.

So the current work flow goes like this:
-connecting to the net works fine the first time, but does not work after being disconnected once;
-after restarting network-manager, connecting is possible again.

(Maybe some cleanup activity fails upon disconnecting?)

I have the exact same problem as Gergely, my modem is a Huawei E226
Additional info:
During the second connection attempt, when there is a high CPU usage, i can see the connecting icon of NM (2 green points and some arrows) flashing very quickly, as if there were some quick error followed by a quick retry.
I once read a message saying it could not open the keyring or something with authentication problem. I will try to reproduce that and paste the exact message.

Additional info:
How to reproduce error:
1 - Plug 3g Modem
2 - Connect to GSM network
3 - Disconnect from GSM network (or wait untill connection is dropped or random)
4 - Try to connect again
At this point, green lights flash at NM icon, CPU load go high. Nothing is logged in modem-manager (maybe a bug in network-manager instead?)

I generated a commented log from this (attached)

and syslog, with a successful (1st) and a failed (2nd) attempt

I see now this is not the exact same bug from the 1st post, maybe i should open another bug?

I just updated network-manager from ppa to version
0.8~a~git.20091216t212901.1e1be1c-0ubuntu1~nmt1~karmic
modemmanager 0.2.git.20091216t232605.8d42094-0ubuntu1~nmt1~karmic
the high cpu and icon flashing problem is gone, altough i still cannot reconnect to 3g after disconnection.
Sometimes it doesn't even recognize there is a 3g modem plugged in. (ill get a full log if this happens again)

Here goes the logs. I can see at modem-manager log that the modem itself had successfully connected, but somehow network-manager shut the connection down.
If any other info is needed, just ask and ill answer asap.

After trying repeatedly to connect and getting the error reported on attached log, it will get in a state which the only debug info in modem-manager is the following
** Message: Modem /org/freedesktop/ModemManager/Modems/2: state changed (disabled -> enabling)
** (modem-manager:3752): DEBUG: (ttyUSB0): --> 'ATZ E0 V1 +CMEE=1<CR>'
** Message: Modem /org/freedesktop/ModemManager/Modems/2: state changed (enabling -> disabled)
at this point, if i killall modem-manager i can connect again.

Same problem as Mr Guga, Huawei E1762. Additionally I am unable to edit the connection as authentication ails as it does not recognise my password.

This only started in January. It was working fine in December.

I would like to confirm bug exactly as first posted. Affecting Lubuntu 10.10 AND now 11.04.

nm-applet will connect my Huawei E1750 modem on the UK 3 3g network.
I live on a boat on the UK inland waterways and am mobile.
If i suffer a dissconnection due to a weak signal nm-applet will not reconnect if i regain the signal and it always reports disconnected
Kill all nm-applet and disconnecting the modem then AFTER a few moments restarting nm-applet and replugging the modem in and it will reconnect if signal strenght is good.
The sakis3g script works perfectly well so it is not a hardware problem
Best Wishes Chris

This bug may be closely related to
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/746078
https://bugs.launchpad.net/modemmanager/+bug/736930
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/435057

I have a Huawei E367 on 11.10 and I frequently have to reconnect my USB modem if I haven't been using my computer for a while and come back and there is no connection.

Your modem mail not be listed

    https://live.gnome.org/NetworkManager/MobileBroadband/

as a supported modem. Please file a request in the upstream bug tracking system

    https://bugzilla.gnome.org/browse.cgi?product=NetworkManager

asking for this modem to be supported.

I found this to be caused by ModemManager using the PPP port for both control and PPP; instead of the PCUI port for control and the PPP port for PPP. This issue should be fixed in the MM_06 branch of ModemManager already, as well as in git master. If anyone can try with MM_06 branch to confirm it, it would be great.

I tried MM_06 but the problem is still there.

This is the patch that allows reconnecting:
==================================
diff --git a/src/mm-generic-gsm.c b/src/mm-generic-gsm.c
index cfd31a9..fa18f2c 100644
--- a/src/mm-generic-gsm.c
+++ b/src/mm-generic-gsm.c
@@ -3919,7 +3919,8 @@ disconnect_done (MMModem *modem,
         return;

     priv = MM_GENERIC_GSM_GET_PRIVATE (modem);
- if (error) {
+ /* PRU 2013.03.03: If the port is closed do not consider it as error */
+ if (error && error->code != MM_SERIAL_ERROR_NOT_OPEN) {
         info->error = g_error_copy (error);
         /* Reset old state since the operation failed */
         prev_state = GPOINTER_TO_UINT (mm_callback_info_get_data (info, MM_GENERIC_GSM_PREV_STATE_TAG));
==================================

Where did you find that patch?

[Expired for modemmanager (Ubuntu) because there has been no activity for 60 days.]