From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH 1/1] enable-fsck: Run after udev devices coldplugged
Date: Fri, 18 Feb 2022 06:37:45 +0100 [thread overview]
Message-ID: <20220218053745.31243-2-ubely@ilbers.de> (raw)
In-Reply-To: <20220218053745.31243-1-ubely@ilbers.de>
This workarounds a problem when CI fails for arm/arm64 due to timeout on
finding ttyAMA0 device by systemd. So, serial getty fails to start.
This problem appears only if enable-fsck recipe is included to build. It
looks like its "After" and "Before" service dependencies somehow break
device appearing.
If enable-fsck service is delayed a bit (placed after device coldplug
finished) problem gets resolved. But it's actually looks like a
workaround for some issue specific to qemu/bullseye.
Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
---
meta/recipes-support/enable-fsck/files/enable-fsck.service | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-support/enable-fsck/files/enable-fsck.service b/meta/recipes-support/enable-fsck/files/enable-fsck.service
index 846497d1..8b33cdb9 100644
--- a/meta/recipes-support/enable-fsck/files/enable-fsck.service
+++ b/meta/recipes-support/enable-fsck/files/enable-fsck.service
@@ -7,7 +7,7 @@
Description=Enable fsck for mounted devices
DefaultDependencies=no
Conflicts=shutdown.target
-After=systemd-remount-fs.service
+After=systemd-remount-fs.service systemd-udev-trigger.service
Before=sysinit.target shutdown.target
ConditionPathIsReadWrite=/etc
--
2.20.1
next prev parent reply other threads:[~2022-02-18 5:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 5:37 [PATCH 0/1] " Uladzimir Bely
2022-02-18 5:37 ` Uladzimir Bely [this message]
2022-02-25 6:12 ` Anton Mikanovich
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=20220218053745.31243-2-ubely@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox