From: Gerd Hoffmann <kraxel@redhat.com>
To: Erik Rull <erik.rull@rdsoftware.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] New assertion failed for USB
Date: Wed, 07 Mar 2012 12:30:11 +0100 [thread overview]
Message-ID: <4F5746C3.5040104@redhat.com> (raw)
In-Reply-To: <2025060672.17677.1331113595558.JavaMail.open-xchange@email.1und1.de>
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
next prev parent reply other threads:[~2012-03-07 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 9:46 [Qemu-devel] New assertion failed for USB Erik Rull
2012-03-07 11:30 ` Gerd Hoffmann [this message]
2012-03-07 12:06 ` Erik Rull
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F5746C3.5040104@redhat.com \
--to=kraxel@redhat.com \
--cc=erik.rull@rdsoftware.de \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).