"-517" is -EPROBE_DEFER, it means some resources for this device
are not ready.
Thanks for the info, I fell on it too on a completely different box but
had no time to find what it is. Now it is clear what is going on.
Here is how the bug reporter fell on it:
dmesg shows that he performed an ACPI S3 transition:
"ACPI: Preparing to enter system sleep state S3"
then he resumed:
"ACPI: Waking up from system sleep state S3"
and the WebCam device failed to resume properly after S3 resume when it
was reset...
It is specific to the attached device.
Last friday, I had similar findings on my AMD box with an ASMedia XHCI
controller. The USB device causing it is a combo dongle. It is a dongle
with a blue LED having an on-board hub chip with two attached devices. A
USB to IrDA controller and a USB bluetooth controller. I suspect that
the device fails to resume both devices properly because of async
suspend-resume. Something similar was observed on libata with combo
devices such as JMicron controllers.
The suspend issue is not new, I fell on it with Ubuntu 16.04 and when
resuming from S3:
[ 3183.832344] dpm_run_callback(): usb_dev_resume+0x0/0x20 returns -5
[ 3183.832356] PM: Device 4-2.1 failed to resume async: error -5
After switching to the last Ubuntu the same device did not operate on
first plug at Ubuntu 16.10 with 4.8.0-26 as I got:
[ 353.027824] usb 3-2.2: device descriptor read/64, error -62
and
[ 354.783808] usb 3-2.2: device not accepting address 8, error -62
[ 354.784433] usb 3-2-port2: unable to enumerate USB device
while the bluetooth LED was off.
Next time I plugged it in, it worked at Ubuntu 16.10 and I performed an
S3 on purpose. After resume from S3 I got the usual error plus the 517
error:
[ 130.842066] usb 3-2.1: reset full-speed USB device number 4 using
ohci-pci
[ 130.959091] dpm_run_callback(): usb_dev_resume+0x0/0x20 returns -5
[ 130.959094] PM: Device 3-2.1 failed to resume async: error -5
[ 131.030092] usb 3-2.2: reset full-speed USB device number 5 using
ohci-pci
[ 131.148471] PM: resume of devices complete after 1088.242 msecs
[ 131.148538] usb 3-2.2:1.0: rebind failed: -517
[ 131.148550] usb 3-2.2:1.1: rebind failed: -517
[ 131.148954] PM: Finishing wakeup.
Here is the combo dongle and its devices:
lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/4p, 12M
|__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/2p, 12M
|__ Port 1: Dev 5, If 0, Class=(Defined at Interface level),
Driver=, 12M
|__ Port 2: Dev 4, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 2: Dev 4, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 2: Dev 4, If 2, Class=Application Specific Interface,
Driver=, 12M
Bus 004 Device 002: ID 0451:2036 Texas Instruments, Inc. TUSB2036 Hub
Bus 004 Device 004: ID 1131:1001 Integrated System Solution Corp.
KY-BT100 Bluetooth Adapter
Bus 004 Device 005: ID 0e55:110a Speed Dragon Multimedia, Ltd Tanic
S110-SG1 + ISSC IS1002N [Slow Infra-Red (SIR) & Bluetooth 1.2 (Class 2)
Adapter]
Tonight I will plug it on the onboard AMD XHCI controller to see if it
does the same thing.
On the same installation a USB stick has another PM related issue
[ 2.709375] scsi host4: runtime PM trying to activate child device
host4 but parent (2-1:1.0) is not active
--
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
