From: Paul Durrant <Paul.Durrant@citrix.com>
To: 'Jan Beulich' <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
"osstest-admin@xenproject.org" <osstest-admin@xenproject.org>
Subject: Re: [xen-unstable test] 118078: regressions - FAIL
Date: Tue, 16 Jan 2018 09:26:38 +0000 [thread overview]
Message-ID: <1a164cc4d2994a76a31602bd568c5e68@AMSPEX02CL01.citrite.net> (raw)
In-Reply-To: <5A5DCC9D020000780019EFF9@prv-mh.provo.novell.com>
> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@suse.com]
> Sent: 16 January 2018 08:58
> To: Paul Durrant <Paul.Durrant@citrix.com>
> Cc: xen-devel <xen-devel@lists.xenproject.org>; osstest-
> admin@xenproject.org
> Subject: Re: [Xen-devel] [xen-unstable test] 118078: regressions - FAIL
>
> >>> On 16.01.18 at 09:43, <osstest-admin@xenproject.org> wrote:
> > flight 118078 xen-unstable real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/118078/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > build-arm64-pvops 6 kernel-build fail REGR. vs. 118003
> > test-amd64-amd64-xl-qemut-win7-amd64 10 windows-install fail REGR. vs.
> 118003
>
> Paul,
>
> is this last one something you could look into?
>
> (XEN) d4: VIRIDIAN GUEST_OS_ID: vendor: 1 os: 4 major: 6 minor: 1 sp: 0
> build: 1db0
> (XEN) d4: VIRIDIAN HYPERCALL: enabled: 1 pfn: 3ffff
> (XEN) d4v0: VIRIDIAN VP_ASSIST_PAGE: enabled: 1 pfn: 3fffe
> (XEN) domain_crash called from viridian.c:452
> (XEN) Domain 4 (vcpu#0) crashed on cpu#1:
> (XEN) ----[ Xen-4.11-unstable x86_64 debug=y Not tainted ]----
> (XEN) CPU: 1
> (XEN) RIP: 0010:[<fffff8000265d479>]
> (XEN) RFLAGS: 0000000000000286 CONTEXT: hvm guest (d4v0)
> (XEN) rax: 0000000000000000 rbx: fffff800027f7e80 rcx: 0000000000000001
> (XEN) rdx: 0000000000000000 rsi: fffffa800129d040 rdi: fffff80002805c40
> (XEN) rbp: 0000000000000080 rsp: fffff880009b0d80 r8: 0000000000000000
> (XEN) r9: fffff800027f7e80 r10: fffffa800129d040 r11: fffff800027f7e90
> (XEN) r12: fffff800008129a0 r13: fffff800028b9be0 r14: fffffa8001239b30
> (XEN) r15: fffff80000b96080 cr0: 0000000080050031 cr4: 00000000000006b8
> (XEN) cr3: 0000000000187000 cr2: 0000000000000000
> (XEN) fsb: 0000000000000000 gsb: fffff800027f7d00 gss: fffff800027f7d00
> (XEN) ds: 002b es: 002b fs: 0053 gs: 002b ss: 0018 cs: 0010
>
> I.e. the domain_crash() in viridian_start_apic_assist().
>
Yes, I'll have a look at that.
Paul
> Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-01-16 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 8:43 [xen-unstable test] 118078: regressions - FAIL osstest service owner
2018-01-16 8:57 ` Jan Beulich
2018-01-16 9:26 ` Paul Durrant [this message]
2018-01-16 17:30 ` Paul Durrant
2018-01-17 8:51 ` Jan Beulich
2018-01-17 9:37 ` Paul Durrant
2018-01-17 10:17 ` Paul Durrant
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=1a164cc4d2994a76a31602bd568c5e68@AMSPEX02CL01.citrite.net \
--to=paul.durrant@citrix.com \
--cc=JBeulich@suse.com \
--cc=osstest-admin@xenproject.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).