These occur when running images under virtualisation on machines with high load which sometimes trigger timeouts in the kernel DMA code. They're harmless to ignore in these cases.
Adding this since "failing" the build due to this is more annoying thank useful. [YOCTO #7387] Signed-off-by: Richard Purdie <richard.pur...@linuxfoundation.org> diff --git a/meta/lib/oeqa/runtime/parselogs.py b/meta/lib/oeqa/runtime/parselogs.py index b1dcc1e..cf0f67c 100644 --- a/meta/lib/oeqa/runtime/parselogs.py +++ b/meta/lib/oeqa/runtime/parselogs.py @@ -22,7 +22,8 @@ common_errors = [ "Failed to load module modesetting", "Failed to load module \"glx\"", "Failed to load module glx", - "[drm] Cannot find any crtc or sizes - going 1024x768" + "[drm] Cannot find any crtc or sizes - going 1024x768", + "hd.: possibly failed opcode" ] x86_common = [ -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core