linux-kernel - Re: linux-next: Tree for Apr 24 [ PM: Device 1-1.2 failed to resume async: error -32 ]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.1304241715170.1548-100000@iolanthe.rowland.org>
Date:	Wed, 24 Apr 2013 17:17:41 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Sedat Dilek <sedat.dilek@...il.com>
cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	<linux-next@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	Linux PM List <linux-pm@...ts.linux-foundation.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>, <linux-usb@...r.kernel.org>
Subject: Re: linux-next: Tree for Apr 24 [ PM: Device 1-1.2 failed to resume
 async: error -32 ]

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.

> > 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

--
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/