DPDK patches and discussions
 help / color / mirror / Atom feed
From: Alejandro Lucero <alejandro.lucero@netronome.com>
To: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] kernel: BUG: soft lockup - CPU#1 stuck for 22s! [kni_single:1782]
Date: Wed, 11 Feb 2015 16:25:53 +0000	[thread overview]
Message-ID: <CAD+H990A4UOw6qthPHfegdzyzcJOh+a8A9=HKeyp59niAgNBDw@mail.gmail.com> (raw)
In-Reply-To: <CADNuJVpqB+kydPe1QXcLV21GRF-TMR9dkXdYysk7XTdBZryhcQ@mail.gmail.com>

Hi Jay,

I saw these errors when I worked in the HPC sector. They come usually with
a kernel dump for each core in the machine so you can know, after some
peering at the kernel code, how the soft lockup triggers. When I did that
it was always an issue with the memory.

So those times that you can still work on the machine after the problem,
look at the kernel messages. I will be glad to look at it.



On Wed, Feb 11, 2015 at 1:33 AM, Jay Rolette <rolette@infiniteio.com> wrote:

> Environment:
>   * DPDK 1.6.0r2
>   * Ubuntu 14.04 LTS
>   * kernel: 3.13.0-38-generic
>
> When we start exercising KNI a fair bit (transferring files across it, both
> sending and receiving), I'm starting to see a fair bit of these kernel
> lockups:
>
> kernel: BUG: soft lockup - CPU#1 stuck for 22s! [kni_single:1782]
>
> Frequently I can't do much other than get a screenshot of the error message
> coming across the console session once we get into this state, so debugging
> what is happening is "interesting"...
>
> I've seen this on multiple hardware platforms (so not box specific) as well
> as virtual machines.
>
> Are there any known issues with KNI that would cause kernel lockups in DPDK
> 1.6? Really hoping someone that knows KNI well can point me in the right
> direction.
>
> KNI in the 1.8 tree is significantly different, so it didn't look
> straight-forward to back-port it, although I do see a few changes that
> might be relevant.
>
> Any suggestions, pointers or other general help for tracking this down?
>
> Thanks!
> Jay
>

  reply	other threads:[~2015-02-11 16:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11  1:33 Jay Rolette
2015-02-11 16:25 ` Alejandro Lucero [this message]
2015-02-16 13:32   ` Jay Rolette
2015-02-16 16:33 ` Jay Rolette
2015-02-17  1:00   ` Matthew Hall
2015-02-17 15:57     ` Jay Rolette

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='CAD+H990A4UOw6qthPHfegdzyzcJOh+a8A9=HKeyp59niAgNBDw@mail.gmail.com' \
    --to=alejandro.lucero@netronome.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).