Hi, Paul-Kenji! >>>>> "PCF" == Paul-Kenji Cahier Furuya writes: [...] > However if one stops the minicom/cat, and waits a bit too long before reopening > it, the device seems to lock up, giving an i/o error for any further operation, > until it is unplugged and plugged again. From what I can observe, it would seem > TI's chipset has some sort of limited buffer that fills up and then > breaks. Catching up the buffer is of course possible as long as it is still > connected. I would assume TI's chipset is guilty, but any suggestions/patches > for a workaround to keep that buffer empty/stop it from breaking/actually fixing > the issue would be welcome. > Thanks, > Paul-Kenji Cahier Furuya > (Kernel: 2.6.36) > Some debug info from cdc_acm: Didn't you skip parts of the log? Are you able to grab usb trace? [...] > trying to reopen the ttyACM0 after too much time was waited and the internal > buffer is full: > [496322.483695] drivers/usb/class/cdc-acm.c: acm_control_msg: rq: 0x22 val: 0x0 > len: 0x0 result: 0 > [496322.485283] drivers/usb/class/cdc-acm.c: acm_ctrl_irq - urb shutting down > with status: -2 Looks like the urb has been killed on the host side but I cannot see from the log why. > [496322.486934] drivers/usb/class/cdc-acm.c: Entering acm_read_bulk with status > -2 > [496322.486939] cdc_acm 2-1:1.0: Aborting, acm not ready > [496322.488874] drivers/usb/class/cdc-acm.c: Entering acm_read_bulk with status > -2 -- WBR, Yauheni Kaliuta -- 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
