From: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
To: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
openembedded-core@lists.openembedded.org,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core] [PATCH v2] systemd: Upgrade 261.3 -> 262
Date: Wed, 30 Sep 2026 17:07:00 +0200 [thread overview]
Message-ID: <b98fe85a-e180-4e8c-b07e-e50d0d888bc4@est.tech> (raw)
In-Reply-To: <DLSFA2EWD42U.1UHXEHKQC0TMP@bootlin.com>
On 2026-09-30 08:04, Mathieu Dubois-Briand wrote:
> Thanks for the new version. It looks better, except for a test fail:
>
> Traceback (most recent call last):
> File "/srv/pokybuild/yocto-worker/qemux86-64-alt/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/qemux86-64-alt/build/layers/openembedded-core/meta/lib/oeqa/runtime/cases/systemd.py", line 100, in test_systemd_failed
> output += self.systemctl('status --full --failed')
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File "/srv/pokybuild/yocto-worker/qemux86-64-alt/build/layers/openembedded-core/meta/lib/oeqa/runtime/cases/systemd.py", line 26, in systemctl
> self.assertEqual(status, expected, message)
> AssertionError: 3 != 0 : SYSTEMD_BUS_TIMEOUT=240s systemctl status --full --failed
> x systemd-coredumpd.service - Listen Kernel Core Dump Socket
> Loaded: loaded (/usr/lib/systemd/system/systemd-coredumpd.service; enabled; preset: enabled)
> Active: failed (Result: start-limit-hit) since Tue 2026-09-29 15:04:12 UTC; 6s ago
> Invocation: 14d841285f64478290e42885757aee13
> Docs: man:systemd-coredump(8)
> Process: 841 ExecCondition=/usr/lib/systemd/systemd-coredump --check-requirements (code=exited, status=1/FAILURE)
> FD Store: 0 (limit: 512)
> Mem peak: 2.1M
> CPU: 43ms
>
> ...
> RESULTS - systemd.SystemdBasicTests.test_systemd_failed: FAILED (1.69s)
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/95/builds/4667
Hi Mathieu,
failure from the 262 upgrade related to kernel version.
I built both, systemd as init, and checked directly:
6.18.52:
# systemd-coredump --check-requirements; echo $?
ioctl(PIDFD_GET_INFO) does not support PIDFD_INFO_COREDUMP and/or
PIDFD_INFO_COREDUMP_SIGNAL.
1
-> coredumpd goes to failed (start-limit-hit), test_systemd_failed
fails
7.2.6:
# systemd-coredump --check-requirements; echo $?
0
-> coredumpd is active (running), test passes
But PIDFD_INFO_COREDUMP_SIGNAL is available from kernel version 6.19.
But below NEWS doesn't say anything about version requirements.
NEWS (https://github.com/systemd/systemd/blob/v262-stable/NEWS#L370) says
* systemd-coredump now supports the kernel coredump socket protocol
available since Linux 6.17. On supported kernels,
systemd-coredumpd.service listens on
/run/systemd/coredumpd/kernel,
and systemd-coredump-register.service registers the socket
through
kernel.core_pattern. Older kernels continue to use the
per-coredump
systemd-coredump@.service path. Changes to coredump.conf require
reloading systemd-coredumpd.service, and deployments that set a
custom kernel.core_pattern should stop and disable that service.
But looks like older kernel logic is not working as expected.
One solution is use ConditionKernelVersion and skip that test on
versions less than 6.19
https://www.freedesktop.org/software/systemd/man/latest/systemd.unit.html#ConditionKernelVersion=
Regards,
Jaipaul
next prev parent reply other threads:[~2026-09-30 15:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 11:39 [PATCH 0/3] systemd: Upgrade 261.3 -> 262 Jaipaul Cheernam
2026-09-28 11:39 ` [PATCH 1/3] " Jaipaul Cheernam
2026-09-29 6:31 ` [OE-core] " Mathieu Dubois-Briand
2026-09-29 6:35 ` Jaipaul Cheernam
2026-09-29 6:59 ` [PATCH v2] " Jaipaul Cheernam
2026-09-30 6:04 ` [OE-core] " Mathieu Dubois-Briand
2026-09-30 15:07 ` Jaipaul Cheernam [this message]
2026-10-01 7:50 ` [PATCH v3] " Jaipaul Cheernam
2026-10-06 7:34 ` Paul Barker
2026-10-06 19:37 ` [PATCH v4] " Jaipaul Cheernam
2026-09-28 11:39 ` [PATCH 2/3] systemd: Update HOMEPAGE Jaipaul Cheernam
2026-09-28 11:39 ` [PATCH 3/3] systemd: Update DESCRIPTION section Jaipaul Cheernam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b98fe85a-e180-4e8c-b07e-e50d0d888bc4@est.tech \
--to=jaipaul.cheernam@est.tech \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.