[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUVUd=0oFhPt8Gneze1UyZ5vyGxoEDnBNrya0+mn99nQkA@mail.gmail.com>
Date: Thu, 25 Apr 2013 17:57:07 +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 Thu, Apr 25, 2013 at 5:49 PM, Alan Stern <stern@...land.harvard.edu> 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
>
--
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/
Powered by blists - more mailing lists