CSI camera red screen with "vid_rend: syncpoint wait timeout"

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
1

Hello, I have similar problem as this thread for TX2: https://devtalk.nvidia.com/default/topic/1037057/jetson-tx2/red-screen-with-quot-vid_rend-syncpoint-wait-timeout-quot-/post/5268424/ but the suggested option is not working (service is not even running).

The red screen shows only with resolution 3840x2160, FullHD is ok and when it occurs, I must reboot the whole devkit, stop it in terminal doesn’t work. Camera used is this https://leopardimaging.com/product/li-jetson-kit-imx274-x/, sadly I can’t try it on different monitor, current is Dell S2817Q connected directly to devkit via HDMI so there aren’t any converters.

Pipeline is

gst-launch-1.0 nvarguscamerasrc ! 'video/x-raw(memory:NVMM), width=(int)3840, height=(int)2160, format=(string)NV12, framerate=(fraction)30/1' ! autovideosink

and terminal output

Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
GST_ARGUS: Creating output stream
CONSUMER: Waiting until producer is connected...
GST_ARGUS: Available Sensor modes :

GST_ARGUS: 3840 x 2160 FR = 59.999999 fps; Analog Gain range min 1.000000, max 44.400002; Exposure Range min 44000, max 666637000;

GST_ARGUS: 1920 x 1080 FR = 59.999999 fps; Analog Gain range min 1.000000, max 177.000000; Exposure Range min 58000, max 184611000;

GST_ARGUS: 3840 x 2160 FR = 29.999999 fps; Analog Gain range min 1.000000, max 30.000000; Exposure Range min 57000, max 20480000;

GST_ARGUS: 1920 x 1080 FR = 59.999999 fps; Analog Gain range min 1.000000, max 177.000000; Exposure Range min 56000, max 666479000;

GST_ARGUS: Running with following settings:
   Camera index = 0 
   Camera mode  = 2 
   Output Stream W = 3840 H = 2160 
   seconds to Run    = 0 
   Frame Rate = 29.999999 
GST_ARGUS: Setup Complete, Starting captures for 0 seconds
GST_ARGUS: Starting repeat capture requests.
CONSUMER: Producer has connected; continuing.
vid_rend: syncpoint wait timeout
'vid_rend: syncpoint wait timeout
'vid_rend: syncpoint wait timeout
'vid_rend: syncpoint wait timeout
'vid_rend: syncpoint wait timeout
'vid_rend: syncpoint wait timeout
'vid_rend: syncpoint wait timeout
'^Chandling interrupt.
Interrupt: Stopping pipeline ...
Execution ended after 0:00:03.558175330
Setting pipeline to PAUSED ...
vid_rend: syncpoint wait timeout
'Setting pipeline to READY ...
vid_rend: syncpoint wait timeout
'vid_rend: syncpoint wait timeout
'GST_ARGUS: Cleaning up
CONSUMER: Done Success
GST_ARGUS: Done Success
Setting pipeline to NULL ...
vid_rend: syncpoint wait timeout
'Freeing pipeline ...
2

Hi voc,
Add below line in /etc/X11/xorg.conf.t194_ref file will solve problem.
Option “TegraReserveDisplayBandwidth” “false”

I am not sure this is a permanent fix or not but this solved problem.

1 Like
3

Thank you, that does seem to be working.

4

This is a known display memory bandwidth issue on TX2/AGX. Please try to use the workaround in #2 if you want to use nvoverlaysink.

5

The suggested workaround does not appear to work for the Jetson TX2 using the JetPack 4.2.

6

Hi Simon.grenier-corriveau,
I didn’t test Jetpack 4.2 for Jetson TX2 But please verify once that you have added Option “TegraReserveDisplayBandwidth” “false” in exact same xorg.conf file.
Because there is a soft link in Jetson AGX Xavier for xorg.conf.

nvidia@nvidia-desktop:~$ ls -list /etc/X11/xorg.conf
1048952 0 lrwxrwxrwx 1 root root 27 Apr 30 21:26 /etc/X11/xorg.conf → /etc/X11/xorg.conf.t194_ref

Likewise, check for Jetson TX2 and update in the proper conf file.

Thanks,
Ritesh

7

This worked for me too.

One important precision: that option goes in the

Section "Device"

block.