tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE

Autonomous Machines Jetson & Embedded Systems Jetson TX2
1

What does this message mean, what is the cause, and how can I resolve it?

The symptoms when I see a message like this is that the screen will only “flicker on” with something actually displayed every few “ticks” of mouse movement, and won’t stay on. I’ve seen it in the past on HDMI, and now I’m getting it on DSI, when I’ve previously had success with the display staying on. It sometimes happens from startup (at least on HDMI) - whereas I think this time I booted and it was working at first, either that or it worked on the previous boot of the same image. Every time I move the mouse, a pile more of these messages pour out into dmesg and the serial console.

Fuller log:

[51062.481899] tegradc 15200000.nvdisplay: unblank
[51062.485308] tegradc 15200000.nvdisplay: *** In dsi_b_1440x1600_35_enable
[51062.693097] tegradc 15200000.nvdisplay: *** Done with dsi_b_1440x1600_35_enable
[51062.698661] tegradc 15200000.nvdisplay: *** dsi: sending dsi_init_cmd
[51062.698668] tegradc 15200000.nvdisplay: *** tegra_dsi_send_panel_cmd n_cmd=37
[51064.293998] tegradc 15200000.nvdisplay: Panel b,1440x1600-35-duallink (panel-b-1440x1600-35-duallink): *** dsi_b_1440x1600_35_postpoweron
[51064.294207] tegradc 15200000.nvdisplay: *** tegra_dsi_send_panel_cmd n_cmd=37
[51065.959271] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51065.996847] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51066.028826] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51066.059952] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51066.113968] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51066.196771] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51066.932393] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51066.971948] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.011973] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.054160] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.089910] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.119294] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.147370] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.218398] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.253901] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.293867] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.345950] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.379348] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.411115] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.445763] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.505609] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.539023] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.569447] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.606482] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.656808] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.708588] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.758326] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.793841] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.824020] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.853744] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.884325] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.910599] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.940856] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51067.972416] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51068.001532] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51068.031329] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51068.064803] tegradc 15200000.nvdisplay: Couldn't find corresponding PROPOSE
[51077.133449] tegradc 15200000.nvdisplay: blank - powerdown
[51077.150869] tegradc 15200000.nvdisplay: Panel b,1440x1600-35-duallink (panel-b-1440x1600-35-duallink): *** dsi_b_1440x1600_35_prepoweroff
[51077.150882] tegradc 15200000.nvdisplay: *** tegra_dsi_send_panel_cmd n_cmd=4
[51077.532578] tegradc 15200000.nvdisplay: Panel b,1440x1600-35-duallink (panel-b-1440x1600-35-duallink): *** In dsi_b_1440x1600_35_disable
[51077.599878] tegradc 15200000.nvdisplay: Panel b,1440x1600-35-duallink (panel-b-1440x1600-35-duallink): *** Done with dsi_b_1440x1600_35_disable

(Mods: Please don’t move this post. These are all Linux kernel messages from the public source code.)

2

rpavlik-sensics,

Which BSP are you using? rel-28.1 or rel-28.2?

3

Any update?

4

I believe I’m forked from the 28.2 release candidate roughly.

I found out that this no longer happens when I stop sending data to the tegra on UART2 (/dev/ttyTHS2) - I had something transmitting “test” to that a few times a second, and no application on the Tegra opening and reading that UART.

Why would sending data to the UART affect display stability?

5

We indeed had case that affected by UART…

https://devtalk.nvidia.com/default/topic/1027467

In fact, both yours and this thread are errors originated from same library.

Here is related topic about the EMC strap pin affecting memory bandwidth and may be the real cause of your issue.

https://devtalk.nvidia.com/default/topic/1009011/jetson-tx2/kernel-4-4-drivers-platform-tegra-mc-isomgr-c-isomgr_init-fails-to-initialize/1