My nvargus program runs for a while and then experiences an nvargus core dump followed by a nvargus service restart. What troubleshooting steps could I take? What potential impact might this have?
journalctl log :
nvargus-daemon-log.txt (247.4 KB)
Hi 1143590135,
In the log, nvargus-daemon crashes 5 times with:
5 buffers still pending during EGLStreamProducer destruction
Mutex not initialized
Main process exited, code=dumped, status=11/SEGV
Before each crash, the same suspicious patterns appear:
V4L2Device not available
Invalid isp config attribute
capture set config ioctl failed
Recommended troubleshooting steps:
# 1. Collect platform/version info
cat /etc/nv_tegra_release
uname -a
dpkg -l | grep nvidia-l4t
# 2. Confirm camera nodes and modes
v4l2-ctl --list-devices
ls -l /dev/video*
v4l2-ctl -d /dev/video0 --list-formats-ext
# 3. Test raw V4L2 first
v4l2-ctl -d /dev/video0 --stream-mmap --stream-count=300
# 4. Test Argus with the simplest pipeline
sudo systemctl restart nvargus-daemon
gst-launch-1.0 -e nvarguscamerasrc sensor-id=0 ! \
'video/x-raw(memory:NVMM),width=1920,height=1080,framerate=30/1' ! \
fakesink
If V4L2 fails, debug the sensor driver/device tree first. If V4L2 passes but Argus crashes, focus on Argus/ISP configuration.
This was a resource release issue; I resolved it after adjusting the resource release logic.
I encountered another problem: my nvargus seems to stop retrieving data after a while. Initially, I suspected it was unable to retrieve raw data, so I closed nvargus and then used v4l2 to retrieve the data stream, which output normally. Therefore, it seems to be an issue with argus. The nvargus log when the problem occurred is as follows:
5月 29 15:58:44 galbot-echo systemd[1]: Started Argus daemon.
5月 29 16:00:56 galbot-echo nvargus-daemon[1337]: E/ libnvphs:socket: Error[2]: socket connection /var/lib/nvphs/nvphsd.ctl to PHS failed: No such file or directory
5月 29 16:00:56 galbot-echo nvargus-daemon[1337]: D/ libnvphs:socket: Warning: connecting to Power Hinting Service failed. Is PHS running?
5月 29 16:00:56 galbot-echo nvargus-daemon[1337]: E/ libnvphs:socket: Error[2]: socket connection /var/lib/nvphs/nvphsd.ctl to PHS failed: No such file or directory
5月 29 16:00:56 galbot-echo nvargus-daemon[1337]: D/ libnvphs:socket: Warning: connecting to Power Hinting Service failed. Is PHS running?
5月 29 16:00:56 galbot-echo nvargus-daemon[1337]: E/ libnvphs: Error: NvPHSSendThroughputHints[usecase=camera, hint=MinCPU, value=4294967295, timeout_ms=1000]: queue_or_send() failed
5月 29 16:01:46 galbot-echo nvargus-daemon[1337]: Module_id 30 Severity 2 : (fusa) Error: InvalidState Status syncpoint signaled but status value not updated in:/capture/src/fusaIspHandler.cpp 848
5月 29 16:01:46 galbot-echo nvargus-daemon[1337]: Module_id 30 Severity 2 : (fusa) Error: InvalidState propagating from:/capture/src/fusaIspHandler.cpp 770
5月 29 16:01:46 galbot-echo nvargus-daemon[1337]: Module_id 30 Severity 2 : (fusa) Error: ResourceAlreadyInUse All descriptors are already pending, no idle descriptors available in:/capture/src/fusaIspHandler.cpp 685
5月 29 16:01:46 galbot-echo nvargus-daemon[1337]: Module_id 30 Severity 2 : (fusa) Error: ResourceAlreadyInUse propagating from:/capture/src/fusaIspHandler.cpp 401
What’s the BSP version?
cat /etc/nv_tegra_release
5.1.4
Apply below patch to verify.
[ARGUS stability]
https://forums.developer.nvidia.com/t/nvarguscamerasrc-timeout-jetpack-5-1-4/316367/3
The above problem still occurs even though both lib files are already in use.
This library has also been updated, and the same problem occurs.
Additionally, I set export enableCamScfLogs=5 and export enableCamPclLogs=5, then collected the nvargus logs: nvargus-daemon 2>&1 | tee argus-output.log
It seems to be indicating a problem with the ISP:
argus-output.log (95.7 MB)
Please get the daemon log without enable enableCamScfLogs=5 and enableCamPclLogs
Thanks
Wouldn’t a more detailed log make troubleshooting much easier?
Here’s a simplified log example:
5月 29 15:58:44 galbot-echo systemd[1]: Started Argus daemon.
5月 29 16:00:56 galbot-echo nvargus-daemon[1337]: E/ libnvphs:socket: Error[2]: socket connection /var/lib/nvphs/nvphsd.ctl to PHS failed: No such file or directory
5月 29 16:00:56 galbot-echo nvargus-daemon[1337]: D/ libnvphs:socket: Warning: connecting to Power Hinting Service failed. Is PHS running?
5月 29 16:00:56 galbot-echo nvargus-daemon[1337]: E/ libnvphs:socket: Error[2]: socket connection /var/lib/nvphs/nvphsd.ctl to PHS failed: No such file or directory
5月 29 16:00:56 galbot-echo nvargus-daemon[1337]: D/ libnvphs:socket: Warning: connecting to Power Hinting Service failed. Is PHS running?
5月 29 16:00:56 galbot-echo nvargus-daemon[1337]: E/ libnvphs: Error: NvPHSSendThroughputHints[usecase=camera, hint=MinCPU, value=4294967295, timeout_ms=1000]: queue_or_send() failed
5月 29 16:01:46 galbot-echo nvargus-daemon[1337]: Module_id 30 Severity 2 : (fusa) Error: InvalidState Status syncpoint signaled but status value not updated in:/capture/src/fusaIspHandler.cpp 848
5月 29 16:01:46 galbot-echo nvargus-daemon[1337]: Module_id 30 Severity 2 : (fusa) Error: InvalidState propagating from:/capture/src/fusaIspHandler.cpp 770
5月 29 16:01:46 galbot-echo nvargus-daemon[1337]: Module_id 30 Severity 2 : (fusa) Error: ResourceAlreadyInUse All descriptors are already pending, no idle descriptors available in:/capture/src/fusaIspHandler.cpp 685
5月 29 16:01:46 galbot-echo nvargus-daemon[1337]: Module_id 30 Severity 2 : (fusa) Error: ResourceAlreadyInUse propagating from:/capture/src/fusaIspHandler.cpp 401
5月 29 15:58:44 galbot-echo systemd[1]: Started Argus daemon.
5月 29 16:00:56 galbot-echo nvargus-daemon[1337]: E/ libnvphs:socket: Error[2]: socket connection /var/lib/nvphs/nvphsd.ctl to PHS failed: No such file or directory
5月 29 16:00:56 galbot-echo nvargus-daemon[1337]: D/ libnvphs:socket: Warning: connecting to Power Hinting Service failed. Is PHS running?
5月 29 16:00:56 galbot-echo nvargus-daemon[1337]: E/ libnvphs:socket: Error[2]: socket connection /var/lib/nvphs/nvphsd.ctl to PHS failed: No such file or directory
5月 29 16:00:56 galbot-echo nvargus-daemon[1337]: D/ libnvphs:socket: Warning: connecting to Power Hinting Service failed. Is PHS running?
5月 29 16:00:56 galbot-echo nvargus-daemon[1337]: E/ libnvphs: Error: NvPHSSendThroughputHints[usecase=camera, hint=MinCPU, value=4294967295, timeout_ms=1000]: queue_or_send() failed
5月 29 16:01:46 galbot-echo nvargus-daemon[1337]: Module_id 30 Severity 2 : (fusa) Error: InvalidState Status syncpoint signaled but status value not updated in:/capture/src/fusaIspHandler.cpp 848
5月 29 16:01:46 galbot-echo nvargus-daemon[1337]: Module_id 30 Severity 2 : (fusa) Error: InvalidState propagating from:/capture/src/fusaIspHandler.cpp 770
5月 29 16:01:46 galbot-echo nvargus-daemon[1337]: Module_id 30 Severity 2 : (fusa) Error: ResourceAlreadyInUse All descriptors are already pending, no idle descriptors available in:/capture/src/fusaIspHandler.cpp 685
5月 29 16:01:46 galbot-echo nvargus-daemon[1337]: Module_id 30 Severity 2 : (fusa) Error: ResourceAlreadyInUse propagating from:/capture/src/fusaIspHandler.cpp 401
The error in the fusaIspHandler.cpp should be in line 812 instead of 848
It could be the lib didn’t replace or the log is older.
nvargus.log (4.0 KB)
here is the latest
It’s still line 848. I replaced this file in the /usr/lib/aarch64-linux-gnu/tegra/libnvfusacap.so directory, right?
Do you run the sample APP like argus_camera or customized APP?
Thanks
This problem is common when running a custom app and the system load is high.
Could you verify by argus_camera sample APP.
Thanks