Hi,
I have met the same issue with,
https://community.nxp.com/message/903516?commentID=903516#comment-903516
https://community.nxp.com/message/860225)
20180118_11:43:13][ 2.834930] 2020000.serial: ttymxc0 at MMIO 0x2020000 (irq = 25, base_baud = 5000000) is a IMX
20180118_11:43:13][ 2.835783] 21f0000.serial: ttymxc3 at MMIO 0x21f0000 (irq = 301, base_baud = 5000000) is a IMX
20180118_11:43:13][ 2.835843] register_console pre console_unlock >>>>>>>>
20180118_11:43:13][ 4.225332] register_console console_unlock() complete >>>>>>>>
20180118_11:43:13][ 4.231314] console [ttymxc3] enabled
20180118_11:43:13][ 4.235678] 21f4000.serial: ttymxc4 at MMIO 0x21f4000 (irq = 302, base_baud = 5000000) is a IMX
20180118_11:43:13][ 4.246606] [drm] Initialized drm 1.1.0 20060810
printk("%s pre console_unlock >>>>>>>>\n", __func__);
console_unlock();
printk("%s console_unlock() complete >>>>>>>>\n", __func__);
I am sure that this is BSP issue. the solution metioned in Linux Kernel - Deadlock in fb and tty doesn't make any sense.
Hi jiu
had you tried to reproduce issue on nxp reference boards with demo
images on
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
several people met the same issue so that i think it is a generic issue.
had you tried minimal linux configuration.
yes, no make any sense. You can test in your sabresd board to see if any issue?
No, I have no reference board.