Re: integrated bluetooth adapter causes errors in dmesg on boot
lsusb (usbutils) 007 "This means the adapter sent an invalid string descriptor to the computer" linux-usb@vger.kernel.org -- 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: integrated bluetooth adapter causes errors in dmesg on boot
On Tue, Jun 02, 2015 at 06:16:20PM +0300, Alexander wrote: > Hello. I have got "Asus Z87-Expert" motherboard with integrated bluetooth > adapter. It causes the following error on boot: > "usb 3-4: string descriptor 0 malformed (err = -61), defaulting to 0x0409" > Though there are no real problems with bluetooth, this error is annoying. > Here is some information: > > dmesg | grep 3-4 > [ 2.037896] usb 3-4: new full-speed USB device number 4 using xhci_hcd > [ 2.167450] usb 3-4: string descriptor 0 malformed (err = -61), defaulting > to 0x0409 > [ 2.169268] usb 3-4: New USB device found, idVendor=0b05, idProduct=17d0 > [ 2.169269] usb 3-4: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > > lsusb | grep 0b05 > Bus 003 Device 004: ID 0b05:17d0 ASUSTek Computer, Inc. > If I run lsusb -v in 3.16.0, I get an error > "lsusb: gconv.c:74: __gconv: Assertion `outbuf != ((void *)0) && *outbuf != > ((void *)0)' failed." That's a really odd error, as lsusb doesn't use gconv, neither does libusb, where does that file (gconv.c) come from? What version of lsusb are you using? 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: integrated bluetooth adapter causes errors in dmesg on boot
On Tue, 2 Jun 2015, Alexander wrote: > Hello. I have got "Asus Z87-Expert" motherboard with integrated > bluetooth adapter. It causes the following error on boot: > "usb 3-4: string descriptor 0 malformed (err = -61), defaulting to 0x0409" This means the bluetooth adapter sent an invalid string descriptor to the computer. > Though there are no real problems with bluetooth, this error is annoying. > Here is some information: > > dmesg | grep 3-4 > [ 2.037896] usb 3-4: new full-speed USB device number 4 using xhci_hcd > [ 2.167450] usb 3-4: string descriptor 0 malformed (err = -61), > defaulting to 0x0409 > [ 2.169268] usb 3-4: New USB device found, idVendor=0b05, idProduct=17d0 > [ 2.169269] usb 3-4: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > > lsusb | grep 0b05 > Bus 003 Device 004: ID 0b05:17d0 ASUSTek Computer, Inc. Maybe you should complain to the manufacturer. > If I run lsusb -v in 3.16.0, I get an error > "lsusb: gconv.c:74: __gconv: Assertion `outbuf != ((void *)0) && *outbuf > != ((void *)0)' failed." > just before the information should be displayed about this device. A bug in lsusb? > However, if I run 4.0.4, this device changes it's number to "1-4" and That's normal; it doesn't mean anything. > here is information about it: > > lsusb -v > http://pastebin.com/raw.php?i=veR7PUnb > dmesg also shows another error with 4.0.4 > > usb 1-4: string descriptor 0 read error: -22 Of course, because the device isn't doing what it is supposed to do. 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
integrated bluetooth adapter causes errors in dmesg on boot
Hello. I have got "Asus Z87-Expert" motherboard with integrated bluetooth adapter. It causes the following error on boot: "usb 3-4: string descriptor 0 malformed (err = -61), defaulting to 0x0409" Though there are no real problems with bluetooth, this error is annoying. Here is some information: > dmesg | grep 3-4 [ 2.037896] usb 3-4: new full-speed USB device number 4 using xhci_hcd [ 2.167450] usb 3-4: string descriptor 0 malformed (err = -61), defaulting to 0x0409 [ 2.169268] usb 3-4: New USB device found, idVendor=0b05, idProduct=17d0 [ 2.169269] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > lsusb | grep 0b05 Bus 003 Device 004: ID 0b05:17d0 ASUSTek Computer, Inc. If I run lsusb -v in 3.16.0, I get an error "lsusb: gconv.c:74: __gconv: Assertion `outbuf != ((void *)0) && *outbuf != ((void *)0)' failed." just before the information should be displayed about this device. However, if I run 4.0.4, this device changes it's number to "1-4" and here is information about it: > lsusb -v http://pastebin.com/raw.php?i=veR7PUnb dmesg also shows another error with 4.0.4 > usb 1-4: string descriptor 0 read error: -22 -- 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
