From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm@vger.kernel.org
Subject: Re: kernel 4.4.2: kvm_irq_delivery_to_api / rwsem_down_read_failed
Date: Mon, 22 Feb 2016 14:44:23 -0500 (EST) [thread overview]
Message-ID: <138627702.27341861.1456170263455.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <56CB630D.8080302@profihost.ag>
----- Original Message -----
> From: "Stefan Priebe" <s.priebe@profihost.ag>
> To: "Paolo Bonzini" <pbonzini@redhat.com>, "qemu-devel" <qemu-devel@nongnu.org>, kvm@vger.kernel.org
> Sent: Monday, February 22, 2016 8:35:41 PM
> Subject: Re: kernel 4.4.2: kvm_irq_delivery_to_api / rwsem_down_read_failed
>
>
> Am 22.02.2016 um 18:36 schrieb Paolo Bonzini:
> >
> >
> > On 20/02/2016 11:44, Stefan Priebe wrote:
> >> Hi,
> >>
> >> while testing Kernel 4.4.2 and starting 20 Qemu 2.4.1 virtual machines.
> >> I got those traces and a load of 500 on those system. I was only abler
> >> to recover by sysrq-trigger.
> >
> > It seems like something happening at the VM level. A task took the mm
> > semaphore and hung everyone else. Difficult to debug without a core
> > (and without knowing who held the semaphore). Sorry.
>
> OK thank you anyway. Is there anything i can do if this happens again?
Try grabbing a vmcore with sysrq-c, if you have kdump configured.
Paolo
prev parent reply other threads:[~2016-02-22 19:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 10:44 kernel 4.4.2: kvm_irq_delivery_to_api / rwsem_down_read_failed Stefan Priebe
2016-02-22 17:36 ` Paolo Bonzini
2016-02-22 19:35 ` Stefan Priebe
2016-02-22 19:44 ` Paolo Bonzini [this message]
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=138627702.27341861.1456170263455.JavaMail.zimbra@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=s.priebe@profihost.ag \
/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.