Re: anyone using pvusb?

[Noboru Iwamatsu <n_iwamatsu@jp.fujitsu.com>]

Hi James,

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

Could you explain more details about the issue?

- changeset of xen/kernel, arch (x86 or x64)
- H/W (CPU, M/B, USB Host controller, ...)
- USB device (Device name and VendorId/ProdId)
- your setting (show me xenstore entries)

>> 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.

Failure of the SCSI-device scanning did not occur with the storage
devices that I've tested.

But, this error might happen due to the mismatch of the
urb->transfer_flags.
I've seen this in the very early version of pvusb.

Regards,
Noboru


Keir Fraser wrote:
> Cc'ing the PVUSB author.
> 
>  -- Keir
> 
> On 03/09/2009 11:42, "James Harper" <james.harper@bendigoit.com.au> wrote:
> 
>> 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@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel