Camera: WARNING: All NvMap Allocations must have a tag to identify the subsys tem allocating memory

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
1

Hi,
Here is my env: DRIVE OS 6.0.4 / Linux / p3710-10-s05, 940-63710-0010-D00 / SDKM 1.8.3.10426 / Ubuntu 20.04.5

I flashed DOS 6.0.4 successfully just now. And then bring up one of official support camera: OV2311.
Here my steps following OV2311 Using 2 Lane DPHY/CPHY :

sudo systemctl disable gdm
sudo systemctl stop gdm
cd /opt/nvidia/drive-linux/samples/nvmedia/nvsipl/test/camera/
./nvsipl_camera --platform-config "LI-O
V2311-VCSEL-GMSL2-55H_CPHY_x2" --link-enable-masks "0x0001 0x0000 0x0000 0x0000" --showfps -d 1

If has no sudo before ./nvsipl_camera, I got

nvsipl_camera: ERROR: Unable to open /dev/ptp2! (errno:13)
nvsipl_camera: ERROR: CClockIdMgr::GetClockId failed
nvsipl_camera: ERROR: Notification Handler Init failed. status: 10

If using sudo :

Could not create NVCCP shared memory nvccpmutex
[ 1807.334914] nvmap_alloc_handle: PID 2285: Main: WARNING: All NvMap Allocations must have a tag to identify the subsys
tem allocating memory.Please pass the tag to the API call NvRmMemHanldeAllocAttr() or relevant. 
MAX96712: Revision 5 detected
MAX96712 Link 0: PHY optimization was enabled
nvsipl_camera: ERROR: NvSIPLCamera Init failed
nvsipl_camera: ERROR: Master initialization failed. status: 5
nvsipl_camera: ERROR: GetSyncObj failed. status: 10
nvsipl_camera: ERROR: Compositor: UnregisterNvSciSyncObjs failed
Closing of TACP shared memory handle failed nvccpmutex

I also confirmed gdm service has stopped:

systemctl status gdm
�● gdm.service - GNOME Display Manager
     Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: en>
     Active: inactive (dead)

Jul 20 19:12:43 tegra-ubuntu systemd[1]: Starting GNOME Display Manager...
Jul 20 19:12:53 tegra-ubuntu systemd[1]: Started GNOME Display Manager.
Jul 20 19:12:54 tegra-ubuntu gdm-launch-environment][1270]: pam_unix(gdm-launch>
Jul 20 19:12:54 tegra-ubuntu gdm-launch-environment][1270]: pam_unix(gdm-launch>
Jul 20 19:12:54 tegra-ubuntu gdm3[1266]: GdmDisplay: Session never registered, >
Jul 20 19:12:54 tegra-ubuntu gdm-launch-environment][1349]: pam_unix(gdm-launch>
Jul 20 19:17:46 tegra-ubuntu systemd[1]: Stopping GNOME Display Manager...
Jul 20 19:17:47 tegra-ubuntu gdm3[1266]: Child process -1354 was already dead.
Jul 20 19:17:47 tegra-ubuntu systemd[1]: gdm.service: Succeeded.
Jul 20 19:17:47 tegra-ubuntu systemd[1]: Stopped GNOME Display Manager.

And here is my connection:
camera_ov2311

2

Dear @Keelung,
Do you have any other camera modules to test? If so, could you check and confirm.

4

@SivaRamaKrishnaNV ,
OV2311 is the only one I got from our teams. So no more camera I can test.

5

Dear @Keelung,
We also notice this issue with OV2311 module on DRIVE OS 6.0.4. The fix is available in next DRIVE OS version. Does this issue block your development?

6

Hi @SivaRamaKrishnaNV ,
It’s ok to wait for next release about one week. But I can’t wait more.
Is there any temporary fix available?
And when next release will be available?
Thanks!

7

Hi @Keelung I noticed you’re working on PDK on another topic so please discuss the fix through your support channel. Thanks.

8

Hi @VickNV , I don’t think so. This isuse is an SDK issue since what’s I referred doc is from NVIDIA DRIVE OS 6.0 Linux SDK Developer Guide : OV2311 Using 2 Lane DPHY/CPHY

UPDATE 1: Can you tell us what’s difference between SDK and PDK exactly?
UPDATE 2: Let’s back to the original post on top of this thread: NV_WORKSPACE setting issue

9

We don’t release patches for issues on the devzone release. Let me send you a private message to explain more.

Please check Overview.

It can be followed up on another topic.

10

We don’t communicate the schedule in the forum. You better contact your nvidia representative for it.
But obviously it won’t be in one week. Sorry for any inconvenince.

14

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.