Bug 10228 - Very frequent SSH connection failures during oe-selftest on qemuppc
Summary: Very frequent SSH connection failures during oe-selftest on qemuppc
Status: RESOLVED FIXED
Alias: None
Product: Runtime Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: High normal
Target Milestone: 2.2 M4
Assignee: Leonardo Sandoval Gonzalez
QA Contact: Yi Zhao
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-09-06 10:26 UTC by Joshua Lock
Modified: 2016-09-09 15:29 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joshua Lock 2016-09-06 10:26:37 UTC 
We're seeing several "Connection to 192.168.7.10 closed by remote host." during oe-selftest for qemuppc. Doesn't seem to matter what image (core-image-sato, core-image-lsb, etc) or distro (poky-lsb, poky).

http://autobuilder.yocto.io:8010/builders/nightly-ppc/builds/40/steps/Running%20Sanity%20Tests/logs/stdio

We're also observing timeouts during oe-selftest of qemuppc:

https://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds/929/steps/Running%20Sanity%20Tests/logs/stdio
Comment 2 Richard Purdie 2016-09-09 12:43:48 UTC 
Fixed by upgrading to qemu 2.7.0 which has ppc TCG fixes. The problem seemed to be disconnections from code in openssh on the guest, dropbear didn't seem to have the issue. http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=e6c48b1213848757c3d3806a1985756bd7d5f30d