On 01/17/2013 01:56 PM, Alan Stern wrote:
On Thu, 17 Jan 2013, Joseph Salisbury wrote:
Hello,
Please consider reverting commit
3d037774b42ed677f699b1dce7d548d55f4e4c2b in mainline as well as in the
current stable releases. It was included upstream as of v3.6-rc6. This
commit introduced a regression, described in the following bug report:
http://bugs.launchpad.net/bugs/1088733
Reverting commit 3d037774b42ed677f699b1dce7d548d55f4e4c2b in the v3.2
kernel has been confirmed to resolve the aforementioned bug.
I do not want to revert this commit without first understanding what is
going wrong. Please ask the reporter to post usbmon traces showing
what happens in both a failed and a successful recording attempt.
Alan Stern
Hi Alan,
There is a tar file[0] attached to the bug report[1]. The tar file
contains a few examples of failed and successful recording attempts
while collecting usbmon traces. There is a readme.txt file available
after extracting the files.
The bug reporter states that only the first recording after boot fails.
Subsequent recordings succeed will succeed.
Thanks again for reviewing this, Alan. Just let me know if you would
like any additional data or testing.
Thanks,
Joe
[0]
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088733/+attachment/3510887/+files/usbmon-1088733.tar.gz
[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088733
--
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
