From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH 0/1] enable-fsck: Run after udev devices coldplugged
Date: Fri, 18 Feb 2022 06:37:44 +0100 [thread overview]
Message-ID: <20220218053745.31243-1-ubely@ilbers.de> (raw)
Earlier patch removing `update-initramfs` call from enable-fsck script
(`enable-fsck: don't run update-initramfs after fstab modification`)
discovered a bug that happens in arm/arm64 qemu targets.
Without running `update-initramfs`, this one-time service is executed
now very quickly and it creates terms when systemd can't find `ttyAMA0`
device and is unable to run serial getty on it.
Failed log:
| [ TIME ] Timed out waiting for device /dev/ttyAMA0.
| [DEPEND] Dependency failed for Serial Getty on ttyAMA0.
Normal (expected) log:
| [ OK ] Found device /dev/ttyAMA0.
| [ OK ] Started Serial Getty on ttyAMA0.
There is no direct relation between device handling and `enable-fsck`,
but enabling this "fast" service, due its "After" and "Before" service
dependencies leads to this device issue.
There are 3 possible situations:
1. `enable-fsck` is disabled:
- Boot is OK in this case
2. `enable-fsck` is enabled and executed fast (only fstab modified):
- Boot fails, device `/dev/ttyAMA0` is not found by systemd
3. `enable-fsck` is enabled and executed slow (can be simply achieved
by adding "sleep 10" to `/usr/share/enable-fsck/enable-fsck.sh`:
- Boot is OK in this case
Case 3 earlier was the main case, while "update-initramfs" was that
slow operation that was "fixing" the issue.
The problem looks like some race in services. It is probably related
to Debian and/or Qemu.
The patch below is a workaround that adds some udev dependency to the
`enable-fsck` service, so it now runs after udev devices coldplugged.
Uladzimir Bely (1):
enable-fsck: Run after udev devices coldplugged
meta/recipes-support/enable-fsck/files/enable-fsck.service | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.20.1
next 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 Uladzimir Bely [this message]
2022-02-18 5:37 ` [PATCH 1/1] " Uladzimir Bely
2022-02-25 6:12 ` [PATCH 0/1] " 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-1-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