On 04/07/2015 10:14 AM, Ian Jackson wrote:
osstest service user writes ("[linux-next test] 50321: regressions - FAIL"):
flight 50321 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/50321/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
...
test-armhf-armhf-xl 5 xen-boot fail REGR. vs. 50276
...
test-amd64-i386-xl 5 xen-boot fail REGR. vs. 50276
linux-next was broken for 32-bit x86. The fix is in tip (commit
3f85483bd80, "x86/cpu: Factor out common CPU initialization code, fix
32-bit Xen PV guests") but it don't see it in next, meaning that it
should still be broken.
The bug was x86-specific so it wouldn't affect ARM.
There is another bug with clockevents, which is generic code and its
both in tip and next. The logs resemble what I see with his bug but it
should only happen on resume --- is this when the failure occurs?
I have a fix for it but I am waiting for tip to be merged into mainline
since I need new symbols that are new in tip.
-boris
It appears that linux-next cannot boot as dom0 on i386 (32-bit x86) or
armhf (32-bit ARM).
The bugs don't seem to be related.
http://logs.test-lab.xenproject.org/osstest/logs/50321/test-amd64-i386-xl/info.html
http://logs.test-lab.xenproject.org/osstest/logs/50321/test-amd64-i386-xl/serial-fiano1.log
(14:12:47 is when osstest timed out and started capturing logs,
sending debug keys, etc.)
http://logs.test-lab.xenproject.org/osstest/logs/50321/test-armhf-armhf-xl/info.html
http://logs.test-lab.xenproject.org/osstest/logs/50321/test-armhf-armhf-xl/serial-arndale-lakeside.log
(up to 13:17:35, likewise)
version targeted for testing:
linux b0a12fb5bc87820b12df22c64dd680a96443de00
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
