On Thu, Apr 20, 2017 at 09:42:50AM +0200, Alfredo Rafael Vicente Boix wrote: > Hello, > > My name is Alfredo from Spain, I'm a secondary school teacher and I > worked with my students with the lego usb tower, I write you in > reference to the following commit > (2fae9e5a7babada041e2e161699ade2447a01989): > > patch: 9363741 > > I have a little problem with the legousbtower module of kernel. I was > working with kernel 4.4 and I had no problem with this module, each > time that I connected the tower I have the following message in my > log: > > [ 4927.822527] usb 3-1: new low-speed USB device number 2 using xhci_hcd > [ 4928.022168] usb 3-1: New USB device found, idVendor=0694, idProduct=0001 > [ 4928.022185] usb 3-1: New USB device strings: Mfr=4, Product=26, > SerialNumber=0 > [ 4928.022188] usb 3-1: Product: LEGO USB Tower > [ 4928.022190] usb 3-1: Manufacturer: LEGO Group > [ 4929.914818] legousbtower 3-1:1.0: LEGO USB Tower firmware version > is 1.0 build 134 > [ 4929.915157] legousbtower 3-1:1.0: LEGO USB Tower #-160 now attached > to major 180 minor 0 > [ 4929.915517] usbcore: registered new interface driver legousbtower > > > And I can use nqc without any problems. > > Since kernel 4.9 (I've tested it with kernel 4.9 and 4.10), I'm having > the same issue. Each time that I connect the legousbtower I have this > error: > > [ 51.036609] usb 1-2: USB disconnect, device number 5 > [ 53.025125] usb 1-2: new low-speed USB device number 6 using xhci_hcd > [ 53.173087] legousbtower 1-2:1.0: LEGO USB Tower get version > control request failed This looks like a xhci bug/issue, and not specifically a legousbtower issue. What exact kernel release numbers did you try? Can you try the latest 4.10.11 release? There have been a number of xhci bugfixes recently (since 4.9.0) that hopefully should resolve issues like this. Or you can try 4.9.23, that too should have the issues fixed. Please let us know if that works or not. thanks, greg k-h -- 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
