All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Erik Rull <erik.rull@rdsoftware.de>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] usb_packet_complete: Assertion ... failed
Date: Mon, 02 Jul 2012 13:05:36 +0200	[thread overview]
Message-ID: <4FF18080.7010305@redhat.com> (raw)
In-Reply-To: <4FEC7060.2010304@siemens.com>

  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

  parent reply	other threads:[~2012-07-02 11:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 15:54 [Qemu-devel] usb_packet_complete: Assertion ... failed Jan Kiszka
2012-06-23  9:29 ` Erik Rull
2012-06-23  9:41   ` Jan Kiszka
     [not found]     ` <4FEB65E5.1060908@rdsoftware.de>
     [not found]       ` <4FEC5D1B.6040307@siemens.com>
     [not found]         ` <4FEC7060.2010304@siemens.com>
2012-07-02 11:05           ` Gerd Hoffmann [this message]
2012-07-02 14:26             ` Jan Kiszka
2012-07-02 15:47               ` Gerd Hoffmann
2012-07-02 15:59                 ` Gerd Hoffmann

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=4FF18080.7010305@redhat.com \
    --to=kraxel@redhat.com \
    --cc=erik.rull@rdsoftware.de \
    --cc=jan.kiszka@siemens.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.