Re: [OE-core] [PATCH v2 2/2] seatd: use readyfd2sd to get rid of systemd service startup races

["Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>]

On Wed Jul 15, 2026 at 12:13 PM CEST, Lucas Stach wrote:
> Currently systemd has no insight into the startup state of the seatd server
> process, so it might start dependant services too early, causing them to
> fail due to being unable to connect to seatd.
>
> Use the readyfd2sd adapter to convert the seatd s6 ready notification to
> systemd-notify and switch the service to the notify type to allow systemd
> to defer dependant service startup until seatd is ready to accept requests.
>
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> ---

Hi,

Thanks for the new version.

It looks like the systemd.SystemdBasicTests.test_systemd_failed test is
failing with this patch, strangely, only for images built without x11
support:

Traceback (most recent call last):
  File "/srv/pokybuild/yocto-worker/no-x11/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
    return func(*args, **kwargs)
  File "/srv/pokybuild/yocto-worker/no-x11/build/layers/openembedded-core/meta/lib/oeqa/runtime/cases/systemd.py", line 95, in test_systemd_failed
    self.assertTrue(settled, msg=msg)
    ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^
AssertionError: False is not true : Timed out waiting for systemd to settle:
starting
...
RESULTS - systemd.SystemdBasicTests.test_systemd_failed: FAILED (127.02s)
SUMMARY:
core-image-weston () - Ran 76 tests in 206.326s
core-image-weston - FAIL - Required tests failed (successes=42, skipped=33, failures=1, errors=0)
core-image-weston - FAILED - Last lines of QEMU boot logs:
--- qemu_boot_log.20260718112858 ---
[␛[0;32m  OK  ␛[0m] Started ␛[0;1;39mSSH Per-Connection Server (192.168.7.3:49632)␛[0m.

[␛[0;32m  OK  ␛[0m] Started ␛[0;1;39mSSH Per-Connection Server (192.168.7.3:49648)␛[0m.

[␛[0;32m  OK  ␛[0m] Started ␛[0;1;39mSSH Per-Connection Server (192.168.7.3:49658)␛[0m.

[␛[0;32m  OK  ␛[0m] Started ␛[0;1;39mSSH Per-Connection Server (192.168.7.3:49668)␛[0m.

[␛[0;32m  OK  ␛[0m] Started ␛[0;1;39mSSH Per-Connection Server (192.168.7.3:49684)␛[0m.

[␛[0;32m  OK  ␛[0m] Started ␛[0;1;39mSSH Per-Connection Server (192.168.7.3:49692)␛[0m.

[␛[0;32m  OK  ␛[0m] Started ␛[0;1;39mSSH Per-Connection Server (192.168.7.3:49706)␛[0m.

[␛[0;32m  OK  ␛[0m] Started ␛[0;1;39mSSH Per-Connection Server (192.168.7.3:49708)␛[0m.

[␛[0;32m  OK  ␛[0m] Started ␛[0;1;39mSSH Per-Connection Server (192.168.7.3:49724)␛[0m.

[␛[0;32m  OK  ␛[0m] Started ␛[0;1;39mSSH Per-Connection Server (192.168.7.3:49728)␛[0m.


--- qemu_boot_log.20260718112858.2 ---
␛[!p␛]104␛\␛[0m␛[?7h␛[1G␛[0J␛[6n
␛[6n␛[!p␛]104␛\␛[0m␛[?7h␛[1G␛[0J␛[6n
␛[6n␛]3008;start=403e36bd5a1c42bbb36601d3a29037c0;user=root;hostname=qemux86-64;machineid=8e279edcef204437b2cc30688f5a9895;bootid=7994f691f1d5422db4ac58bdaddd68dd;pid=246;pidfdid=247;comm=(agetty);servicename=serial-getty@ttyS1.service;invocationid=cefe0df5c3e34907826aff9044103155;type=service␛\␛P+q6E616D65␛\

https://autobuilder.yoctoproject.org/valkyrie/#/builders/25/builds/4157

If needed, the build configuration is here:
https://autobuilder.yoctoproject.org/valkyrie/api/v2/logs/7747007/raw_inline

Can you have a look at the issue?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com