Re: [Xen-devel] [xen-unstable test] 127573: regressions - trouble: broken/fail/pass

[Roger Pau Monné <roger.pau@xxxxxxxxxx>]

On Fri, Sep 14, 2018 at 06:20:40AM +0000, osstest service owner wrote:
> flight 127573 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/127573/
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-i386-migrupgrade     <job status>                 broken
>  test-amd64-amd64-xl-qemuu-dmrestrict-amd64-dmrestrict    <job status>   
> broken
>  test-amd64-i386-qemuu-rhel6hvm-amd    <job status>                 broken
>  test-amd64-amd64-xl-qemuu-debianhvm-amd64-shadow    <job status>        
> broken
>  test-amd64-amd64-xl-qemuu-dmrestrict-amd64-dmrestrict 4 host-install(4) 
> broken REGR. vs. 127541
>  test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm <job status> broken in 
> 127557
>  test-xtf-amd64-amd64-3          <job status>                 broken  in 
> 127557
>  test-amd64-amd64-xl-multivcpu  7 xen-boot                fail REGR. vs. 
> 127541
>  test-amd64-i386-xl-xsm        7 xen-boot                 fail REGR. vs. 
> 127541
>  test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm  7 xen-boot fail REGR. vs. 
> 127541
>  test-amd64-amd64-pygrub       7 xen-boot                 fail REGR. vs. 
> 127541
>  test-amd64-amd64-i386-pvgrub  7 xen-boot                 fail REGR. vs. 
> 127541
>  test-xtf-amd64-amd64-5        7 xen-boot                 fail REGR. vs. 
> 127541
>  test-amd64-i386-qemut-rhel6hvm-intel  7 xen-boot         fail REGR. vs. 
> 127541
>  test-amd64-i386-xl-qemuu-ws16-amd64  7 xen-boot          fail REGR. vs. 
> 127541
>  test-amd64-i386-pair         10 xen-boot/src_host        fail REGR. vs. 
> 127541
>  test-amd64-i386-pair         11 xen-boot/dst_host        fail REGR. vs. 
> 127541
>  test-amd64-amd64-xl-qemuu-debianhvm-amd64-shadow 16 guest-localmigrate/x10 
> fail in 127557 REGR. vs. 127541

Those xen-boot failures are caused by my iommu series, which changes
the order of iommu setup and now the iommu is enabled before the
inclusive mappings are setup. This should lead to iommu faults, but on
some hardware this leads to freezes:

Sep 13 22:31:18.334573 (XEN) *** Building a PV Dom0 ***
Sep 13 22:31:18.334635 (XEN) ELF: phdr: paddr=0x1000000 memsz=0x10bc000
Sep 13 22:31:18.586625 (XEN) ELF: phdr: paddr=0x2200000 memsz=0x52a000
Sep 13 22:31:18.586711 (XEN) ELF: phdr: paddr=0x272a000 memsz=0x23018
Sep 13 22:31:18.598587 (XEN) ELF: phdr: paddr=0x274e000 memsz=0x205000
Sep 13 22:31:18.598667 (XEN) ELF: memory: 0x1000000 -> 0x2953000
Sep 13 22:31:18.598695 (XEN) ELF: note: GUEST_OS = "linux"
Sep 13 22:31:18.610579 (XEN) ELF: note: GUEST_VERSION = "2.6"
Sep 13 22:31:18.610639 (XEN) ELF: note: XEN_VERSION = "xen-3.0"
Sep 13 22:31:18.610666 (XEN) ELF: note: VIRT_BASE = 0xffffffff80000000
Sep 13 22:31:18.622584 (XEN) ELF: note: INIT_P2M = 0x8000000000
Sep 13 22:31:18.622615 (XEN) ELF: note: ENTRY = 0xffffffff8274e180
Sep 13 22:31:18.622642 (XEN) ELF: note: HYPERCALL_PAGE = 0xffffffff81001000
Sep 13 22:31:18.634555 (XEN) ELF: note: FEATURES = 
"!writable_page_tables|pae_pgdir_above_4gb"
Sep 13 22:31:18.634589 (XEN) ELF: note: SUPPORTED_FEATURES = 0x801
Sep 13 22:31:18.646567 (XEN) ELF: note: PAE_MODE = "yes"
Sep 13 22:31:18.646623 (XEN) ELF: note: LOADER = "generic"
Sep 13 22:31:18.646672 (XEN) ELF: note: unknown (0xd)
Sep 13 22:31:18.658578 (XEN) ELF: note: SUSPEND_CANCEL = 0x1
Sep 13 22:31:18.658614 (XEN) ELF: note: MOD_START_PFN = 0x1
Sep 13 22:31:18.658641 (XEN) ELF: note: HV_START_LOW = 0xffff800000000000
Sep 13 22:31:18.670589 (XEN) ELF: note: PADDR_OFFSET = 0
Sep 13 22:31:18.670645 (XEN) ELF: note: PHYS32_ENTRY = 0x1000360
Sep 13 22:31:18.670695 (XEN) ELF: Found PVH image
Sep 13 22:31:18.682602 (XEN) ELF: addresses:
Sep 13 22:31:18.682655 (XEN)     virt_base        = 0xffffffff80000000
Sep 13 22:31:18.682707 (XEN)     elf_paddr_offset = 0x0
Sep 13 22:31:18.682756 (XEN)     virt_offset      = 0xffffffff80000000
Sep 13 22:31:18.694609 (XEN)     virt_kstart      = 0xffffffff81000000
Sep 13 22:31:18.694673 (XEN)     virt_kend        = 0xffffffff82953000
Sep 13 22:31:18.706605 (XEN)     virt_entry       = 0xffffffff8274e180
Sep 13 22:31:18.706670 (XEN)     p2m_base         = 0x8000000000
Sep 13 22:31:18.706720 (XEN)  Xen  kernel: 64-bit, lsb, compat32
Sep 13 22:31:18.718550 (XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 
0x295300

Dario already reported this issue to me yesterday and I'm currently
working on a fix to restore the previous behavior and only enable the
iommu once inclusive mappings are setup.

Roger.

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