[Resend in plain text mode...] Thanks for taking a look! I thought that there might be an bug in re-transmitting the OUT requests that are being NAK'd indefinitely, but a different flash drive works much longer and with that drive, I see many OUT requests that get NAK'd a couple of times, but eventually go through fine. So I think OUT re-transmissions are fine. That drive still fails eventually with infinite NAKs, but this one on a bulk-IN transaction. I agree, it's time to get a bus analyzer. --david On Sun, Mar 9, 2014 at 9:11 AM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > On Fri, 7 Mar 2014, David Mosberger wrote: > >> Felipe, >> >> Thanks for the tip about usbmon --- that looks interesting. Of >> course, as luck would have it, turning on usbmon changes behavior: >> dd'ing to a mass-storage device (/dev/sda1) used to fail after >> ~500KiB. With usbmon, it fails only after about 2MiB. >> >> I attached two logs: first one is the usb-storage debug output without >> usbmon (fails after about 500KB of writing to /dev/sda1), second is >> with usbmon (fails about 2MiB of writing to /dev/sda1). > > I didn't see anything unusual in the logs. It looks like you'll have > to use a bus analyzer to see the actual packets on the wire. > > Alan Stern > -- eGauge Systems LLC, http://egauge.net/, 1.877-EGAUGE1, fax 720.545.9768 -- 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
