From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:34314) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SleRu-00011V-Pl for qemu-devel@nongnu.org; Mon, 02 Jul 2012 07:05:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SleRo-0002l9-SN for qemu-devel@nongnu.org; Mon, 02 Jul 2012 07:05:46 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56680) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SleRo-0002kz-KR for qemu-devel@nongnu.org; Mon, 02 Jul 2012 07:05:40 -0400 Message-ID: <4FF18080.7010305@redhat.com> Date: Mon, 02 Jul 2012 13:05:36 +0200 From: Gerd Hoffmann MIME-Version: 1.0 References: <4FE4953F.50404@siemens.com> <4FE58C97.5050606@rdsoftware.de> <4FE58F2D.1010307@web.de> <4FEB65E5.1060908@rdsoftware.de> <4FEC5D1B.6040307@siemens.com> <4FEC7060.2010304@siemens.com> In-Reply-To: <4FEC7060.2010304@siemens.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] usb_packet_complete: Assertion ... failed List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Erik Rull , qemu-devel Hi, > What I also so in the trace is that the USB core apparently stumbled as > a request that took very long too complete finally returned, and then > the assertion triggered over this request. Can I get such a trace please? usb_host_req_* and usb_host_urb_* enabled should show all interesting information. Oh, and replacing the assert which triggers with a tracepoint (or just a fprintf in case you use the stderr tracer) would be nice, so I can see how qemu continues after the assert(). A request taking a while shouldn't be a issue. Requests for a specific endpoint shouldn't be reordered though, and this seems to happen here. thanks, Gerd