Nsight-compute (ncu-ui) failure on jetpack 6.2 jetson orin nano

Developer Tools Nsight Compute
,
1

I ran into a similar problem when I upgraded from jetpack 6.0 to jetpack 6.1. The nsight compute version 2024.3.1 worked for ncu but not for ncu-ui. The solution posted on this site did not address the problem. I teach a computer architecture class and we distribute jetson orin nano’s to the students. We have discovered that while we can run ncu on the jetson, and create export a report. We can not run ncu-ui without the program crashing. I have sent crash reports to nvidia, but have not received a response. I will append the data from the crash report. Please note that reflashing the operating system is not a solution since the students have the jetson orin nano’s can can not wipe their drives to fix the problem. We need to know how to get ncu-ui working, or figure a way of reading the report file on another system. We have attempted to read the file on a windows based system, but it produced an error code (11). No other data about that failure. Here is the crash dump from the program:

Reason: SIGABRT
Address: 0x3e800140cf9

Thread 0 (crashed)
[0] libc.so.6 + 0x7f1f0
[1] libc.so.6 + 0x7f1d8
[2] libc.so.6 + 0x3a678
[3] libc.so.6 + 0x2712c
[4] libc.so.6 + 0x732fc
[5] libc.so.6 + 0x89568
[6] libc.so.6 + 0x8b2b0
[7] libc.so.6 + 0x8dc70
[8] libstdc++.so.6 + 0xb869c
[9] libstdc++.so.6 + 0xb875c
[10] libRebelPlugin.so + 0x13f5e58
[11] libRebelPlugin.so + 0x7172cc
[12] libQt6Core.so.6 + 0x351670
[13] libQt6Core.so.6 + 0x351670
[14] libQt6Core.so.6 + 0x351670
[15] libQt6Core.so.6 + 0x31fbe0
[16] libQt6Widgets.so.6 + 0x41fc74
[17] libRebelPlugin.so + 0x7e5650
[18] libQt6Widgets.so.6 + 0x446670
[19] libQt6Widgets.so.6 + 0x1dfef4
[20] libQt6Widgets.so.6 + 0x25c66c
[21] libQt6Widgets.so.6 + 0x3f5020
[22] libQt6Core.so.6 + 0x128784
[23] libQt6Widgets.so.6 + 0x19828c
[24] libQt6Widgets.so.6 + 0x199b20
[25] libQt6Core.so.6 + 0x128468
[26] libQt6Widgets.so.6 + 0x1d2e54
[27] libQt6Widgets.so.6 + 0x1edf14
[28] libQt6Widgets.so.6 + 0x1ee298
[29] libQt6Widgets.so.6 + 0x1e060c
[30] libQt6Widgets.so.6 + 0x2eeadc
[31] libQt6Widgets.so.6 + 0x1982ac
[32] libQt6Widgets.so.6 + 0x199b20
[33] libQt6Core.so.6 + 0x128468
[34] libQt6Core.so.6 + 0x1295bc
[35] libQt6Core.so.6 + 0x374ad0
[36] libglib-2.0.so.0 + 0x55a6c
[37] libglib-2.0.so.0 + 0xaaeb8
[38] libglib-2.0.so.0 + 0x52f10
[39] libQt6Core.so.6 + 0x374544
[40] libQt6Core.so.6 + 0x131650
[41] libQt6Core.so.6 + 0x128b54
[42] libAppLib.so + 0xbb680
[43] libc.so.6 + 0x274c8
[44] ncu-ui.bin + 0x6318

Thread 1
[0] libc.so.6 + 0xdbe38
[1] libc.so.6 + 0xdbe18
[2] libglib-2.0.so.0 + 0xaae54
[3] libglib-2.0.so.0 + 0x52f10
[4] libQt6Core.so.6 + 0x374544
[5] libQt6Core.so.6 + 0x131650
[6] libQt6Core.so.6 + 0x21e970
[7] libQt6DBus.so.6 + 0x30a40
[8] libQt6Core.so.6 + 0x28b674
[9] libc.so.6 + 0x7d5b4

Thread 2
[0] libc.so.6 + 0xdbe38
[1] libc.so.6 + 0xdbe18
[2] libxcb.so.1 + 0xc1ec
[3] libxcb.so.1 + 0xdbb4
[4] libQt6XcbQpa.so.6 + 0x51dfc
[5] libQt6Core.so.6 + 0x28b674
[6] libc.so.6 + 0x7d5b4

Thread 3
[0] libc.so.6 + 0x79de8
[1] libc.so.6 + 0x79dc4
[2] libc.so.6 + 0x7c8e8
[3] libTPSConnectionPlugin.so + 0xbf5b8
[4] libc.so.6 + 0x7d5b4

Thread 4
[0] libc.so.6 + 0xe607c
[1] libc.so.6 + 0xe6054
[2] libTPSConnectionPlugin.so + 0xc33d0
[3] libc.so.6 + 0x7d5b4

Thread 5
[0] libc.so.6 + 0x79de8
[1] libc.so.6 + 0x79dc4
[2] libc.so.6 + 0x7c8e8
[3] libRebelPlugin.so + 0x13bceec
[4] libRebelPlugin.so + 0x593578
[5] libc.so.6 + 0x7d5b4

Thread 6
[0] libc.so.6 + 0xdbe38
[1] libc.so.6 + 0xdbe18
[2] libglib-2.0.so.0 + 0xaae54
[3] libglib-2.0.so.0 + 0x52f10
[4] libQt6Core.so.6 + 0x374560
[5] libQt6Core.so.6 + 0x131650
[6] libQt6Core.so.6 + 0x21e970
[7] libQt6Core.so.6 + 0x28b674
[8] libc.so.6 + 0x7d5b4

Thread 7
[0] libc.so.6 + 0x79de8
[1] libc.so.6 + 0x79dc4
[2] libc.so.6 + 0x7cbfc
[3] libQt6Core.so.6 + 0x295714
[4] libQt6Core.so.6 + 0x29546c
[5] libQt6Core.so.6 + 0x28f0b4
[6] libQt6Core.so.6 + 0x28b674
[7] libc.so.6 + 0x7d5b4

Thread 8
[0] libc.so.6 + 0xdbe38
[1] libc.so.6 + 0xdbe18
[2] libglib-2.0.so.0 + 0xaae54
[3] libglib-2.0.so.0 + 0x52f10
[4] libQt6Core.so.6 + 0x374544
[5] libQt6Core.so.6 + 0x131650
[6] libQt6Core.so.6 + 0x21e970
[7] libQt6Core.so.6 + 0x28b674
[8] libc.so.6 + 0x7d5b4

Thread 9
[0] libc.so.6 + 0x79de8
[1] libc.so.6 + 0x79dc4
[2] libc.so.6 + 0x7cbfc
[3] libQt6Core.so.6 + 0x295714
[4] libQt6Core.so.6 + 0x29546c
[5] libQt6Core.so.6 + 0x28f0b4
[6] libQt6Core.so.6 + 0x28b674
[7] libc.so.6 + 0x7d5b4

Thread 10
[0] libc.so.6 + 0x79de8
[1] libc.so.6 + 0x79dc4
[2] libc.so.6 + 0x7cbfc
[3] libQt6Core.so.6 + 0x295714
[4] libQt6Core.so.6 + 0x29546c
[5] libQt6Core.so.6 + 0x28f0b4
[6] libQt6Core.so.6 + 0x28b674
[7] libc.so.6 + 0x7d5b4

Thread 11
[0] libc.so.6 + 0x79de8
[1] libc.so.6 + 0x79dc4
[2] libc.so.6 + 0x7cbfc
[3] libQt6Core.so.6 + 0x295714
[4] libQt6Core.so.6 + 0x29546c
[5] libQt6Core.so.6 + 0x28f0b4
[6] libQt6Core.so.6 + 0x28b674
[7] libc.so.6 + 0x7d5b4

Thread 12
[0] libc.so.6 + 0x79de8
[1] libc.so.6 + 0x79dc4
[2] libc.so.6 + 0x7cbfc
[3] libQt6Core.so.6 + 0x295714
[4] libQt6Core.so.6 + 0x29546c
[5] libQt6Core.so.6 + 0x28f0b4
[6] libQt6Core.so.6 + 0x28b674
[7] libc.so.6 + 0x7d5b4

Thread 13
[0] libc.so.6 + 0x79de8
[1] libc.so.6 + 0x79dc4
[2] libc.so.6 + 0x7cbfc
[3] libQt6Core.so.6 + 0x295714
[4] libQt6Core.so.6 + 0x29546c
[5] libQt6Core.so.6 + 0x28f0b4
[6] libQt6Core.so.6 + 0x28b674
[7] libc.so.6 + 0x7d5b4

Thread 14
[0] libc.so.6 + 0x79de8
[1] libc.so.6 + 0x79dc4
[2] libc.so.6 + 0x7cbfc
[3] libQt6Core.so.6 + 0x295714
[4] libQt6Core.so.6 + 0x29546c
[5] libQt6Core.so.6 + 0x28f0b4
[6] libQt6Core.so.6 + 0x28b674
[7] libc.so.6 + 0x7d5b4

2

Adding @mstrengert to make sure to get some eyes on this.

3

I am going to include the .ncu-rep file. I created this file using ncu, and when I try to run ncu-ui it crashes the same way. This was from the cuda routine vectorAdd.

report.zip (16.2 KB)

4

Hi, @nbeser1

Sorry for the issue you met.
This seems same issue as this Nsight Compute crash with message: free(): invalid pointer

You can upgrade cuda toolkit to have another try.

5

Are you suggesting that I upgrade the cuda toolkit on the jetson orin nano to 12.8? I did not think that jetpack 6.2 would permit that. I developed a work around that I would not recommend to anyone yet. I have a jetson orin nano that is running jetpack 6.0 with cuda 12.2.140. It has nsight-compute 2023.2.2. I created a tar.gz with nsight-compute 2023.2.2 and then transferred it to my newer jetson orin nano. It seems to work properly on the new jetson. That system is running cuda 12.6.65… When I installed ncu and ncu-ui for 2023.2.2 I am able to run ncu-ui.

Please confirm that you are suggesting that I upgrade cuda to 12.8.

6

Yes. You need to install compat package also to make CUDA 12.8 compatible with Jetpack 6.2

7

What compat package to make it comply with jetpack 6.2?

8

image
image1386×246 17.6 KB

9

Thank-you I will try that tonight and let you know.

10

I think the upgrade has caused a new problem. Our jetson orin nanos have dual cameras installed.

Now if we try to use the camera we get the following error:
$ nvgstcapture-1.0
Encoder null, cannot set bitrate!
Encoder Profile = High
Codec not supported. Falling back to opensrc H264 encoder
Supported resolutions in case of ARGUS Camera
(2) : 640x480
(3) : 1280x720
(4) : 1920x1080
(5) : 2104x1560
(6) : 2592x1944
(7) : 2616x1472
(8) : 3840x2160
(9) : 3896x2192
(10): 4208x3120
(11): 5632x3168
(12): 5632x4224

Runtime ARGUS Camera Commands:

Help : ‘h’
Quit : ‘q’
Set Capture Mode:
mo:
(1): image
(2): video
Get Capture Mode:
gmo
Set sensor orientation:
so:
(0): none
(1): Rotate counter-clockwise 90 degrees
(2): Rotate 180 degrees
(3): Rotate clockwise 90 degrees
Get sensor orientation:
gso
Set sensor mode:
smo: e.g., smo:1
Get sensor mode:
gsmo
Set Whitebalance Mode:
wb:
(0): off
(1): auto
(2): incandescent
(3): fluorescent
(4): warm-fluorescent
(5): daylight
(6): cloudy-daylight
(7): twilight
(8): shade
(9): manual
Get Whitebalance Mode:
gwb
Set Saturation (0 to 2):
st: e.g., st:1.25
Get Saturation:
gst
Set Exposure Compensation (-2 to 2):
ec: e.g., ec:-2
Get Exposure Compensation:
gec
Set Auto Whitebalance Lock:
awbl: e.g., awbl:0
Get Auto Whitebalance Lock:
awbl
Set Auto Exposure Lock:
ael: e.g., ael:0
Get Auto Exposure Lock:
gael
Set TNR Mode:
tnrm: e.g., tnrm:1
(0): OFF
(1): FAST
(2): HIGH QUALITY
Get TNR Mode:
gtnrm
Set TNR Strength (-1 to 1):
tnrs: e.g., tnrs:0.5
Get TNR Strength:
gtnrs
Set EE Mode:
eem: e.g., eem:1
(0): OFF
(1): FAST
(2): HIGH QUALITY
Get EE Mode:
geem
Set EE Strength (-1 to 1):
ees: e.g., ees:0.5
Get EE Strength:
gees
Set Auto Exposure Anti-Banding (0 to 3):
aeab: e.g., aeab:2
(0): OFF
(1): MODE AUTO
(2): MODE 50HZ
(3): MODE 60HZ
Get Auto Exposure Anti-Banding:
gaeab
Set Gain Range:
gr: e.g., gr:1 16
Get Gain Range:
ggr
Set Exposure Time Range:
etr: e.g., etr:34000 35000
Get Exposure Time Range:
getr
Set ISP Digital Gain Range:
dgr: e.g., dgr:2 152
Get ISP Digital Gain Range:
gdgr
Capture: enter ‘j’ OR
followed by a timer (e.g., jx5000, capture after 5 seconds) OR
followed by multishot count (e.g., j:6, capture 6 images)
timer/multihot values are optional, capture defaults to single shot with timer=0s
Start Recording : enter ‘1’
Stop Recording : enter ‘0’
Video snapshot : enter ‘2’ (While recording video)
Get Preview Resolution:
gpcr
Get Image Capture Resolution:
gicr
Get Video Capture Resolution:
gvcr

Runtime encoder configuration options:

Set Encoding Bit-rate(in bytes):
br: e.g., br:4000000
Get Encoding Bit-rate(in bytes):
gbr
Set Encoding Profile(only for H.264):
ep: e.g., ep:1
(0): Baseline
(1): Main
(2): High
Get Encoding Profile(only for H.264):
gep
Force IDR Frame on video Encoder(only for H.264):
Enter ‘f’

(nvgstcapture-1.0:3737): GStreamer-WARNING **: 21:32:54.471: Failed to load plugin ‘/usr/lib/aarch64-linux-gnu/gstreamer-1.0/libgstnvarguscamerasrc.so’: /usr/lib/aarch64-linux-gnu/nvidia/libnvcam_imageencoder.so: undefined symbol: jpeg_set_defaults

** (nvgstcapture-1.0:3737): ERROR **: 21:32:54.471: <create_csi_cap_bin:2186> Element nvarguscamerasrc creation failed

Trace/breakpoint trap (core dumped)

I have three jetsons running in my lab. One has jetpack 6.0, and two have jetpack 6.2. One of the jetpack 6.2 has been updated to cuda toolbox 12.8. That one produces the error. The one that was not updated is able to access the camera. Any idea why the patch seems to produce this error?

11

Sorry for the issue you met. But I don’t think cuda toolkit update would have impact on camera.
From the log, it shows GStreamer related issue.

12

My student’s jetson orin nano systems that were updated to Cuda 2.8 following your patch now are showing the same camera problem. I did a search on this type of error message, and there was no apparent fix for the problem. I thought that the patch might have reset or eliminated something connected to the camera.

13

Veraj, I can understand your reluctance to accept the cause, but I thought I would try to setup a test that you might agree with. I have a spare jetson orin nano that I used the SDK Manager on, and setup jetpack 6.2. I also loaded a number of utilities including Firefox, jtop from jetsonHacks and opencv with cuda suppport. I then loaded two nvidia github sources, and one jetsonhacks source that supported cameras. Their links are:

https://github.com/dusty-nv/jetson-utils * Links to an external site.

I tested both the jetson_utils and CSI_Camera utilities and was able to capture images, and save two mpg files. I then loaded your patch to upgrade the cuda toolkit. I then attempted to use the camera capture utility, and it failed. The attachment contains the terminallog.txt file, and a PNG of the screen shot showing the cuda 2.8 toolbox has been installed. There is a screen shot of the simple_camera app which worked in the terminal log but failed right after the patch was applied.

I could use some help in fixing this problem. One of my student’s followed your instruction and now he can’t run the camera which is part of this week’s module. I need to either reverse what was done to the computer, or fix the problem. so that the camera could work again. I do not want to instruct the student to wipe his computer, because there is a half a semester worth or work currently on his system.
OneDrive_1_3-15-2025.zip (6.9 MB)

14

I found a way to recover the camera operation. I used the command to remove the latest cuda toolbox 12.8. What was left was cuda 12.6, and the camera routines started working again.

sudo apt-get remove --purge cuda 12.8

By copying the older nsight-compute version to the jetpack 6.2, I was able to get nsight-compute working. I don’t consider that a good solution, but it allows my students to progress with their homework.

I would like to find out why the cuda upgrade broke the camera routines. That would allow me to use a newer cuda toolbox with nsight compute as well as use the cameras

15

Hi, @nbeser1

Sorry for the issue you met and good to know you have reverted the board back to work.

Regarding upgrading to CUDA 12.8 cause camera not work. Can you please start a new topic in Jetson Nano forum directly ?

16

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