[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] anyone using pvusb?


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Thu, 3 Sep 2009 20:42:15 +1000
  • Delivery-date: Thu, 03 Sep 2009 03:47:10 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcosgzOncowto+FHS56eWduVeLc5ug==
  • Thread-topic: anyone using pvusb?

Is anyone successfully using pvusb under 3.4-testing and 2.6.18-xen?

I've been trying to figure out why my windows drivers are hanging after
the first or second BULK packet is sent, and only just occurred to me to
see if it actually works under Linux, and it doesn't.

The device I'm testing with is a flash memory stick, and basically the
first BULK packet gets sent successfully, which I assume is a read
request, and then a packet is sent to be filled with data read from the
flash device and it either hangs there, or comes back with 0 bytes and
then the next packet hangs - usb_submit_urb returns success but the
complete callback routine is never called.

Under Linux DomU (frontend), I get:

Sep  3 20:33:12 smtp2 kernel: usbcore: registered new driver usb-storage
Sep  3 20:33:12 smtp2 kernel: USB Mass Storage support registered.
Sep  3 20:33:12 smtp2 kernel: usb-storage: device found at 2
Sep  3 20:33:12 smtp2 kernel: usb-storage: waiting for device to settle
before scanning
Sep  3 20:33:23 smtp2 kernel: vusb vusb-0: Unlink after no-IRQ?
Controller is probably using the wrong IRQ.

Nothing is logged in the backend.

lsusb -v under the DomU appears to be just fine - everything is reported
correctly.

Any ideas?

Thanks

James


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.