Red screen after nvidia logo on hdmi and dispalyport

Autonomous Machines Jetson & Embedded Systems Jetson TX2
,
1

Hi,

I’m working on our carrier board for tx2i with R32.7.5
and also made some changes for enabling displayport.

diff --git a/sources/hardware/nvidia/platform/t18x/quill/kernel-dts/tegra186-quill-p3489-1000-a00-00-base.dts b/sources/hardware/nvidia/platform/t18x/quill/kernel-dts/tegra186-quill-p3489-1000-a00-00-base.dts
index 5d76217ba..5b6a7ca0c 100644
--- a/sources/hardware/nvidia/platform/t18x/quill/kernel-dts/tegra186-quill-p3489-1000-a00-00-base.dts
+++ b/sources/hardware/nvidia/platform/t18x/quill/kernel-dts/tegra186-quill-p3489-1000-a00-00-base.dts
@@ -278,9 +278,15 @@
 		};
 
 		sor {
-			status = "disabled";
+//		
+//			status = "disabled";
+			status = "okay";
+////
 			dp-display {
-				status = "disabled";
+//			
+//				status = "disabled";
+				status = "okay";
+////			
 			};
 			hdmi-display {
 				status = "disabled";
@@ -294,7 +300,10 @@
 		};
 
 		dpaux@155c0000 {
-			status = "disabled";
+//		
+//			status = "disabled";
+			status = "okay";
+////
 		};
 
 		sor1 {
@@ -311,8 +320,22 @@
 			status = "disabled";
 		};
 
+// 
+               	nvdisplay@15210000 {
+                       	status = "okay";
+                       	nvidia,fb-win = <2>;
+                       	win-mask = <0xC>;
+               	};
+////
+
+
 		nvdisplay@15220000 {
-			status = "disabled";
+//		
+//			status = "disabled";
+			status = "okay";
+                       	nvidia,fb-win = <4>;
+                       	win-mask = <0x30>;			
+////			
 		};
 	};

But it will show red screen about 2 seconds on both hdmi and displayport monitor after nvidia logo when I power on.
You can see the red screen at14~16 second in the attachment.
It only happens when I connect both monitor, if I only connect hdmi or displayport, it won’t show the red screen.


This problem won’t happen on TX2 module with the same carrier board.
Is there anything wrong with my changes for enabling display port?
Any suggestions would be greatly appreciated.

Thx
Yen

3

Did 32.7.4 reproduce this issue with same module too?

Not sure if related to 32.7.5.

4

R32.7.4 has the same problem on tx2i.

5

Tried this

6

Hi,

After adding “TegraReserveDisplayBandwidth” “false” to xorg.conf, it will always show red screen even login to the ubuntu desktop.

Thx
Yen

7

Please remove TegraReserveDisplayBandwidth false.
What are the display resolution in use on the two monitors?

8

Both of them are 4K monitors.

9

please share the full dmesg

10

And also dump these nodes on both TX2 and TX2i.

cat /sys/kernel/debug/tegradc.0/stats
cat /sys/kernel/debug/tegradc.1/stats
cat /sys/kernel/debug/tegradc.2/stats

Are you sure the device tree in use on TX2 and TX2i are same for display part?

11

Hi,

Please find the dmesg log in attachment.
TX2i:
dmesg0a.txt (86.5 KB)

tx2i_tegradc_stats
tx2i_tegradc_stats803×521 75.4 KB

TX2:

tx2_tegradc_stats
tx2_tegradc_stats692×430 54.3 KB

Thx
Yen

12

Answer this missing question.

Are you sure the device tree in use on TX2 and TX2i are same for display part?

13

Yes, same changes on dts.

14

please dump this node from both TX2 and TX2i.

cat /sys/kernel/debug/tegra_bwmgr/bwmgr_clients_info

15

Hi,
Please find them in attachments.
bwmgr_clients_info_tx2.txt (5.5 KB)
bwmgr_clients_info_tx2i.txt (5.5 KB)

16

Are you using same monitor setup on TX2 and TX2i when you dumped above info?

17

Yes, same carrier board and same monitor setup.

18

Could you share me the tegrastats result of both tx2 and tx2i? Did you run jetson_clocks on tx2i but not tx2 when dumping bwmgr info?

19

We didn’t run jetson_clocks on TX2 and TX2i.

tegrastats_tx2.txt (2.1 KB)
tegrastats_tx2i.txt (2.3 KB)

20

You may need to run sudo when you want to share tegrastats result… Otherwise it won’t print full info…

21

Please see the full info. for tegrastats .
tegrastats_tx2_sudo.txt (5.5 KB)
tegrastats_tx2i_sudo.txt (5.3 KB)