All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: qemu-stable@nongnu.org, "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Kernel: BUG: soft lockup - CPU#0 stuck for 22s! on many machines at the same time
Date: Tue, 1 Mar 2016 11:58:54 +0100	[thread overview]
Message-ID: <56D575EE.9030007@profihost.ag> (raw)

Hello List,

while running Kernel 4.4.2 on the host and Kernel 4.1.18 in guests we're
seeing frequent hangs inside our guests.

This happens for all guests at the same time.

All of them show a trace + soft lockup while seeing no message at the host.

Is this a known bug? I expect this one inside the kernel kvm module as
it happens at the same minute on all guests.

Greets Stefan

             reply	other threads:[~2016-03-01 10:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01 10:58 Stefan Priebe - Profihost AG [this message]
2016-03-06 19:24 ` Kernel: BUG: soft lockup - CPU#0 stuck for 22s! on many machines at the same time Stefan Priebe
2016-03-09  7:37 ` high i/o waits and 100% khugepaged with 4.4.4 Stefan Priebe - Profihost AG
2016-03-17 23:16   ` [Qemu-stable] " Michael Roth
2016-03-21 10:53     ` Stefan Priebe - Profihost AG

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=56D575EE.9030007@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-stable@nongnu.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.