From: Erik Rull <erik.rull@rdsoftware.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] USB continuous reset / unplug cleanup not done properly
Date: Mon, 19 Dec 2011 18:31:24 +0100 [thread overview]
Message-ID: <4EEF74EC.7090800@rdsoftware.de> (raw)
In-Reply-To: <4EEEFD20.9000506@redhat.com>
Hi Gerd,
Gerd Hoffmann wrote:
> Hi,
>
>> 1) Devices get resetted again and again on the host side and do not work
>> properly on the guest side - they work fine on the host side outside qemu.
>
> I see those too. Not clear what is going on here. usbfs requests seem
> to get stuck now and then for not-yet known reasons. Sometimes they
> finish after a few seconds. Sometimes they get stuck long enougth that
> some timeout within the guest fires and the guest resets the device.
Is it possible to increase either the timeout periods or "block" the USB
device during it is in use by the guest, so that usbfs does not want to
reset it?
> I see those with a F16 guest which polls the usb stick with
> test-unit-ready requests. Letting it run idle produces a ...
>
> usb 1-6: reset high speed USB device number 3 using ehci_hcd
>
> ... log line line in the guest now and then. Tried to write a small
> reproducer (tool constantly sending test-unit-ready via usbfs), but that
> one works just fine without any hangs.
Is it possible to trace the USB requests at this level? Maybe there is a
possibility to figure out why the reset happens.
> cheers,
> Gerd
>
Any idea about the second point regarding the remaining devices in the info
usb list?
Best regards,
Erik
prev parent reply other threads:[~2011-12-19 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 14:29 [Qemu-devel] USB continuous reset / unplug cleanup not done properly erik.rull
2011-12-19 9:00 ` Gerd Hoffmann
2011-12-19 17:31 ` Erik Rull [this message]
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=4EEF74EC.7090800@rdsoftware.de \
--to=erik.rull@rdsoftware.de \
--cc=kraxel@redhat.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.