On Mon, Feb 15, 2016 at 11:30:43PM +0000, tilman wrote: > 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. Why did they not want you to use their firmware in their device? > 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). 3.13 is a very old and obsolete kernel version, not much we even remember about 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 ? It's impossible to say without seeing the code, sorry. good luck, 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
