Re: usb 3-4: unable to get BOS descriptor
On Thu, 11 May 2017, Cristian wrote: > Hi, > > 2017-05-11 20:45 GMT+00:00 Alan Stern : > > On Thu, 11 May 2017, Cristian wrote: > > > >> Hi, > >> > >> Attach dmesg > >> [ 968.998463] usb 3-4: unable to get BOS descriptor > >> [ 968.999477] usb 3-4: config 1 has an invalid descriptor of length > >> 1, skipping remainder of the config > >> [ 968.999483] usb 3-4: config 1 has 0 interfaces, different from the > >> descriptor's value: 1 > >> [ 969.001897] usb 3-4: language id specifier not provided by device, > >> defaulting to English > > > > It looks like your device didn't work right the first time you plugged > > it in. But it worked correctly the second time, on a different port, > > according to the log attached to your email. Maybe port 4 is bad. > > > > Does this happen often? > > This does not happen often. Then you shouldn't worry about it. In any case, it seems likely that this is a hardware problem, not a software problem. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: usb 3-4: unable to get BOS descriptor
Hi, 2017-05-11 20:45 GMT+00:00 Alan Stern : > On Thu, 11 May 2017, Cristian wrote: > >> Hi, >> >> Attach dmesg >> [ 968.998463] usb 3-4: unable to get BOS descriptor >> [ 968.999477] usb 3-4: config 1 has an invalid descriptor of length >> 1, skipping remainder of the config >> [ 968.999483] usb 3-4: config 1 has 0 interfaces, different from the >> descriptor's value: 1 >> [ 969.001897] usb 3-4: language id specifier not provided by device, >> defaulting to English > > It looks like your device didn't work right the first time you plugged > it in. But it worked correctly the second time, on a different port, > according to the log attached to your email. Maybe port 4 is bad. > > Does this happen often? This does not happen often. -- Cristian -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: usb 3-4: unable to get BOS descriptor
On Thu, 11 May 2017, Cristian wrote: > Hi, > > Attach dmesg > [ 968.998463] usb 3-4: unable to get BOS descriptor > [ 968.999477] usb 3-4: config 1 has an invalid descriptor of length > 1, skipping remainder of the config > [ 968.999483] usb 3-4: config 1 has 0 interfaces, different from the > descriptor's value: 1 > [ 969.001897] usb 3-4: language id specifier not provided by device, > defaulting to English It looks like your device didn't work right the first time you plugged it in. But it worked correctly the second time, on a different port, according to the log attached to your email. Maybe port 4 is bad. Does this happen often? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: usb 3-4: unable to get BOS descriptor
A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? A: No. Q: Should I include quotations after my reply? http://daringfireball.net/2007/07/on_top On Thu, May 11, 2017 at 03:28:21PM -0300, Cristian wrote: > Hi, > > Attach command. What about answering the other questions? And can you provide only the lsusb -v output for the specific device you are concerned about here? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: usb 3-4: unable to get BOS descriptor
Hi, Attach command. Regards, -- Cristian 2017-05-11 15:22 GMT-03:00 Greg KH : > On Thu, May 11, 2017 at 02:58:24PM -0300, Cristian wrote: >> Hi, >> >> Attach dmesg >> [ 968.998463] usb 3-4: unable to get BOS descriptor > > Device still works, right? > >> [ 968.999477] usb 3-4: config 1 has an invalid descriptor of length >> 1, skipping remainder of the config > > Ick, messy device. > >> [ 968.999483] usb 3-4: config 1 has 0 interfaces, different from the >> descriptor's value: 1 >> [ 969.001897] usb 3-4: language id specifier not provided by device, >> defaulting to English > > Really messy device, what is the configuration of this thing? What is > it? > > Can you provide the output of 'lsusb -v' for just this device? > > thanks, > > greg k-h -- Cristian Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 1 Single TT bMaxPacketSize064 idVendor 0x8087 Intel Corp. idProduct 0x0024 Integrated Rate Matching Hub bcdDevice0.00 iManufacturer 0 iProduct0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 12 Hub Descriptor: bLength 9 bDescriptorType 41 nNbrPorts 6 wHubCharacteristic 0x0009 Per-port power switching Per-port overcurrent protection TT think time 8 FS bits bPwrOn2PwrGood 50 * 2 milli seconds bHubContrCurrent 0 milli Ampere DeviceRemovable0x00 PortPwrCtrlMask0xff Hub Port Status: Port 1: .0100 power Port 2: .0100 power Port 3: .0100 power Port 4: .0100 power Port 5: .0100 power Port 6: .0100 power Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize064 bNumConfigurations 1 Device Status: 0x0001 Self Powered Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize064 idVendor 0x1d6b Linux Foundation idProduct 0x0002 2.0 root hub bcdDevice4.11 iManufacturer 3 Linux 4.11.0-041100-generic ehci_hcd iProduct2 EHCI Host Controller iSerial 1 :00:1d.0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 Hub Descriptor: bLength 9 bDescriptorType 41 nNbrPorts 3 wHubCharac
Re: usb 3-4: unable to get BOS descriptor
On Thu, May 11, 2017 at 02:58:24PM -0300, Cristian wrote: > Hi, > > Attach dmesg > [ 968.998463] usb 3-4: unable to get BOS descriptor Device still works, right? > [ 968.999477] usb 3-4: config 1 has an invalid descriptor of length > 1, skipping remainder of the config Ick, messy device. > [ 968.999483] usb 3-4: config 1 has 0 interfaces, different from the > descriptor's value: 1 > [ 969.001897] usb 3-4: language id specifier not provided by device, > defaulting to English Really messy device, what is the configuration of this thing? What is it? Can you provide the output of 'lsusb -v' for just this device? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
