Hi,
we have an customized rootfs and kernel based on Jetson Linux 35.4.1 flashed on carrier board with Jetson AGX Orin SOM on it. System is flashed with AB support.
For some reason after flashing I can switch from A slot to B slot but cannot switch back from B slot to the A slot. What should I check to understand why switching works only in one way?
Hi,
If the device cannot be flashed/booted, please refer to the page to get uart log from the device:
Jetson/General debug - eLinux.org
And get logs of host PC and Jetson device for reference. If you are using custom board, you can compare uart log of developer kit and custom board to get more information.
Also please check FAQs:
Jetson AGX Orin FAQ
If possible, we would suggest follow quick start in developer guide to re-flash the system:
Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation
And see if the issue still persists on a clean-flashed system.
Thanks!
The issue is that when I’m trying to switch next boot slot from B to A using command sudo nvbootctrl set-active-boot-slot 0 && sudo reboot now I’m still booting into the roots in slot B.
Here is console output from booting after switching from slot B to slot A:
b_to_a_fail.log (29.7 KB)
As a reference, here is console output when I’m successfully switching from A to B:
a_to_b_success.log (57.8 KB)
hello zaripov-kamil,
you may try adding -t <target> options since it’s by default to toggle bootloader slots.
please see-also Dumping Root File Systems Slot A and Slot B Information,
please execute the command to check current rootfs slot status,
$sudo nvbootctrl -t rootfs dump-slots-info
Ok, here is full log starting from the checking current slot (which is B), switching to the slot A and full reboot log until I boot into slot B again:
b_to_a_fail_full.log (57.7 KB)
according to the logs.. it’s booting with bootloader slot:1
for instance,
[0000.318] I> Loading MEMBCT
[0000.320] I> Slot: 1
...
I> Current Boot-Chain Slot: 1
please note that, when rootfs A/B is enabled, Jetson Linux always links the rootfs A/B with Bootloader A/B.
please refer to Manually Modifying Boot Slots for changing bootloader slots as well.
Yes, I know and this is the issue. You can see in the top of b_to_a_fail_full.log that I’m calling command sudo nvbootctrl set-active-boot-slot 0 right before reboot but it seems that it does not work since I’m booting into slot 1.
please refer to Manually Modifying Boot Slots for changing bootloader slots as well.
Am I right that calling sudo nvbootctrl set-active-boot-slot 0 is enough to switch bootloader slot to slot 0?
hello zaripov-kamil,
it should be $ sudo nvbootctrl set-active-boot-slot 0 to switch both bootloader and rootfs.
please also execute $ sudo nvbootctrl dump-slots-info to check the bootloader status.
BTW,
here’s one thing strange regrading to below.
[ OK ] Reached target Late Shutdown Services.
[ OK ] Finished System Reboot.
[ OK ] Reached target System Reboot.
[152443.982148] watchdog: watchdog0: watchdog did not stop!
[152444.246677] systemd-shutdown[1]: Failed to disable hardware watchdog, ignoring: Device or resource busy
[152444.246983] watchdog: watchdog0: watchdog did not stop!
[152444.613884] shutdown[1]: Failed to disable hardware watchdog, ignoring: Device or resource busy
[152444.614160] watchdog: watchdog0: watchdog did not stop!
[15244����4.859206] reboo��
is your system restart automatically? or, you’re using a hardware key to restart the system?
it should be
$ sudo nvbootctrl set-active-boot-slot 0to switch both bootloader and rootfs.
please also execute$ sudo nvbootctrl dump-slots-infoto check the bootloader status.
Hi, you can see in b_to_a_fail_full.log that I’m executing exact these commands to swtich slot from 1 to 0. And according to the sudo nvbootctrl -t rootfs dump-slots-info output active slot become 0.
BTW,
here’s one thing strange regrading to below.[ OK ] Reached target Late Shutdown Services. [ OK ] Finished System Reboot. [ OK ] Reached target System Reboot. [152443.982148] watchdog: watchdog0: watchdog did not stop! [152444.246677] systemd-shutdown[1]: Failed to disable hardware watchdog, ignoring: Device or resource busy [152444.246983] watchdog: watchdog0: watchdog did not stop! [152444.613884] shutdown[1]: Failed to disable hardware watchdog, ignoring: Device or resource busy [152444.614160] watchdog: watchdog0: watchdog did not stop! [15244����4.859206] reboo��is your system restart automatically? or, you’re using a hardware key to restart the system?
You can see in log that I’m rebooting the system using sudo reboot now command. What exactly is strange thing? The errors from the watchdog?
hello zaripov-kamil,
for instance, is the system reboot (actually) within coupe of seconds?
for instance, is the system reboot (actually) within coupe of seconds?
It takes about 4.3s between sudo reboot now execution and last reboot message from the kernel.
hello zaripov-kamil,
could you please interrupt UEFI to check slot A/B status from UEFI menu as well.
BTW, is it a must to stay-on JP-5.1.2/r35.4.1? is it possible moving forward to latest JP-5 or even JP-6 for verificaiton?
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.