[ 8.379445] pcieport 0004:00:00.0: Adding to iommu group 5
[ 8.379562] pcieport 0004:00:00.0: PME: Signaling with IRQ 193
[ 8.379703] pcieport 0004:00:00.0: AER: enabled with IRQ 193
[ 8.379932] nvme 0004:01:00.0: Adding to iommu group 5
[ 8.380139] nvme nvme0: pci function 0004:01:00.0
[ 8.380201] nvme 0004:01:00.0: enabling device (0000 → 0002)
[ 8.380837] tegra194-pcie 141e0000.pcie: Adding to iommu group 6
[ 8.382100] tegra194-pcie 141e0000.pcie: host bridge /bus@0/pcie@141e0000 ranges:
[ 8.382115] tegra194-pcie 141e0000.pcie: MEM 0x3000000000…0x3227ffffff → 0x3000000000
[ 8.382123] tegra194-pcie 141e0000.pcie: MEM 0x3228000000…0x322fffffff → 0x0040000000
[ 8.382127] tegra194-pcie 141e0000.pcie: IO 0x003e100000…0x003e1fffff → 0x003e100000
[ 8.382447] tegra194-pcie 141e0000.pcie: iATU unroll: enabled
[ 8.382449] tegra194-pcie 141e0000.pcie: Detected iATU regions: 8 outbound, 2 inbound
[ 8.530167] nvme nvme0: allocated 64 MiB host memory buffer.
[ 8.562823] nvme nvme0: 6/0/0 default/read/poll queues
[ 8.587855] nvme nvme0: Ignoring bogus Namespace Identifiers
[ 8.596189] nvme0n1: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15
[ 8.713933] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
[ 8.719461] Rootfs mounted over PARTUUID=49e69760-c67f-4215-b70e-800e11076fae
[ 8.728518] Switching from initrd to actual rootfs
[ 8.731631] Kernel panic - not syncing:
[ 8.731635] Attempted to kill init! exitcode=0x00007f00
[ 8.731641] CPU: 2 PID: 1 Comm: chroot Not tainted 5.15.136-tegra #1
[ 8.731645] Hardware name: NVIDIA NVIDIA Jetson Orin NX Engineering Reference Developer Kit/Jetson, BIOS 36.3.0-gcid-36191598 05/06/2024
[ 8.731648] Call trace:
[ 8.731649] dump_backtrace+0x0/0x1d0
[ 8.731663] show_stack+0x34/0x50
[ 8.731667] dump_stack_lvl+0x68/0x8c
[ 8.731674] dump_stack+0x18/0x3c
[ 8.731676] panic+0xc4/0x398
[ 8.731679] do_exit+0xa1c/0xa50
[ 8.731683] do_group_exit+0x44/0xb0
[ 8.731686] __arm64_sys_exit_group+0x2c/0x30
[ 8.731689] invoke_syscall+0x5c/0x150
[ 8.731694] el0_svc_common.constprop.0+0x64/0x120
[ 8.731698] do_el0_svc+0x74/0xb0
[ 8.731701] el0_svc+0x28/0x90
[ 8.731703] el0t_64_sync_handler+0xac/0x130
[ 8.731705] el0t_64_sync+0x1a4/0x1a8
Custom carrier board or devkit?
Which JetPack SW?
Root File System — NVIDIA Jetson Linux Developer Guide 1 documentation
Follow the tutorial to build the Basic Flavor Root File System。
jeston36.3
I want to port the root file without desktop。
My development board is NVidia orin Nano 4G。
sudo ./nv_build_samplefs.sh --abi aarch64 --distro ubuntu --flavor basic --version jammy
The root file obtained through this。
I see this:
This isn’t a “smoking gun” evidence, but when it switches from initrd to the actual filesystem, this is when panic occurs. It is highly likely your initrd needs to be modified to pivot_root to your filesystem. I have no idea what the current system is doing, but make sure your initrd is valid with that filesystem.
Hi 56101855,
Are you using the devkit or custom board for Orin Nano?
Do you refer to Minimal Flavor Root File System?
Have you created a default user through running l4t_create_default_user.sh in Skipping oem-config before flash?
Please also share the full serial console log for further check.
I built “Basic Flavor Root File System”。
The “Basic Flavor Root File System” generated by following this tutorial。
Root filesystem construction step：
$ sudo apt-get install docker.io
$ sudo docker run --privileged -it --rm -v <your_L4T_root>/Linux_for_Tegra:/l4t ubuntu:22.04
(in the container) $ apt-get update
(in the container) $ apt-get install -y qemu-user-static wget sudo bzip2
(in the container) $ cd /l4t/tools/samplefs
(in the container) $ ./nv_build_samplefs.sh --abi aarch64 --distro ubuntu --flavor basic --version jammy
(in the container) $exit
$ sudo tar -xpf ~/nvidia/Linux_for_Tegra/tools/samplefs ~/nvidia/Linux_for_Tegra/rootfs
Burn operation steps：
sudo ./apply_binaries.sh
sudo ./tools/l4t_create_default_user.sh -u ys -p 123456
sudo ./tools/l4t_flash_prerequisites.sh
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" --showlogs --network usb0 jetson-orin-nano-devkit internal
I followed the above steps to generate the “Minimal Flavor Root File System” version, which can be used normally after burning.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.