[FAILED] on boot screen

I have noticed some [FAILED] marks on the boot screen of my Xavier.

  1. Failed to start Load Kernel Modules
nvidia@xavier:~$ sudo systemctl status systemd-modules-load.service
[sudo] password for nvidia:
● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2018-12-14 18:54:41 JST; 11min ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 2326 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
 Main PID: 2326 (code=exited, status=1/FAILURE)
  1. Failed to start Process error reports when automatic reporting is enabled.
nvidia@xavier:~$ sudo systemctl status apport-autoreport.service
● apport-autoreport.service - Process error reports when automatic reporting is enabled
   Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2018-12-14 18:54:47 JST; 12min ago
  Process: 4673 ExecStart=/usr/share/apport/whoopsie-upload-all (code=exited, status=1/FAILURE)
 Main PID: 4673 (code=exited, status=1/FAILURE)

Dec 14 18:54:42 xavier.local systemd[1]: Starting Process error reports when automatic reporting is enabled...
Dec 14 18:54:43 xavier.local whoopsie-upload-all[4673]: ERROR: whoopsie is not running
Dec 14 18:54:47 xavier.local systemd[1]: apport-autoreport.service: Main process exited, code=exited, status=1/FAILURE
Dec 14 18:54:47 xavier.local systemd[1]: apport-autoreport.service: Failed with result 'exit-code'.
Dec 14 18:54:47 xavier.local systemd[1]: Failed to start Process error reports when automatic reporting is enabled.

I also have some errors in dmesg

...
[    0.985123] tegra_debug_uart_syscore_init: stdout-path property missing
...
[    1.819441] tegradc 15200000.nvdisplay: hdmi: tegra_hdmi_tmds_range_read(bd) failed
...
[    8.201121] tegra-xusb 3610000.xhci: Direct firmware load for tegra19x_xusb_firmware failed with error -2
[    8.201123] tegra-xusb 3610000.xhci: Falling back to user helper
...
[    8.227863] tegra186-cam-rtcpu bc00000.rtcpu: IOVM setup error: 130
[    8.227868] tegra186-cam-rtcpu bc00000.rtcpu: RTCPU coverage: IOVM setup error : 4294967291
...
[    8.997233] cgroup: cgroup2: unknown option "nsdelegate"
...
[   10.135573] bmi160 8-0069: nvs_vregs_init vdd err=-19
[   10.135808] tegra-xusb 3610000.xhci: cannot find firmware....retry after 1 second
[   10.138755] bmi160 8-0069: nvs_vregs_init vdd_IO err=-19
[   10.194539] tegra-i2c 31e0000.i2c: no acknowledge from address 0x69
[   10.197979] bmi160 8-0069: bmi_i2c_rd ERR: 0x00
[   10.200992] bmi160 8-0069: bmi_init _id_i2c ERR
[   10.205326] bmi160 8-0069: bmi_pm pm_en=0  ERR=-22
[   10.208770] bmi160 8-0069: bmi_remove
[   10.208774] bmi160 8-0069: bmi_probe done
...

Hi,

Could you see any module by command “lsmod”?

nvidia@xavier:~$ lsmod
Module                  Size  Used by
bnep                   16619  2
fuse                  103334  5
nvs_bmi160             22076  0
nvs                    53924  1 nvs_bmi160
bluedroid_pm           14104  0
ip_tables              18922  0
x_tables               29079  1 ip_tables

Those kernel errors are all non-fatal. I can see them on my device too.
Do you notice any other errors after boot up?

Hi,

Chromium browser has been crashing, but after I reinstalled it, it works fine so far.

In var/log/syslog I have lots of errors like this:

Dec 17 16:57:55 xavier gnome-software-service.desktop[27429]: Error: Can't initialize nvrm channel
Dec 17 16:58:02 xavier gnome-software-service.desktop[27429]: message repeated 529 times: [ Error: Can't initialize nvrm channel]

and this:

Dec 17 17:00:42 xavier gnome-software-service.desktop[27429]: [3210:3245:1217/170042.315190:ERROR:zygote_host_impl_linux.cc(259)] Failed to adjust OOM score of renderer with pid 4099: Permission denied (13)