diff options
author | Kevin Hao <kexin.hao@windriver.com> | 2019-06-06 15:11:47 +0800 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2019-06-07 09:11:48 +0100 |
commit | 720474ee8d83a403123d7b317f095d49a3ea3e0a (patch) | |
tree | 9d9dfd7ada55bb36e32663cb6d2dbb62a8a50f48 /meta/recipes-core/packagegroups | |
parent | e5f2684d60025fbe205d1974ba89341d1d5408be (diff) | |
download | poky-720474ee8d83a403123d7b317f095d49a3ea3e0a.tar.gz |
oeqa/utils/qemurunner: Set both the threadport&serverport with tcpserial parameter
After the commit ad522ea6a64e ("runqemu: Let qemuparams override default
settings"), the order of the two "-serial" parameters when running the
qemu have been switched. The effect of this is that the logging thread
will use ttyS1 (of course can't capture the kernel boot message anymore),
and the test command will run on the ttyS0. So the output of the test
command may be mangled by the kernel message (such as call trace), and
let the test command produce a fake timeout error message. We can't fix
it by just adjusting the order of the threadport and serverport, since
it will break some machines such as qemuarm64 which use the virtio
serial. So using the tcpserial to setup both the threadport and
serverport.
[YOCTO Bug 13309]
(From OE-Core rev: 9f2005dee41b1ef5a0d1f7b69bcd6c8352dac016)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-core/packagegroups')
0 files changed, 0 insertions, 0 deletions