Extremely slow boot with latest TorizonCore build

Technical Support
, , ,
42

Hi @RoccoBr

I did verify that you can remove that service by overriding the existing rngd.service file. On your board, you can run systemctl edit --full rndg.service and then simply remove the line that reads Wants=systemd-udev-settle.service. Alternatively, you can just create the file /etc/systemd/system/rngd.service with the following contents:

[Unit]
Description=Hardware RNG Entropy Gatherer Daemon
DefaultDependencies=no
After=systemd-udev-settle.service
Before=sysinit.target shutdown.target
Conflicts=shutdown.target

[Service]
EnvironmentFile=-/etc/default/rng-tools
ExecStart=/usr/sbin/rngd -f $EXTRA_ARGS

[Install]
WantedBy=multi-user.target

You can use torizoncore-builder to add that to your images so you don’t need to manually do this on every device. See this link for more info.

We’ll continue investigating on our end but this should at least get you past this issue.

Drew

2 Likes
43

Hi @drew.tx
adding file /etc/systemd/system/rngd.service has fixed the issue: using latest TorizonCore v5.7 the device is now booting in 20 seconds.

I was having a look at all components on our custom carrier board that rely on udev and the major one is the modem that is managed by the ppp deamon. it usually comes up very late in the booting stage, it could be that with systemd-udev-settle.service enable, the kernel is waiting for udev to complete its initialization before proceeding further

if it can helps, I can provide our udev scripts and rules

Regards,
Rocco

44

Hello @RoccoBr ,

if it can helps, I can provide our udev scripts and rules

Yes, that would be very helpful :slight_smile:

Best regards,
Josep

45

hi @josep.tx ,
I have provided them privately to @drew.tx

Regards,
Rocco

46

I am fairly certain we determined the root cause here to be the additional dependency on the systemd-udev-settle.service right? @RoccoBr has a local modification removing that dependency and I am working with the openembedded community to have that removed upstream.

@RoccoBr can you confirm? If so we can mark this issue resolved I believe.

Drew

47

hi @drew.tx yes I can confirm it.

the rngd.service file you gave me has fixed the issue