linux-kernel - Re: linux-next: Tree for Apr 24 [ PM: Device 1-1.2 failed to resume async: error -32 ]

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] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.1304251301190.948-100000@iolanthe.rowland.org>
Date:	Thu, 25 Apr 2013 13:02:20 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Sedat Dilek <sedat.dilek@...il.com>
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, 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-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/