Regression: Huawei E160E does not connect and may freeze system for a while

[Otus]

My Huawei E160E does not work with Precise (12.04). The last good release I can confirm working is Maverick (10.10) which I have on my netbook. I don't have the releases in between installed at the moment.

In Maverick it takes maybe a minute to pop up a dialog about inputting PIN. In Precise the dialog never seems to appear. Additionally, if I use my USB keyboard while the modem is plugged in, the UI often freezes for a few seconds during which time nothing on the screen is updated, keyboard and mouse do not work, but music keeps playing.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: modemmanager 0.5.2.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Thu May 3 18:57:14 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120319)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: modemmanager
UpgradeStatus: No upgrade log present (probably fresh install)

[Otus (jan-varho)]

According to lsusb on the maverick netbook (difficult to type anything on precise) the device is:

Bus 001 Device 012: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E270 HSDPA/HSUPA Modem

On the device itself it says E160E, however.

Attached is what I get in my syslog after plugging the device in and waiting for a few minutes.

[Aleksander Morgado (aleksander-m)]

Ah the mighty E160....

See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/772577

Your description of the problem is quite similar to that bug I reported long ago. specially the "option: option_instat_callback: error -108" errors and the kernel stuck for some seconds during modem probing...

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Massimo (pzmax)]

I have the same problem. I confirm the freezing and the error -108. But isn't modemanager, is a bug of kernel next to 2.6.35-32-generic. In my 12.04 system, i solved installing the kernel version cited above. But i think that is work also with the next version to 13.04.