Bug 12034

Summary: backtrace in dmesg on qemuppc with 4.9
Product: [QA/Testing] Runtime Testing Reporter: Todor Minchev <todor.minchev>
Component: generalAssignee: Bruce Ashfield <bruce.ashfield>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: Medium+ CC: akuster, richard.purdie, sgw, tracy.graydon
Version: 2.4   
Target Milestone: 2.5 M2   
Hardware: x86   
OS: Multiple   
See Also: https://bugzilla.yoctoproject.org/show_bug.cgi?id=12183
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12209
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
qemuppc dmesg none

Description Todor Minchev 2017-09-01 17:41:09 UTC
https://autobuilder.yocto.io/builders/nightly-ppc-lsb/builds/453/steps/Running%20Sanity%20Tests/logs/stdio

AssertionError: 255 != 0 : dnf --repofrompath=oe-testimage-repo-noarch,http://192.168.7.7:38458/noarch --repofrompath=oe-testimage-repo-qemuppc,http://192.168.7.7:38458/qemuppc --repofrompath=oe-testimage-repo-ppc7400,http://192.168.7.7:38458/ppc7400 --nogpgcheck install -y http://192.168.7.7:38458/noarch/run-postinsts-dev-1.0-r9.0.noarch.rpm
Comment 1 Armin Kuster 2017-09-07 14:53:38 UTC
pyro has 4.9 too so may need fix there too
Comment 2 Richard Purdie 2017-09-07 21:44:19 UTC
Created attachment 3992 [details]
qemuppc dmesg

There was a backtrace from dmesg which I mentioned to Bruce via email. I've attached that log
Comment 3 Richard Purdie 2017-09-07 21:47:22 UTC
*** Bug 12052 has been marked as a duplicate of this bug. ***
Comment 4 Richard Purdie 2017-09-07 21:47:58 UTC
Looks like we've seen this on two different autobuilders, both with the 4.9 kernel (lsb image)...
Comment 5 Richard Purdie 2017-09-12 12:04:52 UTC
Another failure : https://autobuilder.yocto.io/builders/nightly-ppc-lsb/builds/475
Comment 6 Saul Wold 2017-10-12 14:43:35 UTC
There are additional failures with qemuppc with bug #12183 and bug #12209
Comment 7 Richard Purdie 2018-03-01 16:14:03 UTC
We're going to assume this is fixed as:
* master doesn't have 4.9
* rocko updated to a new 4.9 stable version which may have fixed it.

We can reopen this if we see it again with rocko.