DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nissim Nisimov <NissimN@Radware.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] running dpdk 2.1 on openstak causes CPU soft lockup
Date: Mon, 23 Nov 2015 19:44:09 +0000	[thread overview]
Message-ID: <94AA676E9B9A384A844E7692F3CAD906C5549347@ILMB1.corp.radware.com> (raw)

Hi,

I am running DPDK 2.1.0 based app on OpenStack KVM guest.  OS of guest is Ubuntu LTS 14.04 3.13 kernel.
virtio.

After upgrade to dpdk 2.1 (previous version was dpdk 1.8 and it worked fine) we are seeing the following issue:

[960.004535] BUG: soft lockup - CPU#3 stuck for 23s! [ip:8419]

The message will be printed in an endless loop and the system won't recover.

Is it a known issue in dpdk 2.1? any patch I can apply in order to overcome this?


Thx
Nissim

             reply	other threads:[~2015-11-23 19:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 19:44 Nissim Nisimov [this message]
2015-12-01  8:50 ` Franck BAUDIN
2015-12-01  9:27   ` Nissim Nisimov

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=94AA676E9B9A384A844E7692F3CAD906C5549347@ILMB1.corp.radware.com \
    --to=nissimn@radware.com \
    --cc=dev@dpdk.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).