No, I thank you for your answer. Unfortunately, I'm just a linux newbie. I'm using an OpenWRT embedded device ... so I don't know how to do a git-bisect. The OpenWRT image is cross-compiled on a x86 machine and the kernel gets compiled through a makefile. Another person suggested this: 9:34:28 PM: I guess CD is unconnected in your controller. 9:34:35 PM: And before it wasn't taken into accound. 9:34:38 PM: Now it is. 9:34:44 PM: That looks quite like a possible clue. I don't know what other info I could provide you. Please let me know in case you need some other info. On Thu, Jun 30, 2011 at 9:28 PM, Greg KH <gregkh@xxxxxxx> wrote: > On Thu, Jun 30, 2011 at 09:09:47PM +0200, Felix Paliuc wrote: >> Could it be one of these changes made to ch341: >> >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/usb/serial/ch341.c;h=6ae1c0688b5e14cb03cb9905ea793ac6caa4f84b;hb=61c4f2c81c61f73549928dfd9f3e8f26aa36a8cf > > Yes, it could be any of those. > > Can you run 'git bisect' to try to track down the offender? > > I looked at your strace output, and didn't see anything obvious other > than it looks like the program is timing out a lot. Is it waiting for > data to be sent to it from the device? > > Is there a pointer to the userspace program anywhere that I could look > at it to see if it is setting up the line settings properly? Odds are a > flow control setting isn't being initialized that is now being paid > attention to (older versions of the driver ignored that, which caused > overflow problems and that was fixed.) > > thanks, > > greg k-h > -- 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