On Mon, Apr 4, 2016 at 8:45 PM, Bin Liu <b-liu@xxxxxx> wrote: > Yegor, > > On Mon, Apr 04, 2016 at 09:03:46AM +0200, Yegor Yefremov wrote: >> > >> > I'm using Debian 8 image with following usb_modeswitch: >> > >> > root@baltos:~# usb_modeswitch -e >> > >> > * usb_modeswitch: handle USB devices with multiple modes >> > * Version 2.2.0 (C) Josua Dietze 2014 >> > * Based on libusb1/libusbx >> > >> > ! PLEASE REPORT NEW CONFIGURATIONS ! >> > >> > Both 3.18.21 and 4.5.0 report following error after MA260 insertion: >> > >> > usb 1-1.2: new high-speed USB device number 3 using musb-hdrc >> > usb 1-1.2: New USB device found, idVendor=2357, idProduct=f000 >> > usb 1-1.2: New USB device strings: Mfr=3, Product=2, SerialNumber=4 >> > usb 1-1.2: Product: TP-LINK HSPA+ Modem >> > usb 1-1.2: Manufacturer: TP-LINK, Incorporated >> > usb 1-1.2: SerialNumber: 863745011099716 >> > usb-storage 1-1.2:1.0: USB Mass Storage device detected >> > scsi host0: usb-storage 1-1.2:1.0 >> > scsi 0:0:0:0: CD-ROM TP-LINK MMC Storage 2.31 PQ: 0 ANSI: 2 >> > scsi 0:0:0:1: Direct-Access TP-LINK MMC Storage 2.31 PQ: 0 ANSI: 2 >> > sd 0:0:0:1: [sda] Attached SCSI removable disk >> > usb 1-1.2: USB disconnect, device number 3 >> > usb 1-1.2: new high-speed USB device number 4 using musb-hdrc >> > usb 1-1.2: New USB device found, idVendor=2357, idProduct=9000 >> > usb 1-1.2: New USB device strings: Mfr=3, Product=2, SerialNumber=4 >> > usb 1-1.2: Product: TP-LINK HSPA+ Modem >> > usb 1-1.2: Manufacturer: TP-LINK, Incorporated >> > usb 1-1.2: SerialNumber: 863745011099716 >> > usb-storage 1-1.2:1.2: USB Mass Storage device detected >> > scsi host1: usb-storage 1-1.2:1.2 >> > qmi_wwan 1-1.2:1.4: cdc-wdm0: USB WDM device >> > qmi_wwan 1-1.2:1.4 wwan0: register 'qmi_wwan' at >> > usb-musb-hdrc.0.auto-1.2, WWAN/QMI device, de:ea:e8:d0:61:6c >> > usbcore: registered new interface driver option >> > usbserial: USB Serial support registered for GSM modem (1-port) >> > option 1-1.2:1.0: GSM modem (1-port) converter detected >> > usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB0 >> > option 1-1.2:1.1: GSM modem (1-port) converter detected >> > usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB1 >> > option 1-1.2:1.3: GSM modem (1-port) converter detected >> > usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB2 >> > scsi 1:0:0:0: CD-ROM TP-LINK MMC Storage 2.31 PQ: 0 ANSI: 2 >> > scsi 1:0:0:1: Direct-Access TP-LINK MMC Storage 2.31 PQ: 0 ANSI: 2 >> > sd 1:0:0:1: [sda] Attached SCSI removable disk >> > ------------[ cut here ]------------ >> > WARNING: CPU: 0 PID: 1740 at drivers/usb/musb/musb_host.c:139 >> > musb_h_tx_flush_fifo+0xc4/0xe4() >> > musb-hdrc musb-hdrc.0.auto: Could not flush host TX2 fifo: csr: 2403 >> > Modules linked in: option usb_wwan musb_dsps musb_am335x >> > CPU: 0 PID: 1740 Comm: ModemManager Not tainted 4.5.0 #1 >> > Hardware name: Generic AM33XX (Flattened Device Tree) >> > [<c0017ecc>] (unwind_backtrace) from [<c0014100>] (show_stack+0x10/0x14) >> > [<c0014100>] (show_stack) from [<c03cf384>] (dump_stack+0xb0/0xe4) >> > [<c03cf384>] (dump_stack) from [<c003bf68>] (warn_slowpath_common+0x7c/0xb8) >> > [<c003bf68>] (warn_slowpath_common) from [<c003bfd4>] >> > (warn_slowpath_fmt+0x30/0x40) >> > [<c003bfd4>] (warn_slowpath_fmt) from [<c0534c30>] >> > (musb_h_tx_flush_fifo+0xc4/0xe4) >> > [<c0534c30>] (musb_h_tx_flush_fifo) from [<c0535d74>] >> > (musb_cleanup_urb+0xbc/0x130) >> > [<c0535d74>] (musb_cleanup_urb) from [<c0536424>] (musb_urb_dequeue+0xf0/0x128) >> > [<c0536424>] (musb_urb_dequeue) from [<c050b98c>] (usb_hcd_unlink_urb+0x50/0x84) >> > [<c050b98c>] (usb_hcd_unlink_urb) from [<c050cbd0>] (usb_kill_urb+0x4c/0xc4) >> > [<c050cbd0>] (usb_kill_urb) from [<bf00e85c>] >> > (usb_wwan_close+0xbc/0xf0 [usb_wwan]) >> > [<bf00e85c>] (usb_wwan_close [usb_wwan]) from [<c042d8e0>] >> > (tty_port_shutdown+0x90/0x9c) >> > [<c042d8e0>] (tty_port_shutdown) from [<c042dfd0>] (tty_port_close+0x24/0x4c) >> > [<c042dfd0>] (tty_port_close) from [<c0425f30>] (tty_release+0xec/0x474) >> > [<c0425f30>] (tty_release) from [<c0168b60>] (__fput+0x80/0x1d0) >> > [<c0168b60>] (__fput) from [<c005b944>] (task_work_run+0x90/0xc4) >> > [<c005b944>] (task_work_run) from [<c0013ac4>] (do_work_pending+0x8c/0xb4) >> > [<c0013ac4>] (do_work_pending) from [<c000f8e8>] (slow_work_pending+0xc/0x20) >> > ---[ end trace cbf0ee35fffa18d3 ]--- >> > >> > Debian image was created with these scripts: >> > https://github.com/visionsystemsgmbh/vsdebootstrap >> > Kernel config: https://github.com/visionsystemsgmbh/onrisc_br_bsp/blob/master/board/vscom/baltos/linux-3.15-config >> > >> > I've tried both usb1 channel and USB hub and usb2 channel directly. In >> > both cases I get this crash. >> >> I've made some more test and could at least find a software >> constellation, that produces this error. You'll need ModemManager and >> libqmi. As soon as ModemManager sees the modem it opens and closes its > > Are you sure it is ModemManager open/close the port? Or other app? Good question. At first I had a rootfs without ModemManager and libqmi and I had no tx errors, but as soon as I added ModemManager I got this issue. Will look more into it tomorrow. > In my debian rootfs, I did > > # apt-get install modemmanager libqmi-utils > > but it seems there is not open/close to the modem uart port. tx fifo > flush problem still does not happen to me. here is the enum log. > > 1 [ 663.745927] usb 2-1: new high-speed USB device number 14 using musb-hdrc > 2 [ 663.890525] usb 2-1: New USB device found, idVendor=2357, idProduct=f000 > 3 [ 663.897857] usb 2-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4 > 4 [ 663.905462] usb 2-1: Product: TP-LINK HSPA+ Modem > 5 [ 663.910666] usb 2-1: Manufacturer: TP-LINK, Incorporated > 6 [ 663.916451] usb 2-1: SerialNumber: 863745011324437 > 7 [ 663.961261] usb-storage 2-1:1.0: USB Mass Storage device detected > 8 [ 663.996977] scsi host12: usb-storage 2-1:1.0 > 9 [ 664.999261] scsi 12:0:0:0: CD-ROM TP-LINK MMC Storage 2.31 PQ: 0 ANSI: 2 > 10 [ 665.010298] scsi 12:0:0:1: Direct-Access TP-LINK MMC Storage 2.31 PQ: 0 ANSI: 2 > 11 [ 665.059673] sd 12:0:0:1: [sda] Attached SCSI removable disk > 12 [ 665.699173] usb 2-1: USB disconnect, device number 14 > 13 [ 666.195929] usb 2-1: new high-speed USB device number 15 using musb-hdrc > 14 [ 666.340925] usb 2-1: New USB device found, idVendor=2357, idProduct=9000 > 15 [ 666.348258] usb 2-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4 > 16 [ 666.356057] usb 2-1: Product: TP-LINK HSPA+ Modem > 17 [ 666.361086] usb 2-1: Manufacturer: TP-LINK, Incorporated > 18 [ 666.366857] usb 2-1: SerialNumber: 863745011324437 > 19 [ 666.422189] option 2-1:1.0: GSM modem (1-port) converter detected > 20 [ 666.448184] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0 > 21 [ 666.461670] option 2-1:1.1: GSM modem (1-port) converter detected > 22 [ 666.488928] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1 > 23 [ 666.501318] usb-storage 2-1:1.2: USB Mass Storage device detected > 24 [ 666.528750] scsi host13: usb-storage 2-1:1.2 > 25 [ 666.543441] option 2-1:1.3: GSM modem (1-port) converter detected > 26 [ 666.573614] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2 > 27 [ 666.613559] qmi_wwan 2-1:1.4: cdc-wdm0: USB WDM device > 28 [ 666.627262] qmi_wwan 2-1:1.4 wwan0: register 'qmi_wwan' at usb-musb-hdrc.1.auto-1, WWAN/QMI device, 22:2f:9a:72:2e:40 > 29 [ 667.542287] scsi 13:0:0:0: CD-ROM TP-LINK MMC Storage 2.31 PQ: 0 ANSI: 2 > 30 [ 667.588101] scsi 13:0:0:1: Direct-Access TP-LINK MMC Storage 2.31 PQ: 0 ANSI: 2 > 31 [ 667.653600] sd 13:0:0:1: [sda] Attached SCSI removable disk Could you post output from: mmcli -m 0 >> interfaces in oder to get modem's configuration. And wwan closing >> seems to produce this error. I could reproduce this behavior with >> am335x-evmsk, Linux 4.5 (omap2plus_defconfig, CONFIG_USB_NET_CDC_MBIM, >> CONFIG_USB_NET_QMI_WWAN and CONFIG_USB_SERIAL_OPTION) and Buildroot >> with enabled ModemManager and libqmi support. >> >> Yegor -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
