On Tue, 19 May 2015, Marc MERLIN wrote: > Howdy, > > This is with 3.19, but has been happening with plenty of kernel versions > for years. > > I have a quad core server with > 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) > 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) > 04:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller > > It was dusl core for years, but because it was running out of steam, I figured that maybe > if the cores were stuck with servicing btrfs disk tasks, they wouldn't get back to USB/Serial > in time and cause these problems. > But adding 2 more cores made no difference. > > I have 12+ serial ports via serial/USB on it (almost all ftdi so that I > have serial numbers for each port and can assign them properly). > > My problem is that when cron jobs run, mostly disk intensive ones, my server apparently stops > servicing those serial ports timely, and I get loads of errors with them. > Currently my kernel is built with VOLPREEMPT, although I could change that if you recommend > another option. The problem may have nothing to do with the serial ports. > lsusb: > Bus 004 Device 002: ID 0bc2:50a0 Seagate RSS LLC > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 002 Device 042: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC > Bus 002 Device 041: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC > Bus 002 Device 040: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC > Bus 002 Device 039: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC > Bus 002 Device 038: ID 058f:9254 Alcor Micro Corp. Hub > Bus 002 Device 076: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC > Bus 002 Device 075: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC > Bus 002 Device 074: ID 0409:005a NEC Corp. HighSpeed Hub > Bus 002 Device 073: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC > Bus 002 Device 072: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC > Bus 002 Device 071: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC > Bus 002 Device 070: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC > Bus 002 Device 069: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC > Bus 002 Device 068: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC > Bus 002 Device 067: ID 0409:0050 NEC Corp. > Bus 002 Device 027: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC > Bus 002 Device 022: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC > Bus 002 Device 019: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC > Bus 002 Device 016: ID 1a40:0101 TERMINUS TECHNOLOGY INC. > Bus 002 Device 013: ID 0b95:1780 ASIX Electronics Corp. AX88178 > Bus 002 Device 009: ID 0bc7:0002 X10 Wireless Technology, Inc. Firecracker Interface (ACPI-compliant) > Bus 002 Device 006: ID 1a40:0201 TERMINUS TECHNOLOGY INC. > Bus 002 Device 004: ID 0409:0058 NEC Corp. HighSpeed Hub > Bus 002 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC > Bus 002 Device 002: ID 8087:0024 > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 002: ID 8087:0024 > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Some logs bits if that helps: > [1192409.393119] ftdi_sio ttyUSB10: usb_serial_generic_read_bulk_callback - urb stopped: -32 > [1192409.393246] ftdi_sio ttyUSB4: usb_serial_generic_read_bulk_callback - urb stopped: -32 > [1192409.393248] ftdi_sio ttyUSB2: usb_serial_generic_read_bulk_callback - urb stopped: -32 > [1192409.393491] ftdi_sio ttyUSB10: usb_serial_generic_read_bulk_callback - urb stopped: -32 > [1192409.393751] ftdi_sio ttyUSB4: usb_serial_generic_read_bulk_callback - urb stopped: -32 > [1192409.393989] ftdi_sio ttyUSB2: usb_serial_generic_read_bulk_callback - urb stopped: -32 > [1192409.826753] usb 2-1.4.3: USB disconnect, device number 28 > [1192409.844839] usb 2-1.4.3.1: USB disconnect, device number 29 > > This is likely one of my cronjobs that sees high level serial failure and reboots the > USB serial converters: > [1192409.863482] ftdi_sio ttyUSB2: FTDI USB Serial Device converter now disconnected from ttyUSB2 > [1192409.890563] ftdi_sio 2-1.4.3.1:1.0: device disconnected > [1192409.908200] usb 2-1.4.3.2: USB disconnect, device number 30 > [1192409.926805] ftdi_sio ttyUSB4: FTDI USB Serial Device converter now disconnected from ttyUSB4 > [1192409.953878] ftdi_sio 2-1.4.3.2:1.0: device disconnected > [1192409.971434] usb 2-1.4.3.3: USB disconnect, device number 31 > [1192409.990305] ftdi_sio ttyUSB5: FTDI USB Serial Device converter now disconnected from ttyUSB5 > [1192410.017380] ftdi_sio 2-1.4.3.3:1.0: device disconnected > [1192410.035183] usb 2-1.4.3.4: USB disconnect, device number 32 > [1192410.053640] ftdi_sio ttyUSB10: error from flowcontrol urb > [1192410.071650] ftdi_sio ttyUSB10: FTDI USB Serial Device converter now disconnected from ttyUSB10 > [1192410.099098] ftdi_sio 2-1.4.3.4:1.0: device disconnected > [1192410.332639] usb 2-1.4.3: new full-speed USB device number 33 using ehci-pci > [1192410.462036] usb 2-1.4.3: New USB device found, idVendor=058f, idProduct=9254 > [1192410.485630] usb 2-1.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 > [1192410.509952] usb 2-1.4.3: Product: Generic USB Hub > [1192410.540441] hub 2-1.4.3:1.0: USB hub found > [1192410.555232] hub 2-1.4.3:1.0: 4 ports detected This strongly suggests that the problem lies in the hubs (or in one of them). Something caused a hub to disconnect, and when that happened all of the serial ports downstream from that hub went along for the ride. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
