Greg, On 18 Apr 2014, at 3:43 PM, Greg KH wrote: > On Fri, Apr 18, 2014 at 03:37:53PM -0700, Larry Baker wrote: >> Greg, >> >> Any suggestions how to trace what is going on? > > Going on with what? Was there a bug report in that wall of text that I > missed? :) "It sort of works. What happens is, after about 8 or 9 hours, the RX to the TTY port times out. Sometimes it happens in only an hour, other times it takes about 14 hours." "I am suspicious, for example, that the CTS grant is getting lost." Should I report this on the linux-usb@xxxxxxxxxxxxxxx mailing list? >> I see all the tracing debug code has been removed in the latest >> ftdi_sio driver. > > That's because the kernel provides tracing functionality built-in, no > need for it to be on a driver-by-driver basis. Use it if you think it > is necessary. Can you point me to a web page or kernel doc for how to use it? > Everything else are very cheap devices, with questionable UART silicon. That's what I'm afraid I may never be able to determine -- whether the problem I have is between the driver and the chip (USB protocol), or is in the UART chip (could be USB protocol or the UART itself). This is basically a side project, and I don't have the proper tools anyway to do that kind of trouble-shooting. I will do what I can and report any findings, especially if a different USB serial driver works. Thanks, Larry Baker US Geological Survey 650-329-5608 baker@xxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
