Information about kernel message

Technical Support
, , , ,
1

Hi,

i have some doubts regarding kernel message. My target is compsed from SoM verdin imx8mp 2GB and carrier board mallow. This my tdx info:

Software summary
------------------------------------------------------------
Bootloader:               U-Boot
Kernel version:           6.6.119-7.5.0-devel-ge5c5595adb06 #1-Torizon SMP PREEMPT Mon Jan  5 09:23:13 UTC 2026
Kernel command line:      root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.1/torizon/f2110b8ae890590f3d0d4b3d9ca84dfa84cc27e93362f4058cdd5be44cc3c8b7/0
Distro name:              NAME="Torizon OS"
Distro version:           VERSION_ID=7.5.0-devel-20260121131151-build.0
Distro variant:           VARIANT="Docker"
Hostname:                 verdin-imx8mp-15603379
------------------------------------------------------------

Hardware info
------------------------------------------------------------
HW model:                 Toradex Verdin iMX8M Plus WB on Mallow Board
Toradex version:          0064 V1.1A
Serial number:            15603379
Processor arch:           aarch64
------------------------------------------------------------

When i start my target i see the follows message:


Starting kernel ...

[    1.039654] nvmem imx-ocotp0: cell mac-address raw len 6 unaligned to nvmem word size 4
[    1.047697] nvmem imx-ocotp0: cell mac-address raw len 6 unaligned to nvmem word size 4
Starting systemd-udevd version 255.21^
sysroot.readonly configuration value: 0 (fs writable: 1)
Using legacy ostree bind mount for /
[    6.923741] imx-bus-devfreq 32700000.interconnect: failed to fetch clk: -2
[    6.956237] fsl-aud2htx 30cb0000.aud2htx: failed to pcm register
[    6.977555] fsl-aud2htx 30cb0000.aud2htx: failed to pcm register
[    7.016264] fsl-aud2htx 30cb0000.aud2htx: failed to pcm register
[    7.042416] fsl-aud2htx 30cb0000.aud2htx: failed to pcm register
[    7.060736] fsl-aud2htx 30cb0000.aud2htx: failed to pcm register
[    9.376727] tpm tpm0: A TPM error (256) occurred attempting the self test

Torizon OS 7.5.0-devel-20260121131151+build.0 verdin-imx8mp-15603379 ttymxc2

I see fsl-aud2htx 30cb0000.aud2htx: failed to pcm registert, imx-bus-devfreq 32700000.interconnect: failed to fetch clk: -2 and tpm tpm0: A TPM error (256) occurred attempting the self test.

Can I ignore these messages or do I need to resolve them? If I need to resolve them, what should I do?

Thanks.

Fabio

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

Hello Fabio,

Based on your system information, you’re running Torizon OS 7.5.0-devel on a Verdin iMX8M Plus with Mallow Carrier Board. The kernel messages you’re seeing are common and can be categorized as follows:

Message Analysis

1. imx-bus-devfreq 32700000.interconnect: failed to fetch clk: -2

This message indicates the interconnect driver failed to fetch a clock reference. This is typically harmless and doesn’t affect system functionality. The error code -2 usually means the clock isn’t available or properly configured in the device tree, but the system continues to operate normally.

2. fsl-aud2htx 30cb0000.aud2htx: failed to pcm register

These messages relate to the audio subsystem (AUD2HTX - Audio to HDMI TX). Since you’re using the Mallow Carrier Board, which doesn’t have HDMI output capabilities, this audio component isn’t needed. The driver attempts to register but fails because the hardware path isn’t complete on this carrier board configuration.

3. tpm tpm0: A TPM error (256) occurred attempting the self test

This message indicates the TPM (Trusted Platform Module) self-test failed. The Verdin iMX8M Plus includes TPM functionality for security features (1). However, if you’re not using security features like Secure Boot or encrypted storage, this error won’t impact normal system operation.

Recommendations

You can generally ignore these messages if:

  • Your system boots successfully and reaches the login prompt
  • Your applications function correctly
  • You don’t require audio over HDMI functionality
  • You’re not implementing security features that depend on TPM

Consider addressing them if:

  • You plan to use Secure Boot features (2)
  • You need TPM-based security functionality
  • The messages concern you from a system health perspective

Resolution Options

If you want to clean up these messages, you could create custom device tree overlays to disable unused peripherals, but this is typically unnecessary for normal operation.

The system appears to be functioning correctly based on your boot log reaching the login prompt successfully.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

3

Greetings @fmolon,

Yes those messages you see are all normal and you should be able to ignore them safely.

Best Regards,
Jeremias

1 Like
4

Hi @jeremias.tx,

thanks for your help.

Best regards

Fabio

5

Glad we were able to help clarify.

Best Regards,
Jeremias