https://bugzilla.kernel.org/show_bug.cgi?id=198165 Richard Mauger (rmauger.var@xxxxxxxxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rmauger.var@xxxxxxxxxxxxxxx --- Comment #1 from Richard Mauger (rmauger.var@xxxxxxxxxxxxxxx) --- I think this issue should be assigned to linux-usb@xxxxxxxxxxxxxxx. It looks like a USB problem instead of Bluetooth. I have a similar result on a HP Z2 Mini connected by USB 2.0 cable to a HP Z22n monitor. The HP Z22n has a built in USB 2.0 hub. Using Fedora kernel 4.14.3-300.fc27.x86_64 this is the working journalctl output: kernel: usb 1-4: new high-speed USB device number 3 using xhci_hcd kernel: usb 1-4: New USB device found, idVendor=0424, idProduct=2512 kernel: usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 kernel: hub 1-4:1.0: USB hub found kernel: hub 1-4:1.0: 2 ports detected kernel: usb 1-4.1: new low-speed USB device number 5 using xhci_hcd kernel: usb 1-4.1: New USB device found, idVendor=04d9, idProduct=4545 kernel: usb 1-4.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0 kernel: usb 1-4.1: Product: USB Keyboard kernel: input: USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/1-4.1:1.0/0003:04D9:4545.0002/input/input3 kernel: usb 1-4.2: new full-speed USB device number 6 using xhci_hcd kernel: usb 1-4.2: New USB device found, idVendor=046d, idProduct=c52b kernel: usb 1-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 kernel: usb 1-4.2: Product: USB Receiver kernel: usb 1-4.2: Manufacturer: Logitech However with Fedora kernel 4.14.5-300.fc27.x86_64 the HP Z22n USB 2.0 hub is effectively disabled with this journalctl output: kernel: usb 1-4: new full-speed USB device number 3 using xhci_hcd kernel: usb 1-4: device descriptor read/64, error -71 kernel: usb 1-4: device descriptor read/64, error -71 kernel: usb 1-4: new full-speed USB device number 4 using xhci_hcd kernel: usb 1-4: device descriptor read/64, error -71 kernel: usb 1-4: device descriptor read/64, error -71 kernel: usb usb1-port4: attempt power cycle kernel: usb 1-4: new full-speed USB device number 5 using xhci_hcd kernel: usb 1-4: Device not responding to setup address. kernel: usb 1-4: Device not responding to setup address. kernel: usb 1-4: device not accepting address 5, error -71 kernel: usb 1-4: new full-speed USB device number 6 using xhci_hcd kernel: usb 1-4: Device not responding to setup address. kernel: usb 1-4: Device not responding to setup address. kernel: usb 1-4: device not accepting address 6, error -71 kernel: usb usb1-port4: unable to enumerate USB device I think the block of code that runs the 'attempt power cycle' is part of kernel commit 973593a960ddac0f14f0d8877d2d0abe0afda795 on 20171128. File drivers/usb/core/hub.c has the following block addition in hub_port_connect() against 973593a960ddac0f14f0d8877d2d0abe0afda795: /* When halfway through our retry count, power-cycle the port */ if (i == (SET_CONFIG_TRIES / 2) - 1) { dev_info(&port_dev->dev, "attempt power cycle\n"); usb_hub_set_port_power(hdev, hub, port1, false); msleep(2 * hub_power_on_good_delay(hub)); usb_hub_set_port_power(hdev, hub, port1, true); msleep(hub_power_on_good_delay(hub)); } The 'device descriptor read/64, error -71' output looks like it is probably getting generated by hub_port_init() in the same file. -- You are receiving this mail because: You are the assignee for the bug.-- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
