R31.1 warnings/failures

I have installed R31.1 with JetPack4.1.1 and noticed some unexpected things, at least to my knowledge.

  1. Firewall
[   10.437264] systemd[1]: Set hostname to <jetson-xxxxxxxxxxxxxx>.
[   10.506246] systemd[1]: File /lib/systemd/system/systemd-journald.service:36 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
[   10.509859] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)

May someone shed some light about what this implies ?

  1. bmi160 and nvs
[   11.655194] android_work: did not send uevent (0 0           (null))
[   11.679718] bmi160 8-0069: nvs_vregs_init vdd err=-19
[   11.681417] bmi160 8-0069: nvs_vregs_init vdd_IO err=-19
[   11.737489] tegra-i2c 31e0000.i2c: no acknowledge from address 0x69
[   11.740024] bmi160 8-0069: bmi_i2c_rd ERR: 0x00
[   11.741495] bmi160 8-0069: bmi_init _id_i2c ERR
[   11.742803] bmi160 8-0069: bmi_pm pm_en=0  ERR=-22
[   11.744095] bmi160 8-0069: bmi_remove
[   11.744098] bmi160 8-0069: bmi_probe done

I do see related (unused) modules:

    Module                  Size  Used by
    fuse                  103334  3
    bnep                   16619  2
    nvs_bmi160             22076  0
    nvs                    53924  1 nvs_bmi160
    bluedroid_pm           14104  0
    ip_tables              18922  0
    x_tables               29079  1 ip_tables

The device tree indeed seems to mention a device on I2C bus 8 at address 69, looking at /proc/device-tree/i2c@31e0000, but no device answers at this address.
This has been dirty fixed by bzip2ing both kernel modules: /lib/modules/4.9.108-tegra/kernel/drivers/misc/nvs/nvs.ko and /lib/modules/4.9.108-tegra/kernel/drivers/iio/imu/nvs_bmi/nvs_bmi160.ko.

  1. However systemctl still gives:
systemctl --failed
  UNIT                         LOAD   ACTIVE SUB    DESCRIPTION
● systemd-modules-load.service loaded failed failed Load Kernel Modules

Any idea why ? May a cleaner way to fix point 2 fix this ?

  1. I have also updated with apt and faced the Ubuntu missing toolbars after reboot, this has been fixed by clearing compiz cache as usual:
sudo rm -rf .cache/compizconfig-1/

(No answer expected here)

sha1sums are all ok in /etc/nv_tegra_release.
Thanks for sharing.

Some notes:

  • I did not see these on R31.0.1, but I do see them on R31.1.
  • The bmi module seems to be left over for some Bosch automobile part and is probably just left enabled by accident after work on an automobile. An error would be expected since the part doesn't exist on Xavier itself.
  • No firewall function is enabled by default. People should change passwords for "ubuntu" and "nvidia" right away if the Xavier is to touch an outside network.
  • Firewall function is standard Ubuntu 18.04 on Xavier, so people interested in firewalls can consult Ubuntu documentation.

I added a separate thread for mention of an xusb firmware error message:

Try to modify the status to disable in DT like below.

    i2c@31e0000 {
            pinctrl-names = "default";
            pinctrl-0 = <&dpaux_default>;
            bmi160@69 {
                    compatible = "bmi,bmi160";
                    reg = <0x69>;
                    accelerometer_matrix    = [01 00 00 00 01 00 00 00 01];
                    gyroscope_matrix        = [01 00 00 00 01 00 00 00 01];
                    status = "disable";

The systemd messages aren’t related to network firewalling, they indicate that there are missing kernel configuration options. From systemd’s README:

Required for IPAddressDeny= and IPAddressAllow= in resource control unit settings

Rebuilding the kernel with this config option set (CONFIG_BPF_SYSCALL will also be needed) should make the systemd warnings go away.

Except it doesn’t, because systemd also requires a BPF feature that wasn’t added until Linux 4.11, and we’re still at 4.9. So you we just have to live with the warnings.