On Mon, Jan 04, 2016 at 03:22:48PM +0000, Zbigniew Jędrzejewski-Szmek wrote: > Jan 04 15:50:12 OpenELEC systemd[1]: Started Apply Kernel Variables. > Jan 04 15:51:37 OpenELEC systemd[1]: Job dev-mmcblk0p1.device/start timed out. > Jan 04 15:51:37 OpenELEC systemd[1]: Timed out waiting for device > dev-mmcblk0p1.device. > Jan 04 15:51:37 OpenELEC systemd[1]: Dependency failed for sdcard mount > script. > Jan 04 15:51:37 OpenELEC systemd[1]: Job > storage-.kodi-.local-storage-sdcard.mount/start failed with result > 'dependency'. > Jan 04 15:51:37 OpenELEC systemd[1]: Job dev-mmcblk0p1.device/start failed > with result 'timeout'. > > So you need to figure out why the device does not appear in the alloted time. > Does it need more than 1.5 minutes to initialize? Are some modules only > loaded later on or something else prevents the detection from hapenning?
I've seen it happen when our old friend CONFIG_FHANDLE hasn't been turned on. I think it's still not turned on by default for ARM systems, and the kernel and systemd version looks old enough that it doesn't support the /proc/self/fdinfo way. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
