long standing boot error message

[Jon LaBadie]

My system is about 2 yrs old and started with F19 or
earlier version.  It has always had one boot error
I'm unable to resolve.  Nothing seems to be not
working, so I ponder once in a while.

Anybody recognize this error message?

   usb 2-1.5: string descriptor 0 read error: -22

Jon
-- 
Jon H. LaBadie                  jonfu(a)jgcomp.com

[fred roller]

On Sun, Oct 9, 2016 at 5:32 PM, Jon LaBadie <jonfu(a)jgcomp.com&gt; wrote:

>  Anybody recognize this error message?
>
>     usb 2-1.5: string descriptor 0 read error: -22
>  
According to:

http://www.keil.com/pack/doc/mw/USB/html/_u_s_b__string__descriptor.html

"String descriptors (USB_STRING_DESCRIPTOR) are optional and add human
readable information to the other descriptors. If a device does not support
string descriptors, all references to string descriptors within device,
configuration, and interface descriptors must be set to zero."

Just sounds like your system doesn't know and is telling you as much.  Look
along your second usb bus line, especially if you have a card reader or
some such.

-- Fred

[Samuel Sieb]

On 10/09/2016 02:32 PM, Jon LaBadie wrote:
>  Anybody recognize this error message?
>
>     usb 2-1.5: string descriptor 0 read error: -22
>  
I've seen messages like that often.  I think some devices don't support 
all the descriptors the kernel tries to read or something like that. 
You can find out which device it is by going to 
/sys/bus/usb/devices/2-1.5 and checking out some of the info there. 
Particularly try "cat product".

[Jon LaBadie]

On Sun, Oct 09, 2016 at 06:20:03PM -0400, fred roller wrote:
>  On Sun, Oct 9, 2016 at 5:32 PM, Jon LaBadie <jonfu(a)jgcomp.com&gt;
> wrote:
>  
>  > Anybody recognize this error message?
>  >
>  >    usb 2-1.5: string descriptor 0 read error: -22
>  >
>  
>  According to:
>  
>  http://www.keil.com/pack/doc/mw/USB/html/_u_s_b__string__descriptor.html
>  
>  "String descriptors (USB_STRING_DESCRIPTOR) are optional and add human
>  readable information to the other descriptors. If a device does not support
>  string descriptors, all references to string descriptors within device,
>  configuration, and interface descriptors must be set to zero."
>  
>  Just sounds like your system doesn't know and is telling you as much.  Look
>  along your second usb bus line, especially if you have a card reader or
>  some such.
>  
>  -- Fred 
On Sun, Oct 09, 2016 at 03:21:01PM -0700, Samuel Sieb wrote:
>  On 10/09/2016 02:32 PM, Jon LaBadie wrote:
>  > Anybody recognize this error message?
>  > 
>  >    usb 2-1.5: string descriptor 0 read error: -22
>  > 
>  I've seen messages like that often.  I think some devices don't support all
>  the descriptors the kernel tries to read or something like that. You can
>  find out which device it is by going to /sys/bus/usb/devices/2-1.5 and
>  checking out some of the info there. Particularly try "cat product". 
Well that got me further, thanks.

No "product" listing, but there are vendor and product ids.
The device is my "internal" BlueTooth adapter made by Lite-On.
Based on adjacent product codes, it uses an Atheros chip.
Obviously using a usb interface, much as a BT-dongle would.

Sometime when I have the case open for dust bunny removal I'll
check to see if the BT adapter hooks into a MB USB header.

Though seldom used, the BT device was functioning the few times
I've tried it, so I guess I'll just consider the boot message an
informational warning.

Thanks again,
jon
-- 
Jon H. LaBadie                  jonfu(a)jgcomp.com

[Samuel Sieb]

On 10/09/2016 04:25 PM, Jon LaBadie wrote:
>  No "product" listing, but there are vendor and product
> ids.
>  The device is my "internal" BlueTooth adapter made by Lite-On.
>  Based on adjacent product codes, it uses an Atheros chip.
>  Obviously using a usb interface, much as a BT-dongle would.
>
>  Sometime when I have the case open for dust bunny removal I'll
>  check to see if the BT adapter hooks into a MB USB header.
>  
Interesting, I've never seen a desktop with built-in bluetooth, although 
I've also had very little to do with any recent desktop systems.  But at 
least on laptops, the bluetooth is usually hooked into the USB bus.

>  Though seldom used, the BT device was functioning the few times
>  I've tried it, so I guess I'll just consider the boot message an
>  informational warning.
>  
Yes, I'm pretty sure it's just informational, nothing critical. 
Although given that the product information was missing, that might be 
the descriptor it was trying to read.

[Jon LaBadie]

On Sun, Oct 09, 2016 at 11:48:11PM -0700, Samuel Sieb wrote:
>  On 10/09/2016 04:25 PM, Jon LaBadie wrote:
>  > No "product" listing, but there are vendor and product ids.
>  > The device is my "internal" BlueTooth adapter made by Lite-On.
>  > Based on adjacent product codes, it uses an Atheros chip.
>  > Obviously using a usb interface, much as a BT-dongle would.
>  > 
>  > Sometime when I have the case open for dust bunny removal I'll
>  > check to see if the BT adapter hooks into a MB USB header.
>  > 
>  Interesting, I've never seen a desktop with built-in bluetooth, although
>  I've also had very little to do with any recent desktop systems.  But at
>  least on laptops, the bluetooth is usually hooked into the USB bus. 
I just looked on-line as a few PCI bluetooth adapters.  All that I saw
were combo WiFi/Bluetooth.  They all had either a female USB connector
on the card or a 4 pin header labeled USB.

>  > Though seldom used, the BT device was functioning the few times
>  > I've tried it, so I guess I'll just consider the boot message an
>  > informational warning.
>  > 
>  Yes, I'm pretty sure it's just informational, nothing critical. Although
>  given that the product information was missing, that might be the descriptor
>  it was trying to read. 
There was an entry in /sys/bus/usb/devices/2-1.5 called descriptors.
Trying to pair that with the reference Fred pointed me to makes me
think the descriptors don't match the standard.  The first data
field seems an invalid size and value.  Maybe that is why the
message is being printed.

-- 
Jon H. LaBadie                  jonfu(a)jgcomp.com

[François Patte]

Le 09/10/2016 à 23:32, Jon LaBadie a écrit :
>  My system is about 2 yrs old and started with F19 or
>  earlier version.  It has always had one boot error
>  I'm unable to resolve.  Nothing seems to be not
>  working, so I ponder once in a while.
>  
>  Anybody recognize this error message?
>  
>     usb 2-1.5: string descriptor 0 read error: -22 
Have you some device plugged in an usb port (except a keyboard and a
mouse)?

-- 
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. [phone]
http://www.math-info.univ-paris5.fr/~patte

[Jon LaBadie]

On Tue, Oct 11, 2016 at 08:12:36AM +0200, François Patte wrote:
>  Le 09/10/2016 à 23:32, Jon LaBadie a écrit :
>  > My system is about 2 yrs old and started with F19 or
>  > earlier version.  It has always had one boot error
>  > I'm unable to resolve.  Nothing seems to be not
>  > working, so I ponder once in a while.
>  > 
>  > Anybody recognize this error message?
>  > 
>  >    usb 2-1.5: string descriptor 0 read error: -22
>  
>  Have you some device plugged in an usb port (except a keyboard and a
>  mouse)?
>   
Not to an external usb port.  There is a card reader hooked to a
MB usb header.  We've also determined that the above port is
internally connected to a BlueTooth card.

jl
-- 
Jon H. LaBadie                  jonfu(a)jgcomp.com