All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	Henry Wang <Henry.Wang@arm.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [xen-unstable test] 174809: regressions - trouble: broken/fail/pass
Date: Fri, 18 Nov 2022 15:39:53 +0100	[thread overview]
Message-ID: <Y3eZOcmOYkNLdeGe@Air-de-Roger> (raw)
In-Reply-To: <osstest-174809-mainreport@xen.org>

On Fri, Nov 18, 2022 at 10:21:52AM +0000, osstest service owner wrote:
> flight 174809 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/174809/
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-amd64-xl-qemuu-dmrestrict-amd64-dmrestrict    <job status>   broken
>  test-amd64-amd64-xl-qemuu-dmrestrict-amd64-dmrestrict 5 host-install(5) broken REGR. vs. 174797
>  test-amd64-amd64-xl-credit2  20 guest-localmigrate/x10   fail REGR. vs. 174797
>  test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 15 guest-saverestore fail REGR. vs. 174797
>  test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 15 guest-saverestore fail REGR. vs. 174797
>  test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 12 debian-hvm-install fail REGR. vs. 174797
>  test-amd64-i386-xl-qemut-debianhvm-i386-xsm 12 debian-hvm-install fail REGR. vs. 174797
>  test-amd64-amd64-xl-qemuu-debianhvm-i386-xsm 12 debian-hvm-install fail REGR. vs. 174797
>  test-amd64-i386-xl-qemuu-debianhvm-i386-xsm 12 debian-hvm-install fail REGR. vs. 174797
>  test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 12 debian-hvm-install fail REGR. vs. 174797
>  test-amd64-amd64-xl-qemut-debianhvm-i386-xsm 15 guest-saverestore fail REGR. vs. 174797

Looking at a random failure:

Nov 18 01:55:09.233941 (d1) Searching bootorder for: HALT
Nov 18 01:55:11.681666 (d1) drive 0x000f5890: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=20480000
Nov 18 01:55:11.693694 (d1) Space available for UMB: cb000-e9000, f52e0-f5820
Nov 18 01:55:11.693754 (d1) Returned 258048 bytes of ZoneHigh
Nov 18 01:55:11.705648 (d1) e820 map has 8 items:
Nov 18 01:55:11.705676 (d1)   0: 0000000000000000 - 000000000009fc00 = 1 RAM
Nov 18 01:55:11.705701 (d1)   1: 000000000009fc00 - 00000000000a0000 = 2 RESERVED
Nov 18 01:55:11.717716 (d1)   2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
Nov 18 01:55:11.717768 (d1)   3: 0000000000100000 - 00000000effff000 = 1 RAM
Nov 18 01:55:11.729687 (d1)   4: 00000000effff000 - 00000000f0000000 = 2 RESERVED
Nov 18 01:55:11.729745 (d1)   5: 00000000fc000000 - 00000000fc00b000 = 4 NVS
Nov 18 01:55:11.741693 (d1)   6: 00000000fc00b000 - 0000000100000000 = 2 RESERVED
Nov 18 01:55:11.741752 (d1)   7: 0000000100000000 - 0000000148000000 = 1 RAM
Nov 18 01:55:11.753644 (d1) enter handle_19:
Nov 18 01:55:11.753721 (d1)   NULL
Nov 18 01:55:11.753796 (d1) Booting from DVD/CD...
Nov 18 01:55:11.753864 (d1) Booting from 0000:7c00
Nov 18 01:55:11.753936 (XEN) arch/x86/mm/hap/hap.c:304: d1 failed to allocate from HAP pool
Nov 18 01:55:18.633799 (XEN) Failed to shatter gfn 7ed37: -12
Nov 18 01:55:18.633866 (XEN) d1v0 EPT violation 0x19c (--x/rw-) gpa 0x0000007ed373a1 mfn 0x33ed37 type 0
Nov 18 01:55:18.645790 (XEN) d1v0 Walking EPT tables for GFN 7ed37:
Nov 18 01:55:18.645850 (XEN) d1v0  epte 9c0000047eba3107
Nov 18 01:55:18.645893 (XEN) d1v0  epte 9c000003000003f3
Nov 18 01:55:18.645935 (XEN) d1v0  --- GLA 0x7ed373a1
Nov 18 01:55:18.657783 (XEN) domain_crash called from arch/x86/hvm/vmx/vmx.c:3758
Nov 18 01:55:18.657844 (XEN) Domain 1 (vcpu#0) crashed on cpu#8:
Nov 18 01:55:18.669781 (XEN) ----[ Xen-4.17-rc  x86_64  debug=y  Not tainted ]----
Nov 18 01:55:18.669843 (XEN) CPU:    8
Nov 18 01:55:18.669884 (XEN) RIP:    0020:[<000000007ed373a1>]
Nov 18 01:55:18.681711 (XEN) RFLAGS: 0000000000010002   CONTEXT: hvm guest (d1v0)
Nov 18 01:55:18.681772 (XEN) rax: 000000007ed373a1   rbx: 000000007ed3726c   rcx: 0000000000000000
Nov 18 01:55:18.693713 (XEN) rdx: 000000007ed2e610   rsi: 0000000000008e38   rdi: 000000007ed37448
Nov 18 01:55:18.693775 (XEN) rbp: 0000000001b410a0   rsp: 0000000000320880   r8:  0000000000000000
Nov 18 01:55:18.705725 (XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 0000000000000000
Nov 18 01:55:18.717733 (XEN) r12: 0000000000000000   r13: 0000000000000000   r14: 0000000000000000
Nov 18 01:55:18.717794 (XEN) r15: 0000000000000000   cr0: 0000000000000011   cr4: 0000000000000000
Nov 18 01:55:18.729713 (XEN) cr3: 0000000000400000   cr2: 0000000000000000
Nov 18 01:55:18.729771 (XEN) fsb: 0000000000000000   gsb: 0000000000000000   gss: 0000000000000002
Nov 18 01:55:18.741711 (XEN) ds: 0028   es: 0028   fs: 0000   gs: 0000   ss: 0028   cs: 0020

It seems to be related to the paging pool adding Andrew and Henry so
that he is aware.

Roger.


  reply	other threads:[~2022-11-18 14:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 10:21 [xen-unstable test] 174809: regressions - trouble: broken/fail/pass osstest service owner
2022-11-18 14:39 ` Roger Pau Monné [this message]
2022-11-18 17:22   ` Flask vs paging mempool - Was: " Andrew Cooper
2022-11-18 21:10     ` Jason Andryuk
2022-11-20 11:08       ` Daniel P. Smith
2022-11-21  8:04         ` Jan Beulich
2022-11-21 12:14           ` Daniel P. Smith
2022-11-21 11:37       ` Andrew Cooper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y3eZOcmOYkNLdeGe@Air-de-Roger \
    --to=roger.pau@citrix.com \
    --cc=Henry.Wang@arm.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.