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 13:02:20 -0400 (EDT) Message-ID: References: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: In-Reply-To: Sender: linux-usb-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Sedat Dilek Cc: Stephen Rothwell , linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Linux PM List , "Rafael J. Wysocki" , linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-next.vger.kernel.org On Thu, 25 Apr 2013, Sedat Dilek wrote: > > 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. > > > > As my system works as "expected" after suspend-resume and as you > pointed out "this is harmless" I am not really willing to do more > "homework". > > The ipc-sem-next issue has stolen quite bit of my time. > > Thanks for the usbmon hint, now I know for next USB issues what to do. > And I have never tried my USB-XHCI interface :-). > > /me is just an encouraged Linux-kernel hobbyist. Okay. Don't lose hope; lots of people face unexpected issues like this. Good luck! Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html