On Mon, Jan 27, 2020 at 12:16 PM William Durocher <[email protected]> wrote: > > We have a build using warrior it boots up well but has a very long boot time > of around 95 sec. Using systemd-analyze I notice that we the boot takes a > long time before getting to multi-user.target. As can be seen for the > critical chain analysis below, there is a 60s gap after we get our console on > ttyO0. > > multi-user.target @1min 33.351s > └─getty.target @1min 33.298s > └─[email protected] @34.432s > └─basic.target @31.841s > └─sockets.target @31.804s > └─sshd.socket @31.532s +238ms > └─sysinit.target @31.183s > └─sys-kernel-config.mount @59.350s +962ms > └─systemd-journald.socket @2.553s > └─system.slice @2.027s > └─-.slice @2.028s > > > Looking at the logs I can see that the cause is most likely that ttyS0 is > trying to come up. > > Jan 27 01:07:14 rc8000-5e2b systemd[1]: dev-ttyS0.device: Job > dev-ttyS0.device/start > timed out. > Jan 27 01:07:14 rc8000-5e2b systemd[1]: Timed out waiting for device > /dev/ttyS0. > Jan 27 01:07:14 rc8000-5e2b systemd[1]: Dependency failed for Serial Getty on > ttyS0. > Jan 27 01:07:14 rc8000-5e2b systemd[1]: [email protected]: Job > serial-getty > @ttyS0.service/start failed with result 'dependency'. > Jan 27 01:07:14 rc8000-5e2b systemd[1]: dev-ttyS0.device: Job > dev-ttyS0.device/start > failed with result 'timeout'. > Jan 27 01:07:14 rc8000-5e2b systemd[1]: dev-ttyS0.device: Job > dev-ttyS0.device/start > timed out. > Jan 27 01:07:14 rc8000-5e2b systemd[1]: Timed out waiting for device > /dev/ttyS0. > Jan 27 01:07:14 rc8000-5e2b systemd[1]: Dependency failed for Serial Getty on > ttyS0. > Jan 27 01:07:14 rc8000-5e2b systemd[1]: [email protected]: Job > serial-getty > @ttyS0.service/start failed with result 'dependency'. > Jan 27 01:07:14 rc8000-5e2b systemd[1]: dev-ttyS0.device: Job > dev-ttyS0.device/start > failed with result 'timeout'. > Jan 27 01:07:15 rc8000-5e2b systemd[1]: dev-ttyS0.device: Job > dev-ttyS0.device/start > timed out. > Jan 27 01:07:15 rc8000-5e2b systemd[1]: Timed out waiting for device > /dev/ttyS0. > Jan 27 01:07:15 rc8000-5e2b systemd[1]: Dependency failed for Serial Getty on > ttyS0. > Jan 27 01:07:15 rc8000-5e2b systemd[1]: [email protected]: Job > serial-getty > @ttyS0.service/start failed with result 'dependency'. > Jan 27 01:07:15 rc8000-5e2b systemd[1]: dev-ttyS0.device: Job > dev-ttyS0.device/start > failed with result 'timeout'. > Jan 27 01:07:15 rc8000-5e2b systemd[1]: dev-ttyS0.device: Job > dev-ttyS0.device/start > timed out. > Jan 27 01:07:15 rc8000-5e2b systemd[1]: Timed out waiting for device > /dev/ttyS0. > Jan 27 01:07:15 rc8000-5e2b systemd[1]: Dependency failed for Serial Getty on > ttyS0. > Jan 27 01:07:15 rc8000-5e2b systemd[1]: [email protected]: Job > serial-getty > @ttyS0.service/start failed with result 'dependency'. > Jan 27 01:07:15 rc8000-5e2b systemd[1]: >
what is SERIAL_CONSOLES variable set to ? this should be machine setting. > > We are not using ttyS0 for the console or anything. In our distro config and > layer we refer instead to ttyO0. > > Looking through the environment of the build with "bitbake -e our-image" I > see that we had > > # $KERNEL_CONSOLE > # set? > /home/wdurocher/work/gammaip/warrior/sources/meta/meta/conf/distro/include/default-distrovars.inc:4 > # "ttyS0" > KERNEL_CONSOLE="ttyS0" > > I modifed our distro configuration setting KERNEL_MODULE to ttyO0 > > KERNEL_CONSOLE="ttyO0" > > and now bitbake -e gives me: > > # $KERNEL_CONSOLE [2 operations] > # set > /home/wdurocher/work/gammaip/warrior/sources/meta-gammaip/conf/distro/gammaip.conf:18 > # "ttyO0" > # set? > /home/wdurocher/work/gammaip/warrior/sources/meta/meta/conf/distro/include/default-distrovars.inc:4 > # "ttyS0" > # pre-expansion value: > # "ttyO0" > KERNEL_CONSOLE="ttyO0" > > But loading this image, the logs still shows the timeout waiting for ttyS0. > What else could be making Linux try to configure ttyS0 ? > > Note that I saw in my search that kernel CONFIG_FHANDLE should be set and it > was already so. > > Thanking you for any help on this, > > William Durocher >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#48165): https://lists.yoctoproject.org/g/yocto/message/48165 Mute This Topic: https://lists.yoctoproject.org/mt/70165095/21656 Mute #yocto: https://lists.yoctoproject.org/mk?hashtag=yocto&subid=6691583 Mute #systemd: https://lists.yoctoproject.org/mk?hashtag=systemd&subid=6691583 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
