boards: Update Orin board files spiking some warnings for Ubuntu for Jetson #7
Conversation
…Jetson
AGX Orin, Orin Nano/NX board files:
- Skip list the following Kernel warnings:
- SPI driver altr_a10sr has no spi_device_id for altr,a10sr
- device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
- NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0xffff:
- r8168 Copyright (C) 2024 Realtek NIC software team <nicfae@realtek.com>
This program comes with ABSOLUTELY NO WARRANTY; for details, please see <http://www.gnu.org/licenses/>.
This is free software, and you are welcome to redistribute it under certain conditions; see <http://www.gnu.org/licenses/>.
|
Hi @EstebanVg15 - please add @thierryreding as reviewer (I am not able to add him). Hi @thierryreding - please review this PR. It adds few benign warnings, that are observed in Ubuntu for Tegra, in the skiplist for JP6.x. CC: @jonhunter |
Hi @paritoshd-nv , Thanks for the follow up, I think I am not able to select a reviewer, could this be a permission/related issue ? |
| 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', |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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'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.', |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
@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'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:', |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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?
| 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/>.', |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
I agree, the driver should be patched instead, I will remove this one from the skip list, thanks!
3 participants
Description
This PR is based on Canonical testing when running the
tegra-teststool on the Ubuntu Kernel.Tests
Run the following commands on AGX Orin, and on Orin Nano/NX devices.
tegra-tests-results.zip