From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sedat Dilek Subject: Re: linux-next: Tree for Apr 24 [ PM: Device 1-1.2 failed to resume async: error -32 ] Date: Thu, 25 Apr 2013 17:57:07 +0200 Message-ID: References: Reply-To: sedat.dilek@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Alan Stern Cc: Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Linux PM List , "Rafael J. Wysocki" , linux-usb@vger.kernel.org List-Id: linux-next.vger.kernel.org On Thu, Apr 25, 2013 at 5:49 PM, Alan Stern wrote: > 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. > 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. - Sedat - > Alan Stern >