From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Stern 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) Message-ID: References: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: Received: from iolanthe.rowland.org ([192.131.102.54]:39209 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1758475Ab3DYPtw (ORCPT ); Thu, 25 Apr 2013 11:49:52 -0400 In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Sedat Dilek Cc: Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Linux PM List , "Rafael J. Wysocki" , linux-usb@vger.kernel.org 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