On Tue, Jul 18, 2017 at 3:14 PM, Saurin <saurin2@xxxxxxxxx> wrote: > Hi, following two different crash i am getting in 4.1.15 kernel. Is > there any patch available till latest kernel that i can apply to > address this issue? What serial driver? What are you doing with the tty when this happens? Can you try a newer kernel? > > Call Trace: > [<ffffffff8134a775>] __uart_start.isra.9+0x15/0x40 > [<ffffffff8134a7da>] uart_start+0x3a/0x60 > [<ffffffff81331086>] n_tty_receive_buf_common+0x4c6/0xaf0 > [<ffffffff81334365>] flush_to_ldisc+0xf5/0x1b0 > [<ffffffff8108414d>] try_to_wake_up+0x1cd/0x2d0 > [<ffffffff81075049>] process_one_work+0x139/0x350 > [<ffffffff810ac81c>] try_to_del_timer_sync+0x4c/0x80 > [<ffffffff8107536b>] worker_thread+0x10b/0x460 > [<ffffffff81075260>] worker_thread+0x0/0x460 > [<ffffffff8107a888>] kthread+0xc8/0xe0 > [<ffffffff8107a7c0>] kthread+0x0/0xe0 > [<ffffffff816d5762>] ret_from_fork+0x42/0x70 > [<ffffffff8107a7c0>] kthread+0x0/0xe0 > comm: kwork > > Call Trace: > [<ffffffff813488ba>] uart_put_char+0x8a/0xb0 > [<ffffffff81348870>] uart_put_char+0x40/0xb0 > [<ffffffff81328f1c>] tty_put_char+0x1c/0x40 > [<ffffffff8132da50>] do_output_char+0xa0/0x1f0 > [<ffffffff8132dcee>] __process_echoes+0x14e/0x290 > [<ffffffff81331068>] n_tty_receive_buf_common+0x4a8/0xaf0 > [<ffffffff81334365>] flush_to_ldisc+0xf5/0x1b0 > [<ffffffff81075049>] process_one_work+0x139/0x350 > [<ffffffff8100d784>] __switch_to+0x224/0x600 > [<ffffffff8107536b>] worker_thread+0x10b/0x460 > [<ffffffff816d13f8>] __schedule+0x2d8/0x8e0 > [<ffffffff81075260>] worker_thread+0x0/0x460 > [<ffffffff8107a888>] kthread+0xc8/0xe0 > [<ffffffff8107a7c0>] kthread+0x0/0xe0 > [<ffffffff816d5762>] ret_from_fork+0x42/0x70 > [<ffffffff8107a7c0>] kthread+0x0/0xe0 > comm: kwork > -- > 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 -- 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
