Error reported on serial port during AGX Orin boot: IRQ301: set affinity failed(-22)

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
,
1

Hardware: NVIDIA AGX Orin 64GB + custom carrier board**
Software:** R36.4.0
The error message is as follows:
Starting RmBootstrap

Registered event_type:[0] for dce_core_ipc_type:[1]

Registered event_type:[1] for dce_core_ipc_type:[3]

dce_ipc State Initialized

RmBootstrap completed successfully

[ 11.950862] got firmware version: 2026.

[ 13.864305] IRQ301: set affinity failed(-22).

[ 13.864315] IRQ302: set affinity failed(-22).

[ 13.864317] IRQ303: set affinity failed(-22).

[ 13.864319] IRQ304: set affinity failed(-22).

[ 13.864322] IRQ305: set affinity failed(-22).

[ 13.864323] IRQ306: set affinity failed(-22).

[ 13.864325] IRQ307: set affinity failed(-22).

[ 13.864326] IRQ308: set affinity failed(-22).

[ 13.952003] IRQ301: set affinity failed(-22).

[ 13.952016] IRQ302: set affinity failed(-22).

Ubuntu 22.04.4 LTS ubuntu ttyTCU0
**
Detailed serial boot log is as follows:**

AGX Orin nomal boot1.log (73.5 KB)

3

*** Please note that this reply is generated by LLM automatically ***

Based on the provided information, it appears that you have a custom carrier board for the Jetson AGX Orin module, and you are experiencing issues with the boot process. The serial boot log you provided indicates that the system is booting normally, but there might be some issues with the boot configuration.

Here’s a breakdown of the boot log:

  1. RmBootstrap Registered eventtype0 for dcecoreipctype1: This line indicates that the RmBootstrap (a boot component) has registered an event type 0 for the DCE (Display Control Engine) core IP type 1.
  2. Registered eventtype1 for dcecoreipctype3: This line indicates that the RmBootstrap has registered an event type 1 for the DCE core IP type 3.
  3. dceipc State Initialized: This line indicates that the DCE IPC (Inter-Processor Communication) state has been initialized.
  4. RmBootstrap completed successfully: This line indicates that the RmBootstrap has completed its initialization successfully.
  5. Ubuntu 22.04 LTS ubuntu ttyTCU0: This line indicates that the system has booted into Ubuntu 22.04 LTS, and the terminal is available on ttyTCU0.

Comparing this boot log to the normal boot log for the Jetson AGX Orin (AGX Orin nomal boot1log), we can see that the boot process appears to be normal. However, there might be some issues with the boot configuration that are not immediately apparent from the log.

To troubleshoot the issue, I would recommend checking the following:

  1. Boot configuration: Verify that the boot configuration is correct and matches the expected configuration for the custom carrier board.
  2. Bootloader: Check the bootloader version and configuration to ensure that it is compatible with the custom carrier board.
  3. Kernel: Verify that the kernel version and configuration are correct and compatible with the custom carrier board.
  4. Device tree: Check the device tree configuration to ensure that it is correct and compatible with the custom carrier board.
  5. EEPROM: Verify that the EEPROM configuration is correct and matches the expected configuration for the custom carrier board.

If you are still experiencing issues after checking these items, it may be helpful to provide more information about the custom carrier board and the boot configuration to further troubleshoot the issue.

In terms of the provided documentation, the following sections may be relevant to troubleshooting the issue:

  • Boot Architecture: This section provides information about the boot process and the different components involved.
  • T23x Boot Configuration Table: This section provides information about the boot configuration table and how to configure it for custom carrier boards.
  • Debugging on Jetson Platforms: This section provides information about debugging tools and techniques that can be used to troubleshoot issues on Jetson platforms.
  • Debugging the Kernel: This section provides information about debugging the kernel and how to use tools like kgdb to troubleshoot kernel issues.

I hope this information is helpful in troubleshooting the issue with your custom carrier board. If you have any further questions or need additional assistance, please don’t hesitate to ask.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

4

Hi idealong,

From the serial console log you shared, it seems the board can boot as expected.

set affinity failed(-22) means the kernel tried to bind an IRQ to a specific CPU/core, but the request was rejected with error -22, i.e. EINVAL (“Invalid argument”).
In practice, it usually means that IRQ’s affinity could not be changed to the requested CPU mask, and on Jetson this is often just a warning.