On Mon, 7 May 2012, Christian Melki wrote: > Alan, > > It was a real hardware error. > Turned out it was a bad data bus or memory latch causing bits 16-24 in a word to become corrupted. > This _only_ happened when the data was 0xFFFFFFFF and it was very intermittent. This was why I saw a bad offset. > The -1 was corrupted to a bad urb_index offset. > Don't know why the USB audio code saw that more often than any other code though. > Mental note to self: Port a useful memory tester into RedBoot. :) Congratulations on tracking it down. And I'm glad there's no need to fix the driver. :-) 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
