]> code.ossystems Code Review - openembedded-core.git/commit
systemd: Increase devices timeout in QEMU machines to avoid failures on serial-getty
authorAníbal Limón <anibal.limon@linux.intel.com>
Fri, 28 Aug 2015 16:15:01 +0000 (11:15 -0500)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Sat, 29 Aug 2015 12:39:05 +0000 (13:39 +0100)
commit5196d7bacaef1076c361adaa2867be31759c1b52
treecf8f97398f2ca36fe0729ee0335651e22d2dc884
parent0eda7b4d889b926ab97d60fcbb1c0d12d730f8ea
systemd: Increase devices timeout in QEMU machines to avoid failures on serial-getty

Systemd serial-getty is failing because dev-tty ends with timeout, systemd
uses a default timeout of 90 secs that it's reached on AB's production environment
due to high I/O loads (nfs).

When use QEMU is used without KVM support, the machine code is executed by TCG
(software code execution) that is dependent on devices layer and causes locks
 between TCG/Devices increasing the machine code execution time [1].

QEMU don't support configuration of device timeout always uses a default one that is
90 secs, so the next patch increases the device timeout to 240 secs [2] in order give
enough time to get devices ready. It ONLY applies on QEMU machines.

[YOCTO #8141]

[1] http://blog.vmsplice.net/2011/03/qemu-internals-overall-architecture-and.html
[2] https://bugzilla.yoctoproject.org/show_bug.cgi?id=8141#c10

Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/recipes-core/systemd/systemd/qemuall_io_latency-core-device.c-Change-the-default-device-timeout-to-2.patch [new file with mode: 0644]
meta/recipes-core/systemd/systemd_219.bb