[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1406191059520.1247-100000@iolanthe.rowland.org>
Date: Thu, 19 Jun 2014 11:02:39 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: Jörg Otte <jrg.otte@...il.com>
cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
USB list <linux-usb@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [usb resume regression] in 3.16-rc1
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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists