Latest working kernel version: never worker for me Earliest failing kernel version: Distribution: Ubuntu 8.04.1 hardy Hardware Environment: the usb-to-serial cable 0ea0:6858 Ours Technology, Inc. Software Environment: Linux 2.6.26-1-generic #1 SMP Fri Jun 13 13:24:46 UTC 2008 x86_64 GNU/Linux Problem Description: The driver for this cable doesn't work at all. When I insert the cable, I get with dmesg: [279996.214432] usb 1-1: new full speed USB device using ohci_hcd and address 4 [279996.427344] usb 1-1: configuration #1 chosen from 1 choice [279996.888068] usbcore: registered new interface driver usbserial [279996.891909] usbserial: USB Serial support registered for generic [279996.895286] usbcore: registered new interface driver usbserial_generic [279996.895291] usbserial: USB Serial Driver core [279996.915471] usbserial: USB Serial support registered for oti6858 [279996.916423] oti6858 1-1:1.0: oti6858 converter detected [279996.920178] usb 1-1: oti6858 converter now attached to ttyUSB0 [279996.923301] usbcore: registered new interface driver oti6858 lsmod lists: oti6858 23428 0 usbserial 44144 1 oti6858 When I try to use the tty port provided by this cable, nothing works, and with dmesg I get a lot of messages like: [280403.640688] oti6858_read_int_callback(port = 0, status = 0) [280403.643886] oti6858_read_int_callback(port = 0, status = 0) [280403.644685] oti6858_read_int_callback(port = 0, status = 0) [280403.647887] oti6858_read_int_callback(port = 0, status = 0) [280403.648686] oti6858_read_int_callback(port = 0, status = 0) [280403.651879] oti6858_read_int_callback(port = 0, status = 0) [280403.652685] oti6858_read_int_callback(port = 0, status = 0) See also https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/77825 Steps to reproduce: For me, this happens always if I try to use this cable with any application, such as kmobiletools, that uses the serial tty port.
All USB bugs should be sent to the linux-usb@vger.kernel.org mailing list, and not entered into bugzilla. Please bring this issue up there, if it is still a problem in the latest kernel release.