All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: osstest service owner <osstest-admin@xenproject.org>,
	xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] [xen-unstable test] 140960: regressions - FAIL
Date: Wed, 4 Sep 2019 10:36:50 +0200	[thread overview]
Message-ID: <3b5b6d76-9087-05f5-5359-ec24322dda65@suse.com> (raw)
In-Reply-To: <osstest-140960-mainreport@xen.org>

On 03.09.2019 22:00, osstest service owner wrote:
> flight 140960 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/140960/
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-amd64-xl-pvshim   18 guest-localmigrate/x10   fail REGR. vs. 139876

This looks to be recurring, so I've taken another look. The three
migrations leave this abbreviated pattern in the log:

Sep  3 14:20:42.446667 (XEN) HVM d1v0 save: CPU_MSR
...
Sep  3 14:20:57.850670 (XEN) HVM2 restore: CPU 0
...
Sep  3 14:21:37.062840 (XEN) HVM d2v0 save: CPU_MSR
Sep  3 14:21:37.062888 (XEN) HVM3 restore: CPU 0
...
Sep  3 14:21:56.438552 (XEN) HVM d3v0 save: CPU_MSR
...
Sep  3 14:22:11.506508 (XEN) HVM4 restore: CPU 0

Therefore I wonder whether the first one got lucky and finished
barely ahead of timing out, while the 2nd worked instantly and the
3rd then ended up exceeding the timeout. What is curious are the
intermediate log entries (between the last "save" and the first
corresponding "restore" log entries): Many ones of the form

(XEN) emul-priv-op.c:1113:d0v2 Domain attempted WRMSR c0011020 from 0x0000000000000000 to 0x0040000000000000

with a 15s gap between the first and many subsequent ones) and
finally one of the form

[  451.267669] systemd-logind[2766]: New session 39 of user root.

And finally, at around the time of the failed migration

INIT: Id "T0" respawning too fast: disabled for 5 minutes

While it's not clear that this parallel activity is causing the
migration to progress too slowly, it looks to be a possibility at
least. Can anyone explain what these are?

>  build-amd64-xsm               6 xen-build                fail REGR. vs. 139876

I take it that this is supposed to be taken care of by a342900d48
("tools/shim: Apply more duct tape to the linkfarm logic").

Jan

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

  reply	other threads:[~2019-09-04  8:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03 20:00 [Xen-devel] [xen-unstable test] 140960: regressions - FAIL osstest service owner
2019-09-04  8:36 ` Jan Beulich [this message]
2019-09-04  8:50   ` 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=3b5b6d76-9087-05f5-5359-ec24322dda65@suse.com \
    --to=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 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.