You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using Jetson L47 36.3, and therefore have been using the branch 77-support-nvidia-l4t-362, and are on commit 375a4be. We are seeing some interesting behaviour, and there seems to be a bug in the driver.
Please find the technical steps below:
When the system boots up, the camera is detected and initialised. And the camera view appears and seems to work well (colors being a bit washed out) when we run the command gst-launch-1.0 nvarguscamerasrc sensor_id=0 ! 'video/x-raw(memory:NVMM),width=2464, height=2064, framerate=30/1, format=NV12' ! nvvidconv flip-method=0 ! queue ! autovideosink. The terminal shows:
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
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: 2464 x 2064 FR = 41.299998 fps Duration = 24213076 ; Analog Gain range min 0.000000, max 48.000000; Exposure Range min 1000, max 4000000;
GST_ARGUS: Running with following settings:
Camera index = 0
Camera mode = 0
Output Stream W = 2464 H = 2064
seconds to Run = 0
Frame Rate = 41.299998
GST_ARGUS: Setup Complete, Starting captures for 0 seconds
GST_ARGUS: Starting repeat capture requests.
CONSUMER: Producer has connected; continuing.
Redistribute latency...
^Chandling interrupt.
Interrupt: Stopping pipeline ...
Execution ended after 0:00:09.513306338
Setting pipeline to NULL ...
GST_ARGUS: Cleaning up
CONSUMER: Done Success
GST_ARGUS: Done Success
Freeing pipeline ...
However, if journalctl -f is run on another terminal, it seems there is an issue. The messages below are repeated continously whilst the camera is streaming:
Jun 20 12:02:40 xyzreality-orin4 nvargus-daemon[2933]: Module_id 30 Severity 2 : FuSaCaptureViErrorDecode VI Error in frame: 0
Jun 20 12:02:40 xyzreality-orin4 nvargus-daemon[2933]: Module_id 30 Severity 2 : FALCON_ERROR 0x00000e
Jun 20 12:02:40 xyzreality-orin4 nvargus-daemon[2933]: Module_id 30 Severity 5 : ChanselFault 0x040000
Jun 20 12:02:40 xyzreality-orin4 nvargus-daemon[2933]: Module_id 30 Severity 5 : Current line in frame
Jun 20 12:02:40 xyzreality-orin4 nvargus-daemon[2933]: Module_id 30 Severity 5 : [hi:lo] : 31 16
Jun 20 12:02:40 xyzreality-orin4 nvargus-daemon[2933]: Module_id 30 Severity 5 : Decoder Field Value: 4
Jun 20 12:02:40 xyzreality-orin4 nvargus-daemon[2933]: Module_id 30 Severity 5 :
Jun 20 12:02:40 xyzreality-orin4 nvargus-daemon[2933]: Module_id 30 Severity 2 : EMB_SHORT:
We then set it up to debug further using the following
And then if the camera is streamed and then stopped, the trace file seems to have no issues trace log 1.log
If we enable further logging and run nvargus through the terminal using the following
sudo su
export enableCamPclLogs=5
export enableCamScfLogs=5
/usr/sbin/nvargus-daemon
This time when the gstreamer command is run, a black screen is displayed for a few seconds, and then it closes. The terminal shows:
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
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: 2464 x 2064 FR = 41.299998 fps Duration = 24213076 ; Analog Gain range min 0.000000, max 48.000000; Exposure Range min 1000, max 4000000;
GST_ARGUS: Running with following settings:
Camera index = 0
Camera mode = 0
Output Stream W = 2464 H = 2064
seconds to Run = 0
Frame Rate = 41.299998
GST_ARGUS: Setup Complete, Starting captures for 0 seconds
GST_ARGUS: Starting repeat capture requests.
CONSUMER: Producer has connected; continuing.
(Argus) Error EndOfFile: Unexpected error in reading socket (in src/rpc/socket/client/ClientSocketManager.cpp, functionrecvThreadCore(), line 277)
(Argus) Error EndOfFile: Receive worker failure, notifying 1 waiting threads (in src/rpc/socket/client/ClientSocketManager.cpp, functionrecvThreadCore(), line 350)
(Argus) Error InvalidState: Argus client is exiting with 1 outstanding client threads (in src/rpc/socket/client/ClientSocketManager.cpp, functionrecvThreadCore(), line 366)
(Argus) Error EndOfFile: Receiving thread terminated with error (in src/rpc/socket/client/ClientSocketManager.cpp, functionrecvThreadWrapper(), line 379)
(Argus) Error EndOfFile: Client thread received an error from socket (in src/rpc/socket/client/ClientSocketManager.cpp, functionsend(), line 145)
(Argus) Error EndOfFile: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, functiondispatch(), line 91)
(Argus) Error InvalidState: Receive thread is not running cannot send. (in src/rpc/socket/client/ClientSocketManager.cpp, functionsend(), line 96)
(Argus) Error InvalidState: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, functiondispatch(), line 91)
nvbuf_utils: dmabuf_fd -1 mapped entry NOT found
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, threadExecute:732 NvBufSurfaceFromFd Failed.
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, threadFunction:243 (propagating)
Redistribute latency...
Got EOS from element "pipeline0".
Execution ended after 0:00:01.014790620
Setting pipeline to NULL ...
GST_ARGUS: Cleaning up
(Argus) Error InvalidState: Receive thread is not running cannot send. (in src/rpc/socket/client/ClientSocketManager.cpp, functionsend(), line 96)
(Argus) Error InvalidState: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, functiondispatch(), line 91)
(Argus) Error InvalidState: Receive thread is not running cannot send. (in src/rpc/socket/client/ClientSocketManager.cpp, functionsend(), line 96)
(Argus) Error InvalidState: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, functiondispatch(), line 91)
(Argus) Error InvalidState: Receive thread is not running cannot send. (in src/rpc/socket/client/ClientSocketManager.cpp, functionsend(), line 96)
(Argus) Error InvalidState: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, functiondispatch(), line 91)
Caught SIGSEGV
Segmentation fault (core dumped)
Hi,
We are using Jetson L47 36.3, and therefore have been using the branch 77-support-nvidia-l4t-362, and are on commit 375a4be. We are seeing some interesting behaviour, and there seems to be a bug in the driver.
Please find the technical steps below:
gst-launch-1.0 nvarguscamerasrc sensor_id=0 ! 'video/x-raw(memory:NVMM),width=2464, height=2064, framerate=30/1, format=NV12' ! nvvidconv flip-method=0 ! queue ! autovideosink
. The terminal shows:journalctl -f
is run on another terminal, it seems there is an issue. The messages below are repeated continously whilst the camera is streaming:And then if the camera is streamed and then stopped, the trace file seems to have no issues
trace log 1.log
If we enable further logging and run nvargus through the terminal using the following
the nvargus log is attached
nvargus log.txt
journalctl -f
still has the same messages, although only a few since the stream crashed.the trace file this time reports quite a few issues
trace log 2.log
The text was updated successfully, but these errors were encountered: