From: Hans de Goede <hdegoede@redhat.com>
To: Shawn Starr <shawn.starr@rogers.com>
Cc: qemu-devel@nongnu.org, gerd@kraxel.org
Subject: Re: [Qemu-devel] EHCI USB regression in 1.2.0 - ehci_state_fetchqtd() asserting
Date: Fri, 21 Sep 2012 19:35:42 +0200 [thread overview]
Message-ID: <505CA56E.2060307@redhat.com> (raw)
In-Reply-To: <1516085.s32nvIE3nq@segfault.sh0n.net>
Hi,
On 09/21/2012 05:39 PM, Shawn Starr wrote:
> On Friday, September 21, 2012 02:19:08 PM Hans de Goede wrote:
>> Hi,
>
> <snip>
>>
>> Ok, so your using host redirection here, see the device usb-host
>>
>>> In addition, if i disable usb-redirection device the cam works as it did
>>> before (although like before, the video image is upside down in some
>>> applications).
>>
>> When you say disable the usb-redirection device, do you mean removing
>> the host redirection, and selecting the cam for redirection in a
>> spice client (ie remote-viewer) instead, or... ?
>>
>> Can you please try, disabling host-redirection, then connecting to
>> the vm with remote-viewer and then selecting the cam from
>> remote-viewers UI?
>>
>> Thanks,
>>
>> Hans
>
> Hi Hans,
>
> I am using usb-host and it works. If I keep usb-host and add usb-redirection
> it shows those errors.
Hmm, this sounds like you are using spice usb-redir too and the 2 are fighting
each other. Which spice-client are you using? And are you plugging in the
device after starting up the vm ?
> Your patch however did fix using host-usb alone.
Good.
> I don't have a setup that can let me use usb-redirection unfortunately.
Why not? Looking at your qemu cmdline you are using spice. Hmm, I guesss you
may want to keep the device redirected when no client is connected?
Anyway, if you could remove the host-redirection temporarily and try with
spice usb-redir and collect logs that would be great. If you don't have
time for that, that is ok too, then I'll consider this issue resolved.
Regards,
Hans
next prev parent reply other threads:[~2012-09-21 17:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 16:42 [Qemu-devel] EHCI USB regression in 1.2.0 - ehci_state_fetchqtd() asserting Shawn Starr
2012-09-19 16:53 ` Shawn Starr
2012-09-20 15:37 ` Hans de Goede
2012-09-20 19:08 ` Shawn Starr
2012-09-20 23:28 ` Shawn Starr
[not found] ` <6177450.mT8I4ey0nz@segfault.sh0n.net>
2012-09-21 0:04 ` Shawn Starr
2012-09-21 12:19 ` Hans de Goede
2012-09-21 15:39 ` Shawn Starr
2012-09-21 17:35 ` Hans de Goede [this message]
2012-09-21 18:46 ` Shawn Starr
2012-09-23 10:03 ` Hans de Goede
2012-09-23 18:00 ` Shawn Starr
2012-09-23 18:20 ` Shawn Starr
2012-09-23 18:52 ` Shawn Starr
2012-09-24 9:52 ` Hans de Goede
2012-09-24 14:24 ` Shawn Starr
2012-09-24 9:50 ` Hans de Goede
2012-09-24 14:20 ` Shawn Starr
2012-09-24 14:36 ` Hans de Goede
2012-09-24 14:38 ` Shawn Starr
2012-10-02 15:26 ` Shawn Starr
2012-10-08 11:27 ` Hans de Goede
2012-10-08 13:01 ` Johannes Stezenbach
2012-10-08 13:51 ` Hans de Goede
2012-10-08 14:49 ` Johannes Stezenbach
2012-10-08 15:03 ` Hans de Goede
2012-10-08 16:11 ` Johannes Stezenbach
2012-10-08 20:10 ` Hans de Goede
2012-10-08 20:18 ` Shawn Starr
2012-10-08 21:32 ` Hans de Goede
2012-10-08 21:37 ` Shawn Starr
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=505CA56E.2060307@redhat.com \
--to=hdegoede@redhat.com \
--cc=gerd@kraxel.org \
--cc=qemu-devel@nongnu.org \
--cc=shawn.starr@rogers.com \
/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).