Hi, Sorry for the formatting.
On Tue, Feb 12, 2019 at 12:26 PM Ian Jackson <ian.jack...@citrix.com> wrote: > I don't have a good plan about what to do next. I guess one thing we > could do would be to ask Yogesh to reflash the firmware on laxton0 and > see if that helps. > > I think this issue is likely to be a protracted problem. Any helpful > suggestions from people with more experience of these particular boxes > would be very welcome... Looking at the first failure log [1], it seems we are trying to boot Linux 3.16. So the failure seems legit to me as I don't think 3.16 supports Seattle. Furthermore, previous successful Debian install were using a backport kernel (4.9). So I think we can rule out a firmware bug. Now, I am struggling to understand why osstest is suddenly using 3.16. Was there any change in osstest or the configuration? [1] http://logs.test-lab.xenproject.org/osstest/logs/132973/test-arm64-arm64-xl/serial-laxton0.log -- Julien Grall _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
