Hi, everyone, I’m currently encountering this recurring error when running an nvarguscamerasrc GStreamer pipeline on a custom Jetson-based system running JP514:
nvbuf_utils: dmabuf_fd -1 mapped entry NOT found
Error generated. gstnvarguscamerasrc.cpp, threadExecute:723 NvBufSurfaceFromFd Failed.
The pipeline:
gst-launch-1.0 nvarguscamerasrc sensor-id=0 num-buffers=1 ! "video/x-raw(memory:NVMM), format=(string)NV12, width=(int)...., height=(int)...., framerate=18/1" ! nvvidconv ! nvjpegenc ! filesink location=image.jpg
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: .... x .... FR = 18.000000 fps Duration = 55555556 ; Analog Gain range min 0.000000, max 45.000000; Exposure Range min ......, max ........;
GST_ARGUS: Running with following settings:
Camera index = 0
Camera mode = 0
Output Stream W = .... H = ....
seconds to Run = 0
Frame Rate = 18.000000
GST_ARGUS: Setup Complete, Starting captures for 0 seconds
GST_ARGUS: Starting repeat capture requests.
CONSUMER: Producer has connected; continuing.
nvbuf_utils: dmabuf_fd -1 mapped entry NOT found
Error generated. gstnvarguscamerasrc.cpp, threadExecute:723 NvBufSurfaceFromFd Failed.
Error generated. gstnvarguscamerasrc.cpp, threadFunction:242 (propagating)
Redistribute latency...
Got EOS from element "pipeline0".
Execution ended after 0:00:04.003437912
Setting pipeline to NULL ...
GST_ARGUS: Cleaning up
GST_ARGUS: Done Success
Freeing pipeline ...
nvargus-daemon log:
systemctl status nvargus-daemon.service -l
● nvargus-daemon.service - NVIDIA Argus daemon
Loaded: loaded (/lib/systemd/system/nvargus-daemon.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2025-04-16 18:11:47 UTC; 2h 44min ago
Main PID: 638 (nvargus-daemon)
Tasks: 1 (limit: 36067)
Memory: 151.0M
CGroup: /system.slice/nvargus-daemon.service
└─ 638 /usr/sbin/nvargus-daemon
nvargus-daemon[638]: SCF: Error Timeout: Sending critical error event for Session 1
nvargus-daemon[638]: (in src/api/Session.cpp, function sendErrorEvent(), line 1039)
nvargus-daemon[638]: PowerServiceCore:handleRequests: timePassed = 4502
nvargus-daemon[638]: SCF: Error InvalidState: Sensor GUID 1 is in error state. Skipping requests, capture sequence ID = 3 continue draining session frameStart events 1
nvargus-daemon[638]: (in src/services/capture/FusaCaptureViCsiHw.cpp, function waitCsiFrameStart(), line 545)
nvargus-daemon[638]: SCF: Error InvalidState: Sensor 1 already in same state
nvargus-daemon[638]: (in src/services/capture/CaptureServiceDeviceSensor.cpp, function setErrorState(), line 100)
nvargus-daemon[638]: SCF: Error InvalidState: Timeout!! Skipping requests on sensor GUID 1, capture sequence ID = 3 draining session frameEnd events 1
nvargus-daemon[638]: (in src/services/capture/FusaCaptureViCsiHw.cpp, function waitCsiFrameEnd(), line 648)
nvargus-daemon[638]: PowerServiceCore:handleRequests: timePassed = 6229
dmesg output right after the error:
mc-err: (255) csw_vifalw: EMEM address decode error
status = 0x200100bd; hi_addr_reg = 0x0000007f addr = 0x7ffc340000
secure: no, access-type: write
...
mc-err: Too many MC errors; throttling prints
Notes:
- We do not get this error on:
- Another system running JP512
- A newer setup using JP6
- Same camera sensor setup is used.
Does anyone have insights into what might be causing this issue?
Any insight on the meaning of the dmabuf_fd -1 issue in this context, or how it could relate to mc-err: EMEM address decode error?
Any suggestions would be greatly appreciated!