Skip to content

boards: Update Orin board files spiking some warnings for Ubuntu for Jetson #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
EstebanVg15 wants to merge 1 commit into
base: jetpack6.x
Choose a base branch
from
Open

boards: Update Orin board files spiking some warnings for Ubuntu for Jetson #7

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions boards/nvidia/jetson-agx-orin.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -260,6 +260,9 @@ class Board(boards.Board):
r'platform regulatory.0: Falling back to sysfs fallback for: regulatory.db',
r'IRQ\d*: set affinity failed\(-22\).',
r'nvme nvme0: missing or invalid SUBNQN field.',
r'SPI driver altr_a10sr has no spi_device_id for altr,a10sr',
Copy link
Copy Markdown
Owner

@thierryreding thierryreding Sep 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks odd. Judging by this commit 4ea673e87e50684249223103ccdfef2c0ea83321 in mainline (added in 5.16) there is a SPI device ID for this. Any idea why that's being flagged for you? Are you using this on kernels older than that?

Copy link
Copy Markdown
Author

@EstebanVg15 EstebanVg15 Oct 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @thierryreding ,

Thanks for the follow up on this one, yes we are using a Jammy 5.15 Kernel, we included the suggested patch into our Kernel and now the error message is gone, thank you for that!

I will remove this one from the skip list.

r'device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.',
Copy link
Copy Markdown
Owner

@thierryreding thierryreding Sep 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Judging by the message of the commit that added this warning, enabling IMA_DISABLE_HTABLE is something that you want. Maybe a better approach would be to enable that Kconfig option?

Copy link
Copy Markdown
Author

@EstebanVg15 EstebanVg15 Oct 15, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@thierryreding I talked about this suggestion with our Kernel engineer.

First it is important to say that CONFIG_IMA was intentionally enabled in the generic kernel due to a known bug (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643652).

Meanwhile, "CONFIG_IMA_DISABLE_HTABLE" is kept in the default state of "=n"; for what we could find, enabling "CONFIG_IMA_DISABLE_HTABLE" might have some slight performance hits for tpm measurement, even though it should not break anything, we think that is better to keep that one unchanged.

Could we revisit the approach of integrating this one to the skip-list?

r'NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0xffff:',
Copy link
Copy Markdown
Owner

@thierryreding thierryreding Sep 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is probably good to ignore. We'll look into what exactly this is and why it's even showing. Either it's a real problem that we need to fix or it is not and then it shouldn't be an error/warning.

Copy link
Copy Markdown
Author

@EstebanVg15 EstebanVg15 Oct 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

About this one I was wondering which would be the best path-forward, should we add it to the skip list for the test to succeed? or just ignore it even if the test case continue failing due to this known issue?

]

# Add additional dmesg warn, err here that are to be ignored in the logs test
Expand Down
4 changes: 4 additions & 0 deletions boards/nvidia/jetson-orin-nano.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -229,6 +229,10 @@ class Board(boards.Board):
r'platform regulatory.0: Falling back to sysfs fallback for: regulatory.db',
r'IRQ\d*: set affinity failed\(-22\).',
r'nvme nvme0: missing or invalid SUBNQN field.',
r'SPI driver altr_a10sr has no spi_device_id for altr,a10sr',
r'device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.',
r'NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0xffff:',
r'r8168 Copyright \(C\) 2024 Realtek NIC software team <nicfae@realtek.com> \\x0a This program comes with ABSOLUTELY NO WARRANTY; for details, please see <http://www.gnu.org/licenses/>. \\x0a This is free software, and you are welcome to redistribute it under certain conditions; see <http://www.gnu.org/licenses/>.',
Copy link
Copy Markdown
Owner

@thierryreding thierryreding Sep 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know where this is coming from, but I suspect it's from the Realtek vendor module. This does not warrant error or warning level, so I think that driver should be patched and have that message demoted to something like info or debug.

Copy link
Copy Markdown
Author

@EstebanVg15 EstebanVg15 Oct 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, the driver should be patched instead, I will remove this one from the skip list, thanks!

]

# Add additional dmesg warn, err here that are to be ignored in the logs test
Expand Down
4 changes: 4 additions & 0 deletions boards/nvidia/jetson-orin-nx.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -244,6 +244,10 @@ class Board(boards.Board):
r'platform regulatory.0: Falling back to sysfs fallback for: regulatory.db',
r'IRQ\d*: set affinity failed\(-22\).',
r'nvme nvme0: missing or invalid SUBNQN field.',
r'SPI driver altr_a10sr has no spi_device_id for altr,a10sr',
r'device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.',
r'NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0xffff:',
r'r8168 Copyright \(C\) 2024 Realtek NIC software team <nicfae@realtek.com> \\x0a This program comes with ABSOLUTELY NO WARRANTY; for details, please see <http://www.gnu.org/licenses/>. \\x0a This is free software, and you are welcome to redistribute it under certain conditions; see <http://www.gnu.org/licenses/>.',
]

# Add additional dmesg warn, err here that are to be ignored in the logs test
Expand Down