Hi Greg, Thanks for your reply. I have modified my driver to work, the struct tty_driver has a back pointer to original tty_driver structure. Which had to be initialized to the port variable of original tty_driver structure, after tty_init_port and before tty_register_driver(my_driver), for my_drv->nr numbers, after all uart_register and basic structure initialization is successful. The back pointer I believe is added sometime after 3.0 Kernel, because of which the port initialization handling needed to be done in driver writers code, as contrary to my earlier code, where it must have been taken care by serial core. Thanks again for motivation. For any further bugs, I will keep posting. Abhijit On Wed, May 28, 2014 at 8:07 PM, Greg KH <greg@xxxxxxxxx> wrote: > On Wed, May 28, 2014 at 02:34:07PM +0530, Abhijit Lamsoge wrote: >> Hi All, >> Crash Starts here. >> >> 1498.722292] ------------[ cut here ]------------ >> [ 1498.722305] WARNING: CPU: 3 PID: 5029 at >> /build/buildd/linux-3.13.0/drivers/tty/tty_io.c:1474 >> tty_init_dev+0x1d0/0x1e0() >> [ 1498.722308] tty_init_dev: driver does not set tty->port. This will >> crash the kernel later. Fix the driver! > > Doesn't this explain the issue well enough? > -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
