DriveWorks RenderEngine unable to render sample_camera_replay but can render different samples

christopher.tuch · February 22, 2023, 4:25pm

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other

Target Operating System
Linux
QNX
other

Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
1.9.1.10844
other

Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other

Hi NVIDIA,

I am having a strange problem with DriveWorks Cameras (virtual). On the Host Machine running Ubuntu 20.04 with the latest, tested NVIDIA driver, the render engine is not able to display any image which is coming from a camera (virtual, USB).

Other Samples such as the Lidar/Radar Replay run flawless, other GL applications also run, without problems (pygame, glxgears).

I attached a few Screenshots showing the windows frame, and the screenshot of a screenshot, taken inside the camera_replay sample.

Looking forward for any suggestions from your side, and if something is unclear, I am happy to answer anything.

Thanks in advance.

VickNV · February 22, 2023, 4:36pm

As a next step, could you please share the full command you are using to run the camera_replay sample? This will help us to better understand the issue and reproduce it on our end.

christopher.tuch · February 23, 2023, 8:55am

I execute the shipped binary, by running /usr/local/driveworks/bin/sample_hello_world

christopher.tuch · February 23, 2023, 10:00am

Now I did some more tests:

I added export __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia to my .bashrc
Made multiple runs in a row. The Problem persists (I have no Image), but something odd happened.
Here is the output of the runs:

*****@*****:~$ /usr/local/driveworks/bin/sample_camera_replay        # run 1
ProgramArguments: Missing argument 'dwTracePath' requested
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  150 (GLX)
  Minor opcode of failed request:  16 (X_GLXVendorPrivate)
  Resource id in failed request:  0x260000a
  Serial number of failed request:  0
  Current serial number in output stream:  170
*****@*****:~$ /usr/local/driveworks/bin/sample_camera_replay            # run 2
ProgramArguments: Missing argument 'dwTracePath' requested
X Error of failed request:  BadAlloc (insufficient resources for operation)
  Major opcode of failed request:  150 (GLX)
  Minor opcode of failed request:  5 (X_GLXMakeCurrent)
  Serial number of failed request:  0
  Current serial number in output stream:  157
*****@*****:~$ /usr/local/driveworks/bin/sample_camera_replay      # run 3 (Black Window) Image
ProgramArguments: Missing argument 'dwTracePath' requested
[23-02-2023 10:51:23] Platform: Detected Generic x86 Platform
[23-02-2023 10:51:23] TimeSource: monotonic epoch time offset is 1677078935075513
[23-02-2023 10:51:23] Adding variable DW_Base:DW_Version
[23-02-2023 10:51:23] Addded variable DW_Base:DW_Version
[23-02-2023 10:51:23] Platform: number of GPU devices detected 2
[23-02-2023 10:51:23] Platform: currently selected GPU device 0, Resource Data Dir: trt_08_04_12_05, Arch: gp1xx-discrete
[23-02-2023 10:51:23] Platform: currently selected GPU device discrete ID 0
[23-02-2023 10:51:23] Context::mountResourceCandidateDataPath resource FAILED to mount from './resources': VirtualFileSystem: Failed to mount './resources/resources.pak'
[23-02-2023 10:51:23] Context::mountResourceCandidateDataPath resource FAILED to mount from '/home/*****/data': VirtualFileSystem: Failed to mount '/home/*****/data/resources.pak'
[23-02-2023 10:51:23] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-5.8/bin/../data
[23-02-2023 10:51:23] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-5.8/bin/../data': VirtualFileSystem: Failed to mount '/usr/local/driveworks-5.8/bin/../data/resources.pak'
[23-02-2023 10:51:23] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-5.8/data
[23-02-2023 10:51:23] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-5.8/data': VirtualFileSystem: Failed to mount '/usr/local/driveworks-5.8/data/resources.pak'
[23-02-2023 10:51:23] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.8/bin/../lib/libdw_base.so.5.8
[23-02-2023 10:51:23] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.8/targets/x86_64-Linux/lib/libdw_base.so.5.8
[23-02-2023 10:51:23] SDK: No resources(.pak) mounted, some modules will not function properly
[23-02-2023 10:51:23] TimeSource: monotonic epoch time offset is 1677078935075513
[23-02-2023 10:51:23] Initialize DriveWorks SDK v5.8.82
[23-02-2023 10:51:23] Release build with GNU 9.3.0 from buildbrain-branch-0-g33d6f4a1440
[23-02-2023 10:51:23] Initialize DriveWorks VisualizationSDK v5.8.82
[23-02-2023 10:51:23] Initialize DriveWorksGL SDK v5.8.82
[23-02-2023 10:51:23] GL-SDK: initialize OpenGL
[23-02-2023 10:51:23] SensorFactory::createSensor() -> camera.virtual, video=/usr/local/driveworks-5.8/data/samples/sfm/triangulation/video_0.h264
[23-02-2023 10:51:23] CameraVirtual: defaulting to non SIPL
[23-02-2023 10:51:23] CameraBase: pool size set to 8
[23-02-2023 10:51:23] CameraNVCUVID: no seek table found at /usr/local/driveworks-5.8/data/samples/sfm/triangulation/video_0.h264.seek, seeking is not available.
Camera image with 1280x800 at 30.000000 FPS
Initialization complete.
Timing results:
Thread main:
-onProcess                CPU:   251us, std= 281       | GPU:   200us, std= 356       | samples=123
-onRender                 CPU:   306us, std= 633       | GPU:   304us, std= 894       | samples=300

[23-02-2023 10:51:28] Driveworks VisualizationSDK released
[23-02-2023 10:51:28] Releasing Driveworks SDK Context
[23-02-2023 10:51:28] DriveworksGL SDK released

GLX info:

glxinfo | grep OpenGL 
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 525.78.01
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6.0 NVIDIA 525.78.01
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 525.78.01
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

VickNV · February 23, 2023, 4:36pm

I noticed in your previous topic (Running precompiled Sample: "sample_camera_replay" results in Error: Error cudaErrorUnknown: unknown error) that you were able to run sample_camera_replay. Can you explain why it is not working now? Could you also share the complete log of running the application?

christopher.tuch · February 24, 2023, 9:06am

Hi @VickNV,

I don’t understand, why it is not working. It is a different machine, running 2 1080ti. The previous topic, has been fixed, by forcing GL to use the dedicated GPU on my laptop for rendering. The machine with the 1080ti’s does use the GPU for GL rendering, which can be seen above, in the output of glxinfo.

I don’t know what you mean with “full log of running application”, the following is all I get when running:

~$ /usr/local/driveworks/bin/sample_camera_replay 
ProgramArguments: Missing argument 'dwTracePath' requested
[24-02-2023 10:03:44] Platform: Detected Generic x86 Platform
[24-02-2023 10:03:44] TimeSource: monotonic epoch time offset is 1677150387078059
[24-02-2023 10:03:44] Adding variable DW_Base:DW_Version
[24-02-2023 10:03:44] Addded variable DW_Base:DW_Version
[24-02-2023 10:03:44] Platform: number of GPU devices detected 2
[24-02-2023 10:03:44] Platform: currently selected GPU device 0, Resource Data Dir: trt_08_04_12_05, Arch: gp1xx-discrete
[24-02-2023 10:03:44] Platform: currently selected GPU device discrete ID 0
[24-02-2023 10:03:44] Context::mountResourceCandidateDataPath resource FAILED to mount from './resources': VirtualFileSystem: Failed to mount './resources/resources.pak'
[24-02-2023 10:03:44] Context::mountResourceCandidateDataPath resource FAILED to mount from '/home/chrtuch/data': VirtualFileSystem: Failed to mount '/home/chrtuch/data/resources.pak'
[24-02-2023 10:03:44] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-5.8/bin/../data
[24-02-2023 10:03:44] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-5.8/bin/../data': VirtualFileSystem: Failed to mount '/usr/local/driveworks-5.8/bin/../data/resources.pak'
[24-02-2023 10:03:44] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-5.8/data
[24-02-2023 10:03:44] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-5.8/data': VirtualFileSystem: Failed to mount '/usr/local/driveworks-5.8/data/resources.pak'
[24-02-2023 10:03:44] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.8/bin/../lib/libdw_base.so.5.8
[24-02-2023 10:03:44] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.8/targets/x86_64-Linux/lib/libdw_base.so.5.8
[24-02-2023 10:03:44] SDK: No resources(.pak) mounted, some modules will not function properly
[24-02-2023 10:03:44] TimeSource: monotonic epoch time offset is 1677150387078059
[24-02-2023 10:03:44] Initialize DriveWorks SDK v5.8.82
[24-02-2023 10:03:44] Release build with GNU 9.3.0 from buildbrain-branch-0-g33d6f4a1440
[24-02-2023 10:03:45] Initialize DriveWorks VisualizationSDK v5.8.82
[24-02-2023 10:03:45] Initialize DriveWorksGL SDK v5.8.82
[24-02-2023 10:03:45] GL-SDK: initialize OpenGL
[24-02-2023 10:03:45] SensorFactory::createSensor() -> camera.virtual, video=/usr/local/driveworks-5.8/data/samples/sfm/triangulation/video_0.h264
[24-02-2023 10:03:45] CameraVirtual: defaulting to non SIPL
[24-02-2023 10:03:45] CameraBase: pool size set to 8
[24-02-2023 10:03:45] CameraNVCUVID: no seek table found at /usr/local/driveworks-5.8/data/samples/sfm/triangulation/video_0.h264.seek, seeking is not available.
Camera image with 1280x800 at 30.000000 FPS
Initialization complete.
Video reached end of stream
Timing results:
Thread main:
-onProcess                CPU:   278us, std= 359       | GPU:   212us, std= 466       | samples=1293
-onRender                 CPU:   311us, std= 321       | GPU:   303us, std= 696       | samples=3152

[24-02-2023 10:04:38] Driveworks VisualizationSDK released
[24-02-2023 10:04:38] Releasing Driveworks SDK Context
[24-02-2023 10:04:38] DriveworksGL SDK released

VickNV · February 24, 2023, 5:03pm

Are you experiencing this issue only on the machine with 1080ti GPUs? Did the devkit system work with the laptop you previously used?

Regarding the log, is this the full log of the issue? I asked for it to see if there are any clues that could help us diagnose the issue.

christopher.tuch · March 2, 2023, 3:37pm

Yes this is only with the 1080ti workstation, the laptop is still able to run the samples, but we need to run it on the workstation. I already uninstalled the SDK and nvidia drivers, reinstalled everything again with the SDK Manager, but it still does not work. Now I get the following error when launching /sample_radar_replay or different OpenGL Render samples.

$ /usr/local/driveworks/bin/sample_radar_replay 
ProgramArguments: Missing argument 'dwTracePath' requested
X Error of failed request:  BadAlloc (insufficient resources for operation)
  Major opcode of failed request:  150 (GLX)
  Minor opcode of failed request:  5 (X_GLXMakeCurrent)
  Serial number of failed request:  0
  Current serial number in output stream:  175
# end of program log

VickNV · March 2, 2023, 7:07pm

Based on your description, it does not seem like the issue is related to DRIVE OS. It appears that the applications are failing to request more memory than what is available on the system, or the X server is experiencing other resource constraints. To address this issue, you can try closing any unnecessary applications to free up system resources or increasing the amount of available memory on your system.

system · March 31, 2023, 9:09am

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