From: Paul Durrant <Paul.Durrant@citrix.com>
To: Paul Durrant <Paul.Durrant@citrix.com>,
'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 17:30:59 +0000 [thread overview]
Message-ID: <969bdc15844b47d78cf3582dbdd99fd0@AMSPEX02CL01.citrite.net> (raw)
In-Reply-To: <1a164cc4d2994a76a31602bd568c5e68@AMSPEX02CL01.citrite.net>
> -----Original Message-----
> From: Xen-devel [mailto:xen-devel-bounces@lists.xenproject.org] On Behalf
> Of Paul Durrant
> Sent: 16 January 2018 09:27
> To: 'Jan Beulich' <JBeulich@suse.com>
> Cc: xen-devel <xen-devel@lists.xenproject.org>; osstest-
> admin@xenproject.org
> Subject: Re: [Xen-devel] [xen-unstable test] 118078: regressions - FAIL
>
> > -----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.
No real clue about this as yet. It is odd that the guest has only set up one of the APIC assist pages and yet has taken an interrupt...
Jan 16 01:46:05.691223 (XEN) Dumping guest's current state at key_handler...
Jan 16 01:46:05.691265 (XEN) Size of VMCB = 4096, paddr = 000000020f7f7000, vaddr = ffff83020f7f7000
Jan 16 01:46:05.699269 (XEN) cr_intercepts = 0xfef3fef3 dr_intercepts = 0xffffffff exception_intercepts = 0x60082
Jan 16 01:46:05.707128 (XEN) general1_intercepts = 0xbdc4000f general2_intercepts = 0x2e7f
Jan 16 01:46:05.715222 (XEN) iopm_base_pa = 0xdfd71000 msrpm_base_pa = 0x20f7f4000 tsc_offset = 0xfffffc36684278c9
Jan 16 01:46:05.723116 (XEN) tlb_control = 0 vintr = 0x1020001 interrupt_shadow = 0
Jan 16 01:46:05.723153 (XEN) eventinj 000000008000002f, valid? 1, ec? 0, type 0, vector 0x2f
Jan 16 01:46:05.731141 (XEN) exitcode = 0x64 exitintinfo = 0
Jan 16 01:46:05.739123 (XEN) exitinfo1 = 0 exitinfo2 = 0
Jan 16 01:46:05.739157 (XEN) np_enable = 0x1 guest_asid = 0x4b49
Jan 16 01:46:05.739187 (XEN) virtual vmload/vmsave = 0, virt_ext = 0
I'd expect it to have interrupts disabled at this point. Seemingly doesn't repro on Intel h/w (although I was testing with Win7 SP1 rather than RTM) so I'll try to find some AMD h/w and try again.
Paul
> Paul
>
> > Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xenproject.org
> https://lists.xenproject.org/mailman/listinfo/xen-devel
_______________________________________________
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 18:02 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
2018-01-16 17:30 ` Paul Durrant [this message]
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=969bdc15844b47d78cf3582dbdd99fd0@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).