From: Dario Faggioli <dfaggioli@suse.com>
To: Steven Haigh <netwiz@crc.id.au>, Juergen Gross <jgross@suse.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: RFE: Detect NUMA misconfigurations and prevent machine freezes
Date: Wed, 12 Sep 2018 17:13:59 +0200 [thread overview]
Message-ID: <2d2f115d3f45d76ea439a1b36df9953a3b979aca.camel@suse.com> (raw)
In-Reply-To: <4e93ef83fb40d6a2a87f902f17bc0bc5@crc.id.au>
[-- Attachment #1.1: Type: text/plain, Size: 1527 bytes --]
On Thu, 2018-08-30 at 14:01 +1000, Steven Haigh wrote:
> On 2018-08-29 15:49, Juergen Gross wrote:
> >
> > RAM placement should not matter here. As the name already suggests
> > cpupools do assignment of cpus. RAM allocated will be preferred
> > taken
> > from a local node, but this shouldn't be mandatory for success.
> >
> > Would it be possible to use a debug hypervisor (e.g. 4.12-unstable)
> > for
> > generating a verbose log (hypervisor boot parameter "loglvl=all")
> > and
> > sending the complete hypervisor log?
>
> I don't have a package for 4.11 or 4.12 built at all - but I did this
> on
> 4.10.2-pre (built from staging-4.10).
>
> [..]
>
> Add the CPUs:
> (XEN) Adding cpu 12 to runqueue 0
> (XEN) First cpu on runqueue, activating
> (XEN) Removing cpu 12 from runqueue 0
> (XEN) Adding cpu 13 to runqueue 0
> (XEN) Removing cpu 13 from runqueue 0
> (XEN) Adding cpu 14 to runqueue 0
> (XEN) Removing cpu 14 from runqueue 0
> (XEN) Xen BUG at sched_credit2.c:3452
> (XEN) Adding cpu 15 to runqueue 0
> (XEN) ----[ Xen-4.10.2-pre x86_64 debug=n Not tainted ]----
>
That's not a debug build, though.
It would be useful to test one such build (as suggested by Juergen), to
see if any of the existing ASSERTs triggers.
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Software Engineer @ SUSE https://www.suse.com/
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-09-12 15:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 5:33 RFE: Detect NUMA misconfigurations and prevent machine freezes Steven Haigh
2018-08-29 5:49 ` Juergen Gross
2018-08-30 4:01 ` Steven Haigh
2018-08-30 7:13 ` Juergen Gross
2018-08-30 8:33 ` Jan Beulich
2018-08-30 8:49 ` BUG: sched=credit2 crashes system when using cpupools Steven Haigh
2018-09-12 15:11 ` Dario Faggioli
2018-09-12 15:27 ` Steven Haigh
2018-09-12 15:13 ` Dario Faggioli [this message]
2018-09-13 11:49 ` RFE: Detect NUMA misconfigurations and prevent machine freezes Dario Faggioli
2018-08-29 6:39 ` 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=2d2f115d3f45d76ea439a1b36df9953a3b979aca.camel@suse.com \
--to=dfaggioli@suse.com \
--cc=jgross@suse.com \
--cc=netwiz@crc.id.au \
--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).