@sardylan, seems we're having the same issue here, yes. >From your logs, these are the steps: 1) modem-manager gets the notifications about new ttyUSB0 and ttyUSB1; 2) then defers the probing of port ttyUSB1 (because udev reports ttyUSB1 with interface id 1) 3) starts probing ttyUSB0 (the one with interface id 0); 4) probing port ttyUSB0 succeeds; 5) and starts probing ttyUSB1 (at 20:13:13) 6) kernel hangs for 10s, and meanwhile dumps the "option_instat_callback: error -108" error and closes ttyUSB0 7) modem-manager gets the error about not being able to open ttyUSB1 8) modem-manager marks the modem as invalid because we lost ttyUSB0
The relevant chunk in the logs: May 17 20:13:12 picci modem-manager[9893]: <debug> [1305655992.268449] [mm-manager.c:239] check_export_modem(): (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-5 May 17 20:13:13 picci modem-manager[9893]: <debug> [1305655993.023318] [mm-manager.c:450] supports_defer_timeout(): (ttyUSB1): re-checking support... May 17 20:13:13 picci modem-manager[9893]: <info> [1305655993.024451] [mm-serial-port.c:702] mm_serial_port_open(): (ttyUSB1) opening serial port... May 17 20:13:17 picci kernel: [ 2572.020224] option: option_instat_callback: error -108 May 17 20:13:17 picci kernel: [ 2572.020426] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0 May 17 20:13:17 picci kernel: [ 2572.020477] option 1-5:1.0: device disconnected May 17 20:13:23 picci modem-manager[9893]: <warn> [1305656003.016966] [mm-plugin-huawei.c:247] supports_port(): (Huawei) ttyUSB1: couldn't open serial port: (0) Could not lock serial device ttyUSB1: Input/output error May 17 20:13:23 picci modem-manager[9893]: <debug> [1305656003.017161] [mm-manager.c:617] supports_callback(): (tty/ttyUSB1): ignoring port unsupported by physical modem's plugin May 17 20:13:23 picci modem-manager[9893]: <debug> [1305656003.017416] [mm-manager.c:261] check_export_modem(): Exported modem /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-5 as /org/freedesktop/ModemManager/Modems/0 May 17 20:13:23 picci modem-manager[9893]: <debug> [1305656003.017598] [mm-manager.c:274] check_export_modem(): (/org/freedesktop/ModemManager/Modems/0): VID 0x12D1 PID 0x1003 (usb) May 17 20:13:23 picci modem-manager[9893]: <debug> [1305656003.017636] [mm-manager.c:275] check_export_modem(): (/org/freedesktop/ModemManager/Modems/0): data port is ttyUSB0 May 17 20:13:23 picci modem-manager[9893]: <info> [1305656003.019629] [mm-manager.c:855] device_removed(): (tty/ttyUSB0): released by modem /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-5 May 17 20:13:23 picci modem-manager[9893]: <debug> [1305656003.019769] [mm-modem-base.c:185] mm_modem_base_remove_port(): (ttyUSB0) type primary removed from /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-5 May 17 20:13:23 picci modem-manager[9893]: <debug> [1305656003.019899] [mm-manager.c:200] remove_modem(): Removed modem /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-5 As an additional note when I first analyzed the issue, note that after the first attempt, udev now reports ttyUSB1 as having interface Id 0, and ttyUSB0 as having interface id 1 (modem-manager always defers check of port in the huawei plugin if interface id != 0). In the following logs, the port being deferred is ttyUSB0, while ttyUSB1 gets probed (see that the AT+GCAP reply while probing the ttyUSB1 doesn't contain +FCLASS, while the reply in ttyUSB0 does contain it, so the interface id value 0 is really being moved from ttyUSB0 to ttyUSB1 after the first round). May 17 20:13:23 picci modem-manager[9893]: <debug> [1305656003.357896] [mm-manager.c:484] try_supports_port(): (Huawei): (ttyUSB0) deferring support check May 17 20:13:23 picci modem-manager[9893]: <info> [1305656003.359517] [mm-serial-port.c:702] mm_serial_port_open(): (ttyUSB1) opening serial port... May 17 20:13:23 picci modem-manager[9893]: <debug> [1305656003.362351] [mm-serial-port.c:764] mm_serial_port_open(): (ttyUSB1) device open count is 1 (open) May 17 20:13:23 picci modem-manager[9893]: <debug> [1305656003.362425] [mm-plugin-base.c:838] try_open(): (ttyUSB1): probe requested by plugin 'Huawei' May 17 20:13:23 picci modem-manager[9893]: <debug> [1305656003.464362] [mm-at-serial-port.c:298] debug_log(): (ttyUSB1): --> 'AT+GCAP<CR>' May 17 20:13:24 picci modem-manager[9893]: <debug> [1305656004.265215] [mm-at-serial-port.c:298] debug_log(): (ttyUSB1): <-- '<CR><LF>+GCAP: +CGSM,+DS,+ES<CR><LF><CR><LF>OK<CR><LF>' May 17 20:13:24 picci modem-manager[9893]: <debug> [1305656004.265433] [mm-serial-port.c:798] mm_serial_port_close(): (ttyUSB1) device open count is 0 (close) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/772577 Title: Kernel in Natty disconnects Huawei E160G, ModemManager can't use it -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
