<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 10, 2017 at 7:32 AM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mon, 2017-12-04 at 10:39 -0500, Bruce Ashfield wrote:<br>
> Here is the latest set of kernel updates and bug fixes to the kernel-<br>
> yocto<br>
> build.<br>
><br>
> The 4.9 and 4.12 updates are routine -stable updates. I realize we<br>
> are<br>
> still fighting some boot/hang issues with 4.12, but I didn't see any<br>
> new issues with the 4.12 updates, so I included them in this pull<br>
> request.<br>
><br>
> I've also included Saul's in-tree defconfig fixes + one additional<br>
> patch<br>
> of my own.<br>
><br>
> I also bump linux-yocto-dev to 4.15-rcX, which brought in some build<br>
> issues due to x86 ORC_UNWINDER changes, and ssl cert generation. I've<br>
> added the new dependencies directly in the linux-yocto-dev recipe,<br>
> but<br>
> they will very likely have to move lower into the stack over time.<br>
><br>
> I have some additional, structural changes that are coming shortly,<br>
> but I'm traveling for the next 5 days and will send them when I<br>
> return.<br>
<br>
</span>I tried this series, minus the -dev kernel change in -next and we see:<br>
<br>
<a href="https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/676/steps/Running%20oe-selftest/logs/stdio" rel="noreferrer" target="_blank">https://autobuilder.yocto.io/<wbr>builders/nightly-oe-selftest/<wbr>builds/676/steps/Running%20oe-<wbr>selftest/logs/stdio</a><br>
<br>
The duplicate logging bug makes it hard to read but the key takeaway is:<br>
<br>
2017-12-09 10:49:53,667 - oe-selftest - INFO - Ran 317 tests in 14099.939s<br>
2017-12-09 10:49:53,667 - oe-selftest - INFO - (failures=16, skipped=1)<br>
<br>
I can reproduce easily with:<br>
<br>
oe-selftest -r runqemu.RunqemuTests.test_<wbr>boot_deploy<br>
<br>
which fails locally too. If I revert "linux-yocto/4.12: update to<br>
v4.12.16" it works.<br>
<br>
The test checks if it can login over the serial port so I'm guessing<br>
some serial driver either got turned off or regressed?<br></blockquote><div><br></div><div>I can try the same thing here, but obviously I never send the series if I can't</div><div>boot and log into the qemu instances .. and I only ever use serial for that.</div><div><br></div><div>Hopefully I get the same error so I can debug locally.</div><div><br></div><div>Bruce</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Cheers,<br>
<br>
Richard<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
--<br>
______________________________<wbr>_________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.<wbr>openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/<wbr>mailman/listinfo/openembedded-<wbr>core</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"</div>
</div></div>