Dear all a couple of years ago I wrote a driver for a serial dongle. I did not add it to the linux source because the dongle requires a firmware to be downloaded to the device (ezusb). The manufacturer, IO-DATA, did not want me to use their firmware. I am now in the process to move the driver from kernel version 3.0.x to kernel version 3.13.0 (ubuntu 14.02 runs with it). Once this works, I will migrate it once more to a kernel on the main line (hoping that there are not to many changes in the framework between 3.13.0 and 4.5). a) I can compile the driver, and insert it. It downloads the firmware to the serial dongle. The device reenumerates then, but the driver fails to attach to the device. It hangs while allocating the memory for the urbs of the write pool usb messages. It then behaves like a time bomb: The load slowly increase, and eventually, the system stops and I need to reboot the system. Any thoughts on how to trace down the root cause and fix it ? Here the sys log indicating this: usb 3-3: usbrsa_attach [ 5017.515778] usb-serial (null):allocate_write_urbs() [ 5039.595625] ------------[ cut here [ 5039.595642] WARNING: CPU: 4 PID: 71 at /build/linux-faWYrf/linux-3.13.0/kernel/watchdog.c:245 watchdog_overflow_callback+0x9c/0xd0() [ 5039.595644] Watchdog detected hard LOCKUP on cpu 4 And here the part of the log after the enumeration sequence: [ 492.820632] usb 3-3: Product: USB-RS232C CONVERTER [ 492.820638] usb 3-3: Manufacturer: I-O DATA DEVICE,Inc. [ 492.820642] usb 3-3: SerialNumber: USB-RSA Rev.1 [ 492.821209] usbrsa 3-3:1.0: IO-DATA - USB-RSA converter detected [ 492.821225] usbrsa_attach start [ 492.821230] usb 3-3: usbrsa_attach b) The driver requires the modules ezusb, and usb-serial. The usb serial driver framework does not offer to use the module_init function any longer. What would be the appropriate place the corresponding request_module commands? Many thanks Tilman -- 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
