From: Aurelien Jarno <aurelien@aurel32.net>
To: Max Krasnyansky <maxk@kernel.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [5050] uhci: rewrite UHCI emulator, fully async operation with multiple outstanding transactions ( Max Krasnyansky)
Date: Fri, 22 Aug 2008 03:46:50 +0200 [thread overview]
Message-ID: <20080822014650.GB2569@volta.aurel32.net> (raw)
In-Reply-To: <48AE07C9.20200@kernel.org>
On Thu, Aug 21, 2008 at 05:26:49PM -0700, Max Krasnyansky wrote:
> Anthony Liguori wrote:
>> Aurelien Jarno wrote:
>>> On Thu, Aug 21, 2008 at 07:30:32PM +0000, Anthony Liguori wrote:
>>>
>>>> Revision: 5050
>>>> http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=5050
>>>> Author: aliguori
>>>> Date: 2008-08-21 19:30:31 +0000 (Thu, 21 Aug 2008)
>>>>
>>>> Log Message:
>>>> -----------
>>>> uhci: rewrite UHCI emulator, fully async operation with multiple
>>>> outstanding transactions (Max Krasnyansky)
>>>>
>>>
>>> Please note that this commit has broken the -usbdevice option (at least
>>> disk, tablet and mouse) for a GNU/Linux guest running a 2.6.18 kernel.
>>>
>> Well, reverting is going to be painful since this is the 4th patch in a
>> series of 8, so I'll try to fix this tonight, otherwise, I'll revert.
>
> I've done all my testing so far with XP as a guest, and the -usbdevice
> tablet is working just fine. In fact nothing should have changed in that
> area since builtin devices are synchronous.
>
> I'll setup Linux guest right now and check things out.
>
> Aurelien, can you provide a bit more details on your setup. Do use KQEMU
> or KVM ? Since you mentioned table & mouse I'm assuming that you're
> using a graphic console. Is it VNC or SDL ?. In fact why don't you just
> send me your qemu command like. So that I can replicated the problem
> better.
>
I am using QEMU, from the SVN, without KQEMU. The problem does not
depend of the console used (SDL, VNC or curses). The guest kernel
outputs the following errors:
usb 1-2: device not accepting address 2, error -71
usb 1-2: new full speed USB device using uhci_hcd and address 3
usb 1-2: device not accepting address 3, error -71
usb 1-2: new full speed USB device using uhci_hcd and address 4
usb 1-2: device not accepting address 4, error -71
usb 1-2: new full speed USB device using uhci_hcd and address 5
usb 1-2: device not accepting address 5, error -71
You can download the image from:
http://people.debian.org/~aurel32/qemu/amd64/
It is reproducible with the following command line:
qemu-system-x86_64 -hda debian_etch_amd64_small.qcow -usbdevice tablet
The error can also be reproduced with -usbdevice mouse or -usbdevice
disk:image.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
next prev parent reply other threads:[~2008-08-22 1:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 19:30 [Qemu-devel] [5050] uhci: rewrite UHCI emulator, fully async operation with multiple outstanding transactions ( Max Krasnyansky) Anthony Liguori
2008-08-21 22:32 ` Aurelien Jarno
2008-08-21 22:38 ` Anthony Liguori
2008-08-21 22:43 ` Aurelien Jarno
2008-08-21 22:41 ` Anthony Liguori
2008-08-22 0:26 ` Max Krasnyansky
2008-08-22 1:46 ` Aurelien Jarno [this message]
2008-08-22 3:34 ` Max Krasnyansky
2008-08-22 6:07 ` Max Krasnyansky
2008-08-22 8:59 ` Aurelien Jarno
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=20080822014650.GB2569@volta.aurel32.net \
--to=aurelien@aurel32.net \
--cc=maxk@kernel.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).