From: Alan Stern <stern@rowland.harvard.edu>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Linux PM List <linux-pm@lists.linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-usb@vger.kernel.org
Subject: Re: linux-next: Tree for Apr 24 [ PM: Device 1-1.2 failed to resume async: error -32 ]
Date: Thu, 25 Apr 2013 11:49:51 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44L0.1304251145110.948-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <CA+icZUX96ADfV5rxce+2t4J870BvZTPGOCCSgVcJ8_Hc2RMxeg@mail.gmail.com>
On Thu, 25 Apr 2013, Sedat Dilek wrote:
> [ Run logging on USB-bus #1 ]
>
> # cat /sys/kernel/debug/usb/usbmon/1u > /tmp/usbmon-1u.txt <--- USB-bus #01
>
> [ Do suspend plus resume ]
>
> ...
>
> [ Check /tmp/usbmon-1u.txt file ]
>
> ...
>
> File attached!
That also looks normal. Did you have CONFIG_USB_DEBUG enabled during
this test? If you did, you could try turning it back off to see if the
original problem returns while still doing a usbmon trace.
Alan Stern
next prev parent reply other threads:[~2013-04-25 15:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 20:00 linux-next: Tree for Apr 24 [ PM: Device 1-1.2 failed to resume async: error -32 ] Sedat Dilek
[not found] ` <CA+icZUXAwh=jg4f8AGV+-Moxc-kWJrjRhZ8+9pF4s41wDbba4A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-24 20:09 ` Sedat Dilek
2013-04-24 20:32 ` Alan Stern
2013-04-24 20:40 ` Sedat Dilek
2013-04-24 21:14 ` Sedat Dilek
2013-04-25 15:44 ` Alan Stern
2013-04-25 15:52 ` Sedat Dilek
2013-04-25 16:02 ` Alan Stern
2013-04-24 21:17 ` Alan Stern
2013-04-24 21:25 ` Sedat Dilek
2013-04-24 22:07 ` Sedat Dilek
2013-04-25 15:49 ` Alan Stern [this message]
2013-04-25 15:57 ` Sedat Dilek
[not found] ` <CA+icZUVUd=0oFhPt8Gneze1UyZ5vyGxoEDnBNrya0+mn99nQkA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-25 17:02 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44L0.1304251145110.948-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).