From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:56342) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S5F4r-0004fU-5P for qemu-devel@nongnu.org; Wed, 07 Mar 2012 06:31:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S5F4S-0002wt-2Y for qemu-devel@nongnu.org; Wed, 07 Mar 2012 06:30:40 -0500 Received: from mx1.redhat.com ([209.132.183.28]:6631) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S5F4R-0002wl-QP for qemu-devel@nongnu.org; Wed, 07 Mar 2012 06:30:15 -0500 Message-ID: <4F5746C3.5040104@redhat.com> Date: Wed, 07 Mar 2012 12:30:11 +0100 From: Gerd Hoffmann MIME-Version: 1.0 References: <2025060672.17677.1331113595558.JavaMail.open-xchange@email.1und1.de> In-Reply-To: <2025060672.17677.1331113595558.JavaMail.open-xchange@email.1und1.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] New assertion failed for USB List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Erik Rull Cc: "qemu-devel@nongnu.org" On 03/07/12 10:46, Erik Rull wrote: > Hi Gerd, > > there are new assertion failed when plugging in a USB security dongle at > guest runtime. > They occur on the current GIT master + your async patch. > > /home/erik/qemu/hw/usb.c:352 usb_packet_complete: Assertion > '((&ep->queue)->tqh_first) == p' failed. > I got this only once and I'm currently not able to reproduce that. Strange. > Next one is: > Same security dongle (I tested two different hardware versions, both show > the same behaviour): > - They get detected at runtime (beside this one crash above) but it takes > quite long > - When being plugged in before guest startup I get the following assertion > - this seems to happen in BIOS before the guest OS actually boots: > /home/erik/qemu/hw/usb-uhci.c:967: uhci_fill_queue: Assertion 'ret == 2' > failed. Might be related. In both cases the packet queue somehow isn't in the state we expecting it to be. > If you need further information, just let me know how to produce it. Enable tracing for these events ... usb_packet_state_change usb_host_req_* usb_host_urb_* ... and try to reproduce. Hopefully that gives a clue. cheers, Gerd