qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Martin Cerveny <M.Cerveny@computer.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] usb3 - xhci - Assertion `intr->er_full' failed
Date: Thu, 02 Feb 2017 08:11:50 +0100	[thread overview]
Message-ID: <1486019510.20628.10.camel@redhat.com> (raw)
In-Reply-To: <alpine.GSO.2.00.1702012023540.5038@dmz.c-home.cz>

  Hi,
> - usb with usbredir 0.7.1

What kind of device do you assign to the guest?

> - guest windows 7 - renesas driver 2.1.36 or 2.1.39

ok.

> Where is the verfied windows driver that is compatible/tested with xhci code ?

Usually I test with the drivers shipped by the operating system, i.e.
linux kernel or windows 8 (or newer).

> I see some movement on xhci sources (https://www.kraxel.org/cgit/qemu/log/?h=work/qemu-xhci) - 
> Is there some special driver for "PCI_DEVICE_ID_REDHAT_XHCI" "1b36:000c PCI xhci usb host adapter" for Windows Guests
> that is compatible with xhci qemu code ?

Generic xhci drivers should work with any xhci controller, no matter
what pci ids it has.

> ---------------------------------- USB keyboard + qemu-xen-4.8.0 + 2.1.39 driver + DEBUG_XHCI + DEBUG_DATA ---------------------------

Is the usb keyboard enough to trigger this?

enabling usb_xhci_* trace events would be more helpful than DEBUG_XHCI
(see qemu.git/docs/tracing.txt).

cheers,
  Gerd

  reply	other threads:[~2017-02-02  7:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 20:16 [Qemu-devel] usb3 - xhci - Assertion `intr->er_full' failed Martin Cerveny
2017-02-02  7:11 ` Gerd Hoffmann [this message]
2017-02-02 12:48   ` Martin Cerveny

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=1486019510.20628.10.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=M.Cerveny@computer.org \
    --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).