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]
Date:	Wed, 24 Apr 2013 23:14:19 +0200
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	Alan Stern <stern@...land.harvard.edu>
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, Apr 24, 2013 at 10:40 PM, Sedat Dilek <sedat.dilek@...il.com> wrote:
> On Wed, Apr 24, 2013 at 10:32 PM, Alan Stern <stern@...land.harvard.edu> wrote:
>> On Wed, 24 Apr 2013, Sedat Dilek wrote:
>>
>>> > [ CC linux-pm and linux-usb (ehci) folks ]
>>> >
>>> > This happens with my external USB mouse after suspend/resume.
>>> >
>>> > Excerpt (full dmesg and kernel-config attached):
>>> >
>>> > $ dmesg | egrep -i 'usb|async' | grep 1-1.2
>>> > [    1.258602] usb 1-1.2: new low-speed USB device number 3 using ehci-pci
>>> > [    1.368649] usb 1-1.2: New USB device found, idVendor=046d, idProduct=c00e
>>> > [    1.368661] usb 1-1.2: New USB device strings: Mfr=1, Product=2,
>>> > SerialNumber=0
>>> > [    1.368668] usb 1-1.2: Product: USB-PS/2 Optical Mouse
>>> > [    1.368672] usb 1-1.2: Manufacturer: Logitech
>>> > [    1.957999] input: Logitech USB-PS/2 Optical Mouse as
>>> > /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input4
>>> > [   62.353997] usb 1-1.2: reset low-speed USB device number 3 using ehci-pci
>>> > [   62.636893] PM: Device 1-1.2 failed to resume async: error -32
>>> > [   64.243543] usb 1-1.2: USB disconnect, device number 3
>>> > [   64.380328] usb 1-1.2: new low-speed USB device number 5 using ehci-pci
>>> > [   64.477612] usb 1-1.2: New USB device found, idVendor=046d, idProduct=c00e
>>> > [   64.477618] usb 1-1.2: New USB device strings: Mfr=1, Product=2,
>>> > SerialNumber=0
>>> > [   64.477621] usb 1-1.2: Product: USB-PS/2 Optical Mouse
>>> > [   64.477623] usb 1-1.2: Manufacturer: Logitech
>>> > [   64.481934] input: Logitech USB-PS/2 Optical Mouse as
>>> > /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input11
>>> >
>>
>> 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.
>
> The last days I also use the touchpad, so the issue is new to me,
> which says not that much :-).
>
> [1] http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?h=timers/core&id=77c675ba18836802f6b73d2d773481d06ebc0f04
>
>>> Thos 3 lines IIRC are important (one line missing above):
>>>
>>> [   62.353997] usb 1-1.2: reset low-speed USB device number 3 using ehci-pci
>>> [   62.636877] dpm_run_callback(): usb_dev_resume+0x0/0x20 returns -32
>>> [   62.636893] PM: Device 1-1.2 failed to resume async: error -32
>>>
>>> - Sedat -
>>>
>>> > Any help/hints/infos welcome :-)!
>>
>> 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.
>

With CONFIG_USB_DEBUG=y I do not see a PM/async line.

Might you have a look at the logs?

Thanks!

- Sedat -

> Can you give me more hints how to do a usbmon-trace?
>
>> 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"?
>
> Thanks for the fast as lightning reply!
>
> - Sedat -
>
>> Alan Stern
>>

View attachment "dmesg_3.9.0-rc8-next20130424-3-iniza-small_after-suspend-resume.txt" of type "text/plain" (107493 bytes)

Download attachment "config-3.9.0-rc8-next20130424-3-iniza-small" of type "application/octet-stream" (112435 bytes)

Download attachment "dmesg_3.9.0-rc8-next20130424-3-iniza-small_after-s-r.diff" of type "application/octet-stream" (10554 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ