All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dietmar Hahn <dietmar.hahn@ts.fujitsu.com>
To: xen-devel@lists.xenproject.org
Subject: POD: soft lockups in dom0 kernel
Date: Thu, 05 Dec 2013 14:55:29 +0100	[thread overview]
Message-ID: <1538524.5AKIkpF9LB@amur> (raw)

Hi,

when creating a bigger (> 50 GB) HVM guest with maxmem > memory we get
softlockups from time to time.

kernel: [  802.084335] BUG: soft lockup - CPU#1 stuck for 22s! [xend:31351]

I tracked this down to the call of xc_domain_set_pod_target() and further
p2m_pod_set_mem_target().

Unfortunately I can this check only with xen-4.2.2 as I don't have a machine
with enough memory for current hypervisors. But it seems the code is nearly
the same.

My suggestion would be to do the 'pod set target' in the function
xc_domain_set_pod_target() in chunks of maybe 1GB to give the dom0 scheduler
a chance to run.
As this is not performance critical it should not be a problem.

I can reproduce this with SLES11-SP3 with Linux 3.0.101 and xen-4.2.2.

# cat dummy
name = "DummyOS"
memory = 10000
maxmem = 12000
builder='hvm'

# echo 1 > /proc/sys/kernel/watchdog_thresh
# xm create -c dummy

This leads to a kernel message:
kernel: [ 5019.958089] BUG: soft lockup - CPU#4 stuck for 3s! [xend:20854]

Any comments are welcome.
Thanks.

Dietmar.

-- 
Company details: http://ts.fujitsu.com/imprint.html

             reply	other threads:[~2013-12-05 13:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 13:55 Dietmar Hahn [this message]
2013-12-06 10:00 ` POD: soft lockups in dom0 kernel Jan Beulich
2013-12-06 11:07   ` David Vrabel
2013-12-06 11:30     ` Jan Beulich
2013-12-06 12:00       ` David Vrabel
2013-12-06 13:52         ` Dietmar Hahn
2013-12-06 14:58           ` David Vrabel
2013-12-06 14:50         ` Boris Ostrovsky
2014-01-16 11:10 ` Jan Beulich
2014-01-20 14:39   ` Andrew Cooper
2014-01-20 15:16     ` Jan Beulich
2014-01-29 14:12   ` Dietmar Hahn

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=1538524.5AKIkpF9LB@amur \
    --to=dietmar.hahn@ts.fujitsu.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.