Kernel module "unknown symbol" after enabled - CONFIG_NET_DSA in A13

[skkandasamy1984]

I have enabled - CONFIG_NET_DSA in A13 and getting below errors. Board configuration is using - NXP i.MX8MM EVK board,

Kernel configuration file - imx8mm_gki.fragment

[ 11.503604][ T175] mii: Unknown symbol netif_carrier_on (err -22)
[ 11.509814][ T175] mii: disagrees about version of symbol netif_carrier_off

[ 11.553733][ T175] can_dev: disagrees about version of symbol kfree_skb_reason
[ 11.561152][ T175] can_dev: Unknown symbol kfree_skb_reason (err -22)

[ 13.558378][ T175] ppp_generic: disagrees about version of symbol skb_push
[ 13.565392][ T175] ppp_generic: Unknown symbol skb_push (err -22)

[skkandasamy1984]

Hi @JosephAtNXP ,

We have another problem. Box is booting fine, u-boot, kernel and android system. Box is rebooting, after reaching box uptime - 3 minutes. We unable to find root cause reason from logcat, serial logs for rebooting issue. 

Can you pls provide some suggestion for us?, We need support for this issue.

[JosephAtNXP]

Hi,

Thank you for your interest in NXP Semiconductor products,

We can associate this behavior to how are you performing the build process, check this link.

Could you confirm that you have this config?

CONFIG_BRIDGE=y 
CONFIG_HAVE_NET_DSA=y
CONFIG_NET_DSA=y

Regards

[skkandasamy1984]

Hi @JosephAtNXP ,

Thanks for your support.

Yes. After enabled below configuration, Issue is solved.

CONFIG_BRIDGE=y
CONFIG_HAVE_NET_DSA=y
CONFIG_NET_DSA=y

[skkandasamy1984]

Hi,  We have enabled - CONFIG_NET_DSA=m only in Kernel configuration file - imx8mm_gki.fragment.

GKI kernel version: ./system_dlkm/lib/modules/6.1.25-android14-11-gaa4fe52ab59e-ab10687853/kernel/drivers/net/

After build NXP A13 repo, Linux version 6.1.36-dirty

Getting below checksum mismatch for all net calls.

[   11.403297][  T177] Found checksum 5BB528FB vs module 560A9DDB

[   11.409303][  T177] mii: disagrees about version of symbol netif_carrier_on

[   11.416292][  T177] mii: Unknown symbol netif_carrier_on (err -22)

Can you pls help us for this kernel mismatch loading issue?.