From: Gary M <garym@oedata.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] DPDK causing Soft lockup on XEN ?
Date: Thu, 17 Jul 2014 14:42:13 -0600 [thread overview]
Message-ID: <CAGwOJnw0nGw_-wmNnHWRVj4vax+Mq-egNcnUVEJqNm7xdsm3AQ@mail.gmail.com> (raw)
Hi,
Maybe this is a config issue.. need some help.
I have a situation where xen is reporting a cpu is stuck after the
ip_fragmentation example hangs setting up memory.
Sys log:
Message from syslogd@port22 at Jul 17 14:27:32 ...
kernel:[180294.724037] BUG: soft lockup - CPU#7 stuck for 22s!
[ip_fragmentatio:12886]
Message from syslogd@port22 at Jul 17 14:28:00 ...
kernel:[180322.724037] BUG: soft lockup - CPU#7 stuck for 22s!
[ip_fragmentatio:12886]
Message from syslogd@port22 at Jul 17 14:28:36 ...
kernel:[180358.724037] BUG: soft lockup - CPU#7 stuck for 23s!
[ip_fragmentatio:12886]
Message from syslogd@port22 at Jul 17 14:29:04 ...
kernel:[180386.724037] BUG: soft lockup - CPU#7 stuck for 23s!
[ip_fragmentatio:12886]
Message from syslogd@port22 at Jul 17 14:29:40 ...
kernel:[180422.724037] BUG: soft lockup - CPU#7 stuck for 22s!
[ip_fragmentatio:12886]
Message from syslogd@port22 at Jul 17 14:30:08 ...
kernel:[180450.724037] BUG: soft lockup - CPU#7 stuck for 22s!
[ip_fragmentatio:12886]
Message from syslogd@port22 at Jul 17 14:30:40 ...
kernel:[180482.724037] BUG: soft lockup - CPU#7 stuck for 22s!
[ip_fragmentatio:12886]
Message from syslogd@port22 at Jul 17 14:31:08 ...
kernel:[180510.724038] BUG: soft lockup - CPU#7 stuck for 22s!
[ip_fragmentatio:12886]
Message from syslogd@port22 at Jul 17 14:31:44 ...
kernel:[180546.724037] BUG: soft lockup - CPU#7 stuck for 23s!
[ip_fragmentatio:12886]
Message from syslogd@port22 at Jul 17 14:32:12 ...
kernel:[180574.724037] BUG: soft lockup - CPU#7 stuck for 23s!
[ip_fragmentatio:12886]
Message from syslogd@port22 at Jul 17 14:32:48 ...
kernel:[180610.724037] BUG: soft lockup - CPU#7 stuck for 22s!
[ip_fragmentatio:12886]
reply other threads:[~2014-07-17 20:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAGwOJnw0nGw_-wmNnHWRVj4vax+Mq-egNcnUVEJqNm7xdsm3AQ@mail.gmail.com \
--to=garym@oedata.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).