linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
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: Wed, 24 Apr 2013 23:25:36 +0200	[thread overview]
Message-ID: <CA+icZUVHvO-fzqwdTHNa_ijHSuxFaoZVKdS=TDH2CQXYYARdjQ@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1304241715170.1548-100000@iolanthe.rowland.org>

On Wed, Apr 24, 2013 at 11:17 PM, Alan Stern <stern@rowland.harvard.edu> wrote:
> On Wed, 24 Apr 2013, Sedat Dilek wrote:
>
>> > Did this work differently under earlier kernels?
>> >
>>
>> Unfortunately, s/r did not work for several Linux-Next releases as
>> there is missing tglx's patch pendinging in tip.git/timers/core.
>
> Have you tried testing under 3.8?  Or earlier releases?
>
>> > This indicates that the optical mouse didn't survive the suspend/resume
>> > sequence and had to be reenumerated.  Without more information, there's
>> > no way to tell specifically what went wrong during the initial reset at
>> > timestamp 62.353997.
>> >
>> > If you want to pursue this farther, you could enable CONFIG_USB_DEBUG.
>> > You could also collect a usbmon trace for bus 1 showing what happens
>> > during the suspend and resume.
>> >
>>
>> Hmm, I can try to enable CONFIG_USB_DEBUG and build a new kernel.
>>
>> Can you give me more hints how to do a usbmon-trace?
>
> See Documentation/usb/usbmon.txt.
>

Grrr, that docs do not mention which kernel-configs have to be set!

CONFIG_USB_DEBUG=y is not enough.

# modprobe -v usbmon
FATAL: Module usbmon not found.

# CONFIG_USB_MON is not set <--- Grrr!!!

Doing a -4 build...

- Sedat -

>> > On the other hand, what difference does it really make if a mouse has
>> > to be reenumerated?
>> >
>>
>> As a non-USB-expert it's hard to interprete such "bogus" lines in your logs.
>> I am curious enough to ask which is fair :-).
>> AFAICS in your eyes this is "harmless"?
>
> If the device continues to work normally after the resume and none of
> your programs are affected, then it is harmless.
>
> Alan Stern
>

  reply	other threads:[~2013-04-24 21:25 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 [this message]
2013-04-24 22:07             ` Sedat Dilek
2013-04-25 15:49               ` Alan Stern
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='CA+icZUVHvO-fzqwdTHNa_ijHSuxFaoZVKdS=TDH2CQXYYARdjQ@mail.gmail.com' \
    --to=sedat.dilek@gmail.com \
    --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=sfr@canb.auug.org.au \
    --cc=stern@rowland.harvard.edu \
    /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).