Root device (mmcblk0p1) was not found while doing reboot stress test with Jetson Linux 35.1

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
1

Hi,

We flashed the Jetson Linux 35.1 image from sdk manager into our carrier board + P3668-0001 NX SOM (EMMC SKU). We used the NVP Model clock configuration tool for set the power mode to “20Ｗ-6 Core” and did the reboot stress test for testing system stabiblity. The main differnece between our carrier board and devkit is that carrier board has USB LAN (rt8152) and LTE module (Quectel EG25) . We meet a problem is “Root device was not found and cause system hang”. Please help to check this. Thanks

Normal log

[ 0.000000] Kernel command line: root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0
…
[ 6.882553] mmcblk0: mmc0:0001 DG4016 14.7 GiB
[ 6.883162] mmcblk0rpmb: mmc0:0001 DG4016 partition 3 4.00 MiB, chardev (510:0)
[ 6.967665] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19
[ 7.370115] Root device found: mmcblk0p1
[ 7.376803] Found dev node: /dev/mmcblk0p1
[ 7.411764] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
[ 7.415730] Rootfs mounted over mmcblk0p1
[ 8.488298] EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)

Fail log:

[ 0.000000] Kernel command line: root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0
…
[ 6.825295] mmcblk0: mmc0:0001 DG4016 14.7 GiB
[ 6.825423] mmcblk0rpmb: mmc0:0001 DG4016 partition 3 4.00 MiB, chardev (510:0)
[ 6.829299] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19
jetpack502-mount emmc fail.log (1.8 MB)

3

Why are you filing a new topic again while you already filed a duplicated one few days ago?

What is the point here?

4

Hi,

They are different , this case doesn’t enter recovery mode and reboot it can recover. But the other case is not, we can’t recover it through reboot. It always boot from initrd.

5

I feel these issues are same. Sometimes. mmcblk0p1 will disappear, and if that happened in UEFI, then it will enter UEFI recovery boot. But if that happened later, then rootfs will be gone.

Could you try to reproduce your issue on devkit? I don’t feel we would see bpmp error on devkit in boot stress.

7

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