VOXL2 vlan

jcai

Hello, has 8021q vlan been tested on the VOXL2 before? I'm building the module for 1.8.02 for SDK 1.4 by enabling CONFIG_VLAN_8021Q, but it's causing some issues.

Below is the output from lsmod before and after enabling the module:

voxl2:/$ lsmod
Module                  Size  Used by
voxl_platform_mod      16384  0
voxl_gpio_mod          16384  0
voxl_fsync_mod         16384  0
machine_dlkm          159744  0
wcd938x_slave_dlkm     16384  0
wcd938x_dlkm          110592  1 machine_dlkm
wcd9xxx_dlkm           49152  1 wcd938x_dlkm
mbhc_dlkm              45056  1 wcd938x_dlkm
tx_macro_dlkm         106496  0
rx_macro_dlkm         102400  0
va_macro_dlkm          98304  0
wsa_macro_dlkm         69632  1 machine_dlkm
swr_ctrl_dlkm          57344  4 wsa_macro_dlkm,tx_macro_dlkm,rx_macro_dlkm,va_macro_dlkm
bolero_cdc_dlkm        57344  5 machine_dlkm,wsa_macro_dlkm,tx_macro_dlkm,rx_macro_dlkm,va_macro_dlkm
wsa881x_dlkm           45056  1 machine_dlkm
wcd_core_dlkm          32768  7 wsa881x_dlkm,machine_dlkm,wsa_macro_dlkm,tx_macro_dlkm,rx_macro_dlkm,va_macro_dlkm,wcd938x_dlkm
stub_dlkm              16384  0
hdmi_dlkm              24576  0
swr_dlkm               24576  4 wsa881x_dlkm,wcd938x_dlkm,swr_ctrl_dlkm,wcd938x_slave_dlkm
pinctrl_lpi_dlkm       20480  0
pinctrl_wcd_dlkm       16384  0
usf_dlkm               57344  0
native_dlkm           163840  0
platform_dlkm        2195456  1 native_dlkm
q6_dlkm               909312  9 bolero_cdc_dlkm,machine_dlkm,pinctrl_lpi_dlkm,usf_dlkm,va_macro_dlkm,swr_ctrl_dlkm,wcd9xxx_dlkm,native_dlkm,platform_dlkm
adsp_loader_dlkm       16384  0
apr_dlkm              229376  4 q6_dlkm,usf_dlkm,adsp_loader_dlkm,platform_dlkm
snd_event_dlkm         16384  5 bolero_cdc_dlkm,machine_dlkm,q6_dlkm,pinctrl_lpi_dlkm,apr_dlkm
q6_notifier_dlkm       16384  3 q6_dlkm,pinctrl_lpi_dlkm,apr_dlkm
q6_pdr_dlkm            16384  1 q6_notifier_dlkm
88XXau               2342912  0
8821cu               2465792  0
8188eu               1200128  0

voxl2:/$ lsmod
Module                  Size  Used by
stub_dlkm              16384  0
q6_notifier_dlkm       16384  0
q6_pdr_dlkm            16384  1 q6_notifier_dlkm

The cause of this can be found using dmesg, where an example line is shown below. A multitude of other modules are showing similar errors with other symbols like _dev_err

[    4.764189] voxl_gpio_mod: disagrees about version of symbol device_create
[    4.764192] voxl_gpio_mod: Unknown symbol device_create (err -22)

However, running dmesg | grep VLAN gives:

voxl2:/$ dmesg | grep VLAN
[    1.954223] 8021q: 802.1Q VLAN Support v1.8
[    5.013433] 8021q: adding VLAN 0 to HW filter on device bond0

tom

@jcai Are you seeing any negative effects from this other than the errors in dmesg? It may not be an issue if not

jcai

@tom There's a couple, which I'm guessing have to do with all those modules not getting loaded anymore:

eth0 no longer shows up in ifconfig
voxl-configure-cameras returns cat: /sys/module/voxl_platform_mod/parameters/config: No such file or directory

There may be more, but I haven't dug too deep into finding all the effects

Alex Kushleyev

@jcai , you are probably modifying / building the kernel for an older SDK (while using newer SDK) or you have the kernel built for SDK 1.4.0 but actual installed SDK is older.

You can see which versions / tags of kernel and meta-voxl2 / meta-voxl2-bsp repos are used in each SDK here: https://docs.modalai.com/voxl2-voxl2-mini-system-image/

and follow instructions how to get the right tags as mentioned here : https://docs.modalai.com/voxl2-kernel-build-guide/#get-the-correct-tags

Please double check that the installed SDK matches the version of the kernel that you are customizing.

Alex

jcai

@Alex-Kushleyev To be sure, I cleaned the workspace and rebuilt the docker image as well. I re-synced, ensuring that the tag for the repos is v1.8.02. My voxl is also on SDK 1.4

Is this behaviour reproducible?

Alex Kushleyev

@jcai , hmm.. I will need to check with our Kernel guru :).

Will get back to you soon..

Alex

modaltb

Hey @jcai ,

Are you building a "debug" or "perf" kernel?

There's a little slop I have with voxl-gpio-mod and voxl-platform-mod.... they're being built out of tree and shipping in the rootfs... which if you load a debug kernel, causes problems like above....

By default the build is 'perf':
https://gitlab.com/voxl-public/system-image-build/qrb5165-kernel-build-docker/-/blob/qrb5165-ubun1.0-14.1a/bin/qrb5165-build.sh?ref_type=heads#L13

If you are using 'perf' and still having issues please let me know.

I want to move these two modules IN TREE, then this can go away... we're planning on doing this in future (major) release.

jcai

@modaltb As far as I can tell, I'm building a perf kernel. These are my changes:

MODAL_REPO_BRANCH=v1.8.02 in bin/qrb5165-common.sh

I've added the following lines to ./lu.um.1.2.1/apps_proc/poky/meta-voxl2-bsp/recipes-kernel/linux-msm/files/fragments/m005x.cfg:

CONFIG_MACVLAN=y
CONFIG_VLAN_8021Q=y

And then building:

./qrb5165-build.sh -m M0054