On Thu, 19 Jun 2014, Jörg Otte wrote: > on resume with 3.16-rc1 I get the following error messages in dmesg > which are alltogether not present in 3.15: > > [ 43.518116] dpm_run_callback(): 0xffffffffa53c4120 returns -13 > [ 43.518119] PM: Device 1-1 failed to resume async: error -13 > [ 43.522380] hub 1-1:1.0: hub_port_status failed (err = -71) > [ 43.528538] sd 0:0:0:0: [sda] Starting disk > [ 43.530886] hub 1-1:1.0: hub_port_status failed (err = -71) > [ 43.535140] usb 1-1-port2: cannot disable (err = -71) > [ 43.535142] dpm_run_callback(): 0xffffffffa53c4120 returns -71 > [ 43.535145] PM: Device 1-1.2 failed to resume async: error -71 > [ 43.543673] usb 1-1-port4: cannot disable (err = -71) > [ 43.543674] dpm_run_callback(): 0xffffffffa53c4120 returns -71 > [ 43.543679] PM: Device 1-1.4 failed to resume async: error -71 > > usb devices connected to the hub (in my case mouse and keyboard) are > all death after resume and cannot be activated again. -13 is -EACCES. It's not clear what could have caused that error, since EACCES isn't used in the USB core or in ehci-hcd. Can you try doing the same thing after enabling dynamic debugging in usbcore and ehci-hcd? Alan Stern -- 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
