On Wed, Apr 17, 2013 at 02:46:23PM +0200, Karsten Malcher wrote: > Am 17.04.2013 13:31, schrieb Johan Hovold: > > The logs there appear not to have debugging enabled in usb-serial core. > > Please post the logs with debugging enabled in both modules to this > > thread as well. > > O.K. Nobody has requested this so far. > So this time with both modules in debug-mode: > > root@PC:# lsmod | grep usb > usb_storage 43870 0 > usbserial 32061 1 pl2303 > usbhid 36379 0 > hid 81288 1 usbhid > usbcore 128498 8 ehci_hcd,ohci_hcd,usbhid,usbserial,uas,usb_storage,pl2303 > usb_common 12354 1 usbcore > scsi_mod 162372 6 libata,sd_mod,sr_mod,sg,uas,usb_storage > > root@PC:# rmmod pl2303 > root@PC:# rmmod usbserial > root@PC:# modprobe usbserial debug=1 > root@PC:# modprobe pl2303 debug=1 > > * Then i connected the adapter. > * Connect with cutecom and a wired loop with 9600 baud. > * Write "Test" > * Close connection > * Remove adapter > > Logs attached. The logs look incomplete. It's probably because they're flooded with serial_write_room and chars_in_buffer messages. Can you try to reproduce this on a later kernel (e.g. 3.8) which uses dynamic debugging? Can you minimise your test setup using a custom program which only opens the device, initialises it, writes the four characters (e.g. "test") and reads them back (over you hardwired loop) before closing the device again? Make sure to verify it using a working device first. Thanks, Johan -- 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
