Bug 206339 - On v5.5.rc2 For "lsusb -v" it shows as "can't get device qualifier: Resource temporarily unavailable, can't get debug descriptor: Resource temporarily unavailable"
Summary: On v5.5.rc2 For "lsusb -v" it shows as "can't get device qualifier: Resource ...
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: USB (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Default virtual assignee for Drivers/USB
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-28 10:31 UTC by Sudarshan
Modified: 2020-06-30 01:27 UTC (History)
2 users (show)

See Also:
Kernel Version: all the recent versions from 4.14 onwards
Subsystem:
Regression: No
Bisected commit-id:


Attachments
For "lsusb -v" it shows as "can't get device qualifier: Resource temporarily unavailable" (10.96 KB, text/plain)
2020-01-28 10:31 UTC, Sudarshan
Details

Description Sudarshan 2020-01-28 10:31:48 UTC
Created attachment 287009 [details]
For "lsusb -v" it shows as "can't get device qualifier: Resource temporarily unavailable"

Hi,

1. On recent ML v5.5.rc2 when i give cmd "lsusb -v", i see below errors from USB internal hubs.Same issue is seen on Yacto & Ubuntu desktop PCs.

2. There is no functionality issue seen so far... USB mounting, enumeration works as expected.

3. Issue started noticed from v4.14 onwards.
The same issue is not seen on v4.1.49.

Error:
======
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
...
...
...
"can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable"

4. Does it mean while parsing/decoding USB device descriptor info from ACPI is something went wrong ? or something wrong from usb utils/libs ?

I tried debugging, but i am not expert on USB so could not get the RC yet.

5. Can someone please help to share the fix details/possible fix, if you know it already.

FYI... PFA logs for more info.


Thanks
Sudarshan
Comment 1 Reyy kakeru 2020-06-02 18:11:20 UTC
Created attachment 289473 [details]
KONTOL

Oalah asuuu asu
Comment 2 Zhang Rui 2020-06-29 11:34:35 UTC
reassign to the USB experts
Comment 3 Alan Stern 2020-06-30 01:27:19 UTC
Try running "sudo lsusb -v" instead.

Note You need to log in before you can comment on or make changes to this bug.