On Fri, 14 Oct 2011, Paul Zimmerman wrote: > Attached are the log from the CV tester (v 0.9.13.1) and a screenshot from > the USB analyzer. The failing test sequence starts at packet #1367853. > Notice that the error message in the log does not match what actually > happened on the bus. Here is the failing test message: Issuing Get Max LUN request with incorrect Length parameter (>1) Invalid response from Get Max LUN request, expected 1 byte of data to be returned but received at least 10 bytes The analyzer screenshot shows that the device did send back only one byte of data. So this appears to be a bug in the CV program itself, not a violation of any sort. In fact, the error message indicates that the mass-storage gadgets' current behavior is correct. (But maybe the CV program prints out the wrong error message -- this would still be a bug, of course.) Does the same thing happen if you run the test using an EHCI controller instead of XHCI? Alan Stern -- 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
