I've got some ftdi usb-serial devices causing mass USB hanging on SOME hardware often; it seems when the remote serial device asserts DSR or some such handshaking line.
On a problem device, lsusb shows: Bus 002 Device 001: ID 0000:0000 Bus 001 Device 005: ID 0403:6001 Future Technology Devices International, Ltd 8-bit FIFO Bus 001 Device 002: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd 8-bit FIFO Bus 001 Device 003: ID 058f:9254 Alcor Micro Corp. Hub Bus 001 Device 001: ID 0000:0000 The two 0403:6001 are a single FTDI dual serial adaptor. On my dell laptop or an HP laptop using Ubuntu Feisty (kernel 2.6.20-15) it works fine. On some via chipsets I get foul errors like this when I power up the remote device (at the other end of the serial cable) with minicom used locally. I think the error is when the remote device asserts the DSR or some such handshaking line. (This time the device was plugged into ttyUSB1 while minicom was running on ttyUSB0, and no I don't have brltty installed) shep:~# dmesg -c usb 1-2: USB disconnect, address 3 usb 1-2.1: USB disconnect, address 4 ftdi_sio 1-2.1:1.0: device disconnected usb 1-2.2: USB disconnect, address 5 ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1 ftdi_sio 1-2.2:1.0: device disconnected usb 1-2: new full speed USB device using uhci_hcd and address 6 drivers/usb/serial/ftdi_sio.c: error from flowcontrol urb drivers/usb/serial/ftdi_sio.c: update_mctrl Error from MODEM_CTRL urb: DTR LOW, RTS LOW ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 usb 1-2: device descriptor read/64, error -110 I use: shep:~# rmmod uhci_hcd shep:~# modprobe uhci_hcd to recover which shows: shep:~# dmesg -c usb 1-2: device descriptor read/64, error -110 usb 1-2: new full speed USB device using uhci_hcd and address 7 usb 1-2: device descriptor read/64, error -110 usb 1-2: device descriptor read/64, error -110 usb 1-2: new full speed USB device using uhci_hcd and address 8 uhci_hcd 0000:00:07.3: remove, state 1 usb usb2: USB disconnect, address 1 uhci_hcd 0000:00:07.3: USB bus 2 deregistered uhci_hcd 0000:00:07.2: remove, state 1 usb usb1: USB disconnect, address 1 usb 1-2: device not accepting address 8, error -108 hub 1-0:1.0: cannot disable port 2 (err = -19) hub 1-0:1.0: cannot reset port 2 (err = -19) hub 1-0:1.0: cannot disable port 2 (err = -19) hub 1-0:1.0: cannot disable port 2 (err = -19) usb 1-1: USB disconnect, address 2 uhci_hcd 0000:00:07.2: USB bus 1 deregistered USB Universal Host Controller Interface driver v3.0 PCI: Enabling device 0000:00:07.2 (0000 -> 0001) PCI: Found IRQ 7 for device 0000:00:07.2 PCI: Sharing IRQ 7 with 0000:00:07.3 PCI: Sharing IRQ 7 with 0000:00:0a.0 uhci_hcd 0000:00:07.2: UHCI Host Controller uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1 uhci_hcd 0000:00:07.2: irq 7, io base 0x0000d400 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected PCI: Enabling device 0000:00:07.3 (0000 -> 0001) PCI: Found IRQ 7 for device 0000:00:07.3 PCI: Sharing IRQ 7 with 0000:00:07.2 PCI: Sharing IRQ 7 with 0000:00:0a.0 uhci_hcd 0000:00:07.3: UHCI Host Controller uhci_hcd 0000:00:07.3: new USB bus registered, assigned bus number 2 uhci_hcd 0000:00:07.3: irq 7, io base 0x0000d800 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected usb 1-1: new low speed USB device using uhci_hcd and address 2 usb 1-1: configuration #1 chosen from 1 choice input: CHESEN PS2 to USB Converter as /class/input/input3 input: USB HID v1.10 Keyboard [CHESEN PS2 to USB Converter] on usb-0000:00:07.2-1 input: CHESEN PS2 to USB Converter as /class/input/input4 input: USB HID v1.10 Mouse [CHESEN PS2 to USB Converter] on usb-0000:00:07.2-1 usb 1-2: new full speed USB device using uhci_hcd and address 3 usb 1-2: configuration #1 chosen from 1 choice hub 1-2:1.0: USB hub found hub 1-2:1.0: 4 ports detected usb 1-2.1: new full speed USB device using uhci_hcd and address 4 usb 1-2.1: configuration #1 chosen from 1 choice ftdi_sio 1-2.1:1.0: FTDI USB Serial Device converter detected drivers/usb/serial/ftdi_sio.c: Detected FT232BM usb 1-2.1: FTDI USB Serial Device converter now attached to ttyUSB0 usb 1-2.2: new full speed USB device using uhci_hcd and address 5 usb 1-2.2: configuration #1 chosen from 1 choice ftdi_sio 1-2.2:1.0: FTDI USB Serial Device converter detected drivers/usb/serial/ftdi_sio.c: Detected FT232BM usb 1-2.2: FTDI USB Serial Device converter now attached to ttyUSB1 I've got two of this FTDI device, and both have the same problem. I can pull the power on the remote device all I like and nothing happens, unless one of the ttyUSB is open, even with getty. Just here I had getty running on USB0 and USB1 and applied the power to the USB1 device: shep:~# dmesg -c usb 1-2.2: USB disconnect, address 5 ftdi_sio 1-2.2:1.0: device disconnected usb 1-2.2: new full speed USB device using uhci_hcd and address 6 usb 1-2.2: configuration #1 chosen from 1 choice ftdi_sio 1-2.2:1.0: FTDI USB Serial Device converter detected drivers/usb/serial/ftdi_sio.c: Detected FT232BM usb 1-2.2: FTDI USB Serial Device converter now attached to ttyUSB2 When these errors occur, my USB keyboard stops responding (on Debian 4) and no amount of plugging and unplugging will make it work. I get the same errors from RH9 with kernel 2.4.20-8 through Debian 4 with 2.6.18-4-686 and Ubuntu with 2.6.20-15-generic. So.... what next? ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
