Developing with SSD on Jetson TX2 and getting segmentaion fault
I use a SSD as the root directory for development following the tutorial [url]http://www.jetsonhacks.com/2017/08/05/develop-on-ssd-nvidia-jetson-tx1-and-jetson-tx2/[/url]. I've installed CUDA and CUDNN and used [code]nvcc -V[/code] to verify. Also, use cudnn_sample_v6 to verify CUDNN, but get "segmentation fault".
I use a SSD as the root directory for development following the tutorial http://www.jetsonhacks.com/2017/08/05/develop-on-ssd-nvidia-jetson-tx1-and-jetson-tx2/.
I've installed CUDA and CUDNN and used
nvcc -V
to verify.
Also, use cudnn_sample_v6 to verify CUDNN, but get "segmentation fault".

#1
Posted 04/16/2018 02:51 AM   
Hi, Could you also test CUDA sample which is located at '/usr/local/cuda-[version]'? Thanks.
Hi,

Could you also test CUDA sample which is located at '/usr/local/cuda-[version]'?

Thanks.

#2
Posted 04/16/2018 03:10 AM   
Sure, all of the CUDA samples result in the same "Segmentation fault (core dumped)". Thanks.
Sure, all of the CUDA samples result in the same "Segmentation fault (core dumped)".

Thanks.

#3
Posted 04/16/2018 03:56 AM   
You might want to run in gdb and get a stackframe/backtrace.
You might want to run in gdb and get a stackframe/backtrace.

#4
Posted 04/16/2018 03:55 PM   
Hi, What do you mean and how to fix it? Thanks.
Hi,

What do you mean and how to fix it?

Thanks.

#5
Posted 04/16/2018 06:04 PM   
Stack frames are just debug info...it won't actually change anything. When you run a program in gdb and it crashes from a seg fault it'll stop at the current location in the source code. The "bt" (backtrace) command will show the stack frame...which is a list of what actual source code is running at that instant and just prior. Do you use arguments when you run the program? Assuming your program is named "sample", and that you are in the directory where it is, then you would do something like this: [code]gdb ./sample r bt q y[/code] The "r" command says to run. Assuming the program crashes it will stop...then "bt" will show the backtrace (stack frame)...this is what you want to post here in the forum. "q" will quit..."y" is when it asks if you really want to quit a running program.
Stack frames are just debug info...it won't actually change anything. When you run a program in gdb and it crashes from a seg fault it'll stop at the current location in the source code. The "bt" (backtrace) command will show the stack frame...which is a list of what actual source code is running at that instant and just prior.

Do you use arguments when you run the program? Assuming your program is named "sample", and that you are in the directory where it is, then you would do something like this:
gdb ./sample
r
bt
q
y


The "r" command says to run. Assuming the program crashes it will stop...then "bt" will show the backtrace (stack frame)...this is what you want to post here in the forum. "q" will quit..."y" is when it asks if you really want to quit a running program.

#6
Posted 04/16/2018 06:40 PM   
Hi, We are trying to reproduce this issue internally. Just want to confirm that you are using JetPack 3.1 on TX2, is this correct? We will update further information with you later. Thanks.
Hi,

We are trying to reproduce this issue internally.
Just want to confirm that you are using JetPack 3.1 on TX2, is this correct?

We will update further information with you later.
Thanks.

#7
Posted 04/17/2018 03:05 AM   
Hi, Yes, I am using JetPack 3.1 on TX2. The version of CUDA is 8.0.84-1 and CUDNN is 6.0.21-1. The solid-state drive that I am using is Intel. Thanks.
Hi,

Yes, I am using JetPack 3.1 on TX2.
The version of CUDA is 8.0.84-1 and CUDNN is 6.0.21-1.
The solid-state drive that I am using is Intel.

Thanks.

#8
Posted 04/17/2018 05:19 AM   
Hi, I am using JetPack 3.1 to install ubuntu 16.04 only. Then, copy CUDA and CUDNN files in jetpack_download folder, and install them individually. Thanks.
Hi,

I am using JetPack 3.1 to install ubuntu 16.04 only.
Then, copy CUDA and CUDNN files in jetpack_download folder, and install them individually.

Thanks.

#9
Posted 04/17/2018 05:25 AM   
Hi, We have verified the functionality of an installation on SSD. Everything works well and CUDA can be launched without a segmentation fault. Guess that there are some issues when setting up the libraries. Please remember that the CUDA driver for Jetson is included in the OS. And it's recommended to install the libraries from JetPack directly. Please let us know if there is any installed driver or library that not originate from JetPack. Thanks.
Hi,

We have verified the functionality of an installation on SSD.
Everything works well and CUDA can be launched without a segmentation fault.

Guess that there are some issues when setting up the libraries.
Please remember that the CUDA driver for Jetson is included in the OS.
And it's recommended to install the libraries from JetPack directly.

Please let us know if there is any installed driver or library that not originate from JetPack.

Thanks.

#10
Posted 04/17/2018 06:23 AM   
JetPack is capable of installing CUDA on the host as well. Are you sure you didn't get the x86_64 CUDA files?
JetPack is capable of installing CUDA on the host as well. Are you sure you didn't get the x86_64 CUDA files?

#11
Posted 04/17/2018 06:59 PM   
Hi, linuxdev I am quite sure that it was CUDA for arm64, so [code]nvcc -V[/code] could get the CUDA version. Thanks.
Hi, linuxdev

I am quite sure that it was CUDA for arm64, so
nvcc -V
could get the CUDA version.

Thanks.

#12
Posted 04/18/2018 07:07 AM   
Hi, AastallL Follow your suggestion by installing all packages via [b]Jetpack 3.1[/b] and everything goes well before the following step: I used [b]buildJetsonTX2Kernel[/b] [url]https://github.com/jetsonhacks/buildJetsonTX2Kernel[/url] and got the new [b]ImageSSD[/b] with version [b]-jetsonbot-v0.1[/b]. Then, changed the context in the [b]extlinux.conf[/b] file shown as follows. [code] TIMEOUT 30 DEFAULT primary MENU TITLE p2771-0000 eMMC boot options LABEL primary MENU LABEL primary kernel SSD LINUX /boot/ImageSSD APPEND ${cbootargs} root=/dev/sda1 rw rootwait rootfstype=ext4 LABEL eMMC MENU LABEL eMMC kernel LINUX /boot/Image APPEND ${cbootargs} root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 [/code] After rebooting, I ran the CUDA and cuDNN samples and got [b]segmentation fault[/b] again. Could you help me build the JetsonTX2 kernel properly? Thanks.
Hi, AastallL

Follow your suggestion by installing all packages via Jetpack 3.1 and everything goes well before the following step:

I used buildJetsonTX2Kernel https://github.com/jetsonhacks/buildJetsonTX2Kernel and got the new ImageSSD with version -jetsonbot-v0.1.

Then, changed the context in the extlinux.conf file shown as follows.

TIMEOUT 30
DEFAULT primary

MENU TITLE p2771-0000 eMMC boot options

LABEL primary
MENU LABEL primary kernel SSD
LINUX /boot/ImageSSD
APPEND ${cbootargs} root=/dev/sda1 rw rootwait rootfstype=ext4

LABEL eMMC
MENU LABEL eMMC kernel
LINUX /boot/Image
APPEND ${cbootargs} root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4


After rebooting, I ran the CUDA and cuDNN samples and got segmentation fault again.

Could you help me build the JetsonTX2 kernel properly?

Thanks.

#13
Posted 04/18/2018 08:26 AM   
When using that kernel what shows up from "uname -r"? Are there modules at "/lib/modules/$(uname -r)/"?
When using that kernel what shows up from "uname -r"? Are there modules at "/lib/modules/$(uname -r)/"?

#14
Posted 04/18/2018 05:06 PM   
Hi linuxdev, [code] uname -r 4.4.38-jetsonbot-v0.1 [/code] There are two modules folders in the folder "/lib/modules/4.4.38-tegra": [b]4.4.38-jetsonbot-v0.1[/b] and [b]4.4.38-tegra[/b] Thanks.
Hi linuxdev,

uname -r
4.4.38-jetsonbot-v0.1


There are two modules folders in the folder "/lib/modules/4.4.38-tegra":
4.4.38-jetsonbot-v0.1 and 4.4.38-tegra

Thanks.

#15
Posted 04/19/2018 02:33 AM   
Scroll To Top

Add Reply