Re: Debugging bus resets

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

 



On 05/13/2009 12:21 PM, Brad Schick wrote:
> If I look at the usbmon output, however, there seem to be more control
> transfers that aren't in the usbfs_snoop log. Is there a reliable way to
> correlate the two logs?
>
>   
I'll answer myself... I'd assume this is because usbmon shows all usb
activity and not just that from user space usbfs calls. It would still
be nice to have a good way to correlate the logs beyond manually
matching up requests and responses.

Looking at the logs with that in mind, what it looks like to me is:
    - kernel starts an enumeration process
    - vmware claims the interface and resets it
    - vmware starts its own enumeration calls
    - vmware resets the interface again
    - vmware continue enumeration calls

Its also look like the kernel may be doing its own enumeration again
after each reset. To be expected?

Assuming this analysis is accurate, I guess that answers my question. I
wonder what vmware would say about all this.

-Brad
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux