Re: [Xen-devel] [qemu-upstream-4.11-testing test] 136184: regressions - FAIL

[Anthony PERARD <anthony.perard@xxxxxxxxxx>]

On Thu, May 16, 2019 at 10:38:54PM +0100, Julien Grall wrote:
> Hi Anthony,
> 
> Thank you for CCing me.
> 
> On 5/16/19 11:37 AM, Anthony PERARD wrote:
> > On Wed, May 15, 2019 at 07:48:17PM +0000, osstest service owner wrote:
> > > flight 136184 qemu-upstream-4.11-testing real [real]
> > > http://logs.test-lab.xenproject.org/osstest/logs/136184/
> > > 
> > > Regressions :-(
> > > 
> > > Tests which did not succeed and are blocking,
> > > including tests which could not be run:
> > >   build-arm64-pvops               <job status>                 broken  in 
> > > 134594
> > >   build-arm64                     <job status>                 broken  in 
> > > 134594
> > >   build-arm64-xsm                 <job status>                 broken  in 
> > > 134594
> > >   build-arm64-xsm            4 host-install(4) broken in 134594 REGR. vs. 
> > > 125575
> > >   build-arm64-pvops          4 host-install(4) broken in 134594 REGR. vs. 
> > > 125575
> > >   build-arm64                4 host-install(4) broken in 134594 REGR. vs. 
> > > 125575
> > >   test-arm64-arm64-libvirt-xsm  7 xen-boot                 fail REGR. vs. 
> > > 125575
> > >   test-arm64-arm64-xl           7 xen-boot                 fail REGR. vs. 
> > > 125575
> > >   test-arm64-arm64-xl-xsm       7 xen-boot                 fail REGR. vs. 
> > > 125575
> > >   test-arm64-arm64-xl-credit2   7 xen-boot                 fail REGR. vs. 
> > > 125575
> > > 
> > 
> > Ian, Julien,
> > 
> > I can't figure out why Xen consistently fails to boot on rochester* in
> > the qemu-upstream-4.11-testing flights. The xen-4.11-testing seems to
> > pass.
> > 
> > At boot, the boot loader seems to load blobs, but when it's time to Xen
> > to shine, there are no output from Xen on the serial.
> 
> The serial console is initializing fairly late in the process. Any useful
> message (such as memory setup or even part of the interrupts) will be hide
> out. For getting them, you need earlyprintk. Unfortunately they can't be
> configured at runtime today :(.

I think I managed to run the job with earlyprintk on rochester, but
Xen have booted:
http://logs.test-lab.xenproject.org/osstest/logs/136451/

So that probably wasn't very useful.

(I had to hack osstest in order to compile xen with early printk.)

-- 
Anthony PERARD

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel