Huawei E620 USB 3G card not switched to modem mode, dmesg/modemmanager loop

[Martin Pitt]

Binary package hint: modemmanager

When I plug in my Huawei E620, it seems that modemmanager has trouble with removing the fake CD-ROM and switching it to modemmode:

[ 4703.420631] usb-storage: device scan complete
[ 4703.422691] scsi 4215:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2
[ 4703.424708] scsi 4215:0:0:1: Direct-Access HUAWEI SD Storage 2.31 PQ: 0 ANSI: 2
[ 4703.437681] sr1: scsi-1 drive
[ 4703.437976] sr 4215:0:0:0: Attached scsi CD-ROM sr1
[ 4703.438147] sr 4215:0:0:0: Attached scsi generic sg2 type 5
[ 4703.438432] sd 4215:0:0:1: Attached scsi generic sg3 type 0
[ 4703.462263] option: option_instat_callback: error -108
[ 4703.462588] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[ 4703.462612] option 1-8.2:1.0: device disconnected
[ 4703.462733] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[ 4703.462766] option 1-8.2:1.1: device disconnected
[ 4703.462879] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[ 4703.462908] option 1-8.2:1.2: device disconnected
[ 4703.550294] usb 1-8.2: reset full speed USB device using ehci_hcd and address 16
[ 4703.671820] option 1-8.2:1.2: GSM modem (1-port) converter detected
[ 4703.672019] usb 1-8.2: GSM modem (1-port) converter now attached to ttyUSB0
[ 4703.675924] option 1-8.2:1.1: GSM modem (1-port) converter detected
[ 4703.676085] usb 1-8.2: GSM modem (1-port) converter now attached to ttyUSB1
[ 4703.676237] option 1-8.2:1.0: GSM modem (1-port) converter detected
[ 4703.676373] usb 1-8.2: GSM modem (1-port) converter now attached to ttyUSB2
[ 4703.688381] option: option_instat_callback: error -108

This loops on and on ad infinitum.

This is reflected on endless loops in modemmanager:

** Message: (ttyUSB2) opening serial device...
** (modem-manager:24757): DEBUG: (Huawei): (ttyUSB0) deferring support check
** (modem-manager:24757): DEBUG: (Huawei): (ttyUSB1) deferring support check
** Message: (ttyUSB2) opening serial device...

During this, /dev/sr1 keeps existing, and GNOME fails to automount it. I never get a /dev/ttyUSB*.

ProblemType: Bug
Architecture: amd64
Date: Tue Oct 13 12:12:19 2009
DistroRelease: Ubuntu 9.10
Package: modemmanager 0.2.git.20091003t063318.aa78b5f-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
SourcePackage: modemmanager
Uname: Linux 2.6.31-13-generic x86_64

[Martin Pitt (pitti)]

For the record, in Jaunty this device worked just fine.

[Martin Pitt (pitti)]

Needless to say that "mm-test.py" just says "no modems found"

[Alexander Sack (asac)]

[18334.554085] option: option_instat_callback: error -108 ... also in bug 450237

[Alexander Sack (asac)]

@bugabundo: you had some idea about the regression window, right? what timeframe was that again?

The "option: " error from above feels like a kernel bug. Can you check if using older kernel helps?

[Fernando Miguel (fernandomiguel)]

1 or 2 weeks MAX.i'll have to grep my IRC logs.
i told you the next day it happened!
Not at home right now :(

[Fernando Miguel (fernandomiguel)]

according to irclogs (http://irclogs.ubuntu.com/2009/10/06/%23ubuntu-mozillateam.html)
it was on the 06/10/2009
but udev changelog https://edge.launchpad.net/ubuntu/karmic/+source/udev/+changelog
only shows changes on 23/09/2009
 -- Scott James Remnant < <email address hidden>> Wed, 23 Sep 2009 14:22:52 -0700

[Alexander Sack (asac)]

please try to downgrade to udev 146-1 then. also try two kernels that existed _before the 6th Oct

[Fernando Miguel (fernandomiguel)]

bah, not sure i still have them! last night i ran janitor to remove several of the old 6 kernels i had!

[Alexander Sack (asac)]

maybe try this kernel: https://edge.launchpad.net/ubuntu/+source/linux/2.6.31-10.35

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 446146, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.