As I was attempting to modify my device tree file to enable two SPI devices (2 chip selects on one, 1 chip select on the other) I suddenly started experiencing problems during booting. I get the following errors on the console during booting:
[ OK ] Reached target Sound Card. [ 7.077614] random: nonblocking pool is initialized [ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. [ TIME ] Timed out waiting for device dev-ttymxc0.device. [DEPEND] Dependency failed for Serial Getty on ttymxc0. [FAILED] Failed to start Load Kernel Modules. See 'systemctl status systemd-modules-load.service' for details. Mounting Configuration File System...
The ‘systemctl’ command gives me the following:
● systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled) Active: failed (Result: timeout) since Wed 2019-02-06 18:29:25 UTC; 42min ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Main PID: 82 CGroup: /system.slice/systemd-modules-load.service └─82 /lib/systemd/systemd-modules-load Oct 05 02:34:39 colibri-vf systemd-modules-load: Inserted module 'libcomposite' Oct 05 02:34:39 colibri-vf systemd-modules-load: Inserted module 'imx_rpmsg_tty' Feb 06 18:26:24 colibri-vf systemd: systemd-modules-load.service: Start operation timed out. Terminating. Feb 06 18:27:55 colibri-vf systemd: systemd-modules-load.service: State 'stop-final-sigterm' timed out. Killing. Feb 06 18:29:25 colibri-vf systemd: systemd-modules-load.service: Processes still around after final SIGKILL. Entering failed mode. Feb 06 18:29:25 colibri-vf systemd: Failed to start Load Kernel Modules. Feb 06 18:29:25 colibri-vf systemd: systemd-modules-load.service: Unit entered failed state. Feb 06 18:29:25 colibri-vf systemd: systemd-modules-load.service: Failed with result 'timeout'. Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
At the time I get the error there is about a 4 1/2 minute delay waiting for some process or other before it times out. Thinking that this might be caused by my modified device tree file (unlikely, since all my SPI ports were working perfectly) I restored the original unmodified device tree file. That did not change the booting problem.
I could just re-flash my module with the linux console image and start over, but I would like to know what caused this problem. It would be better if I could just fix it and continue with my work. Note that I have not made any changes to the Linux kernel. I have only modified the device tree file.