Hi David
Thanks for the quick reply!
I tested your suggestions both on Linux and Windows:
Linux
r575
Debug & Validation mode:
Still the same segmentation fault in optixModuleCreate (validation mode had no effect)
Release & Validation mode:
\[ 4\]\[ COMPILER\]: Info: Pipeline statistics
module(s) : 1
entry function(s) : 3
trace call(s) : 1
continuation callable call(s) : 0
direct callable call(s) : 0
basic block(s) in entry functions : 322
instruction(s) in entry functions : 7890
non-entry function(s) : 0
basic block(s) in non-entry functions: 0
instruction(s) in non-entry functions: 0
debug information : no
\[ 2\]\[VALIDATION_ERROR\]: \[TRAVERSABLE_GRAPH_DEPTH_EXCEEDED\] traversable graph depth exceeded during traversal
launch index: \[131, 0, 0\]
additional occurrences: 36
transform list:
size: 1
traversable handle:
handle: 0xe00072dd82aeca09
traversable type: instance transform
The traversal depth of the scene graph passed to an optixTrace call exceeds the maximum traversable graph depth. The maximum traversable graph depth set using optixPipelineSetStackSize.
\[ 2\]\[ ERROR\]: Error syncing stream (CUDA error string: unspecified launch failure, CUDA error code: 719)
Error recording resource event on user stream (CUDA error string: unspecified launch failure, CUDA error code: 719)
Error recording resource event on user stream (CUDA error string: unspecified launch failure, CUDA error code: 719)
Error launching work to RTX
Error recording resource event on user stream (CUDA error string: unspecified launch failure, CUDA error code: 719)
Simulation failed: /home/rafael/code/planetaryraytracer/gpu-raytracer/src/photonTracer/raytracing_pipeline.cpp(58): optixLaunch(pipeline\_, stream, dParam, sizeof(InputParameters), &sbt\_, params.numberOfRays, 1, 1) failed with error 7053 (OPTIX_ERROR_VALIDATION_FAILURE) Error during validation mode run
I don’t have any recursive optixTrace launches so this error surprises me.
We use an iterative approach with for loop in the __raygen__rg program.
r580
I updated the driver to r580 and used Cuda Toolkit 13.0 to compile the simulation. Both had no effect.
Windows
r560
Using validation mode and CUDA_LAUNCH_BLOCKING had no impact both in Debug and Release.
However the deprecated launcher had an impact:
No env variable set:
\[ 4\]\[ COMPILER\]: Info: Pipeline statistics
module(s) : 1
entry function(s) : 3
trace call(s) : 1
continuation callable call(s) : 0
direct callable call(s) : 0
basic block(s) in entry functions : 1483
instruction(s) in entry functions : 42689
non-entry function(s) : 54
basic block(s) in non-entry functions: 211
instruction(s) in non-entry functions: 7543
debug information : yes
\[ 3\]\[ MEMORY\]: cblCmdListBufferSize insufficient, attempting allocation
\[ 3\]\[ MEMORY\]: cblCmdListBufferSize insufficient, attempting allocation
\[ 2\]\[ ERROR\]: Error syncing stream (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
Error freeing CBL command list buffer (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
Error freeing CBL command list buffer (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
Error recording resource event on user stream (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
Error recording resource event on user stream (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
Error launching work to RTX
Error recording resource event on user stream (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
With: $env:OPTIX_FORCE_DEPRECATED_LAUNCHER = “CBL1”
\[ 4\]\[ COMPILER\]: Info: Pipeline statistics
module(s) : 1
entry function(s) : 3
trace call(s) : 1
continuation callable call(s) : 0
direct callable call(s) : 0
basic block(s) in entry functions : 1483
instruction(s) in entry functions : 42689
non-entry function(s) : 54
basic block(s) in non-entry functions: 211
instruction(s) in non-entry functions: 7543
debug information : yes
\[ 2\]\[ ERROR\]: Error syncing stream (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
Error launching work to RTX
Error recording resource event on user stream (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
Does this imply that the error is not related do the CBL library?
Do you think the segfault on Linux in optixModuleCreate in Debug and the memory errors might be related?
Kind regards
Rafael