All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Igor Druzhinin <igor.druzhinin@citrix.com>,
	osstest-admin@xenproject.org,
	xen-devel <xen-devel@lists.xenproject.org>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [xen-unstable test] 112855: regressions - trouble: blocked/broken/fail/pass
Date: Mon, 28 Aug 2017 01:25:22 -0600	[thread overview]
Message-ID: <59A3E182020000780017449F@prv-mh.provo.novell.com> (raw)
In-Reply-To: <6a7219d3-1019-9537-c545-414a75e9a278@oracle.com>

>>> On 25.08.17 at 19:14, <boris.ostrovsky@oracle.com> wrote:
> On 08/25/2017 09:40 AM, Jan Beulich wrote:
>>>>> On 25.08.17 at 05:15, <osstest-admin@xenproject.org> wrote:
>>> flight 112855 xen-unstable real [real]
>>> http://logs.test-lab.xenproject.org/osstest/logs/112855/ 
>>>
>>> Regressions :-(
>>>
>>> Tests which did not succeed and are blocking,
>>> including tests which could not be run:
>>>  test-amd64-i386-examine       7 reboot                   fail REGR. vs. 112809
>>>  test-amd64-i386-freebsd10-amd64  7 xen-boot              fail REGR. vs. 112809
>> These two are watchdog NMIs during the loading of Dom0. Most
>> likely candidate for introducing the issue is Boris' scrub series.
> 
> 
> I haven't been able to reproduce this but perhaps adding
> process_pending_softirqs() in alloc_heap_pages() and free_heap_pages()
> loops if CONFIG_SCRUB_DEBUG is set might help?

That's possible, but might as well only be papering over a deeper
issue, e.g. ...

> One other thing that also comes to mind is that there is probably no
> reason to scrub (and in some cases poison) pages during dom0 creation.

... this one: Iirc before your series Dom0 pages weren't being
scrubbed, and imo this property ought to be retained (also if
any other boot time allocations now suddenly got scrubbed).

Jan


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

  reply	other threads:[~2017-08-28  7:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25  3:15 [xen-unstable test] 112855: regressions - trouble: blocked/broken/fail/pass osstest service owner
2017-08-25 13:40 ` Jan Beulich
2017-08-25 17:14   ` Boris Ostrovsky
2017-08-28  7:25     ` Jan Beulich [this message]
2017-08-28 13:57       ` Boris Ostrovsky
2017-08-28 14:02         ` Jan Beulich
2017-08-28 14:24           ` Boris Ostrovsky
2017-08-28 14:52             ` Jan Beulich
2017-08-28 15:36               ` Boris Ostrovsky
2017-08-29  8:07                 ` Jan Beulich
2017-08-29 12:45                   ` Boris Ostrovsky
2017-08-29 13:12                     ` Jan Beulich

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=59A3E182020000780017449F@prv-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=igor.druzhinin@citrix.com \
    --cc=osstest-admin@xenproject.org \
    --cc=roger.pau@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.