dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: chetan bhasin <chetan.bhasin017@gmail.com>
To: "Dey, Souvik" <sodey@rbbn.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] kernel crash with DPDK 18.11
Date: Fri, 5 Jul 2019 13:24:40 +0530	[thread overview]
Message-ID: <CACZZ+Y6oqE3OrV-rn3ADk4znM9B9njtG_JyTdiiUELRMvvgSrQ@mail.gmail.com> (raw)
In-Reply-To: <BN7PR03MB389264885A9A48A7F291FCACCDEE0@BN7PR03MB3892.namprd03.prod.outlook.com>

Hi Souvik,

I am also facing this issue on DPDK 17.11.4 but not sure whether it is
because of fragmented traffic or not.

Are you able to get the direction regarding this issue? Can you please
guide.

Thanks,
Chetan Bhasin

On Sat, Jun 15, 2019 at 12:00 AM Dey, Souvik <sodey@rbbn.com> wrote:

> Hi All,
>               I am using DPDK 18.11 with linux kernel 4.19.28. I have kni
> devices created and I can see a crash in the kernel with ipv6/v4 fragmented
> packets. Does anyone seen this already or is there any fixes/patches
> available for this .
>
> Snippet of kernel panic
>
>
> Message from syslogd@vsbc1 at Jun 14 04:52:05 ...
>
> kernel:[ 6815.672497] rte_kni: kni_net_rx_normal
> kernel:[ 6815.672497] skbuff: skb_over_panic: text:0000000024f44e9b
> len:3024 put:1518 head:000000002a1b576a data:00000000cec907b4 tail:0xc12
> end:0x980 dev:<NULL>
>
> Message from syslogd@vsbc1 at Jun 14 04:52:05 ...
> kernel:[ 6815.672497] skbuff: skb_over_panic: text:0000000024f44e9b
> len:3024 put:1518 head:000000002a1b576a data:00000000cec907b4 tail:0xc12
> end:0x980 dev:<NULL>
>
> Message from syslogd@vsbc1 at Jun 14 04:52:06 ...
> kernel:[ 6815.854134] Kernel panic - not syncing: Fatal exception
>
> Message from syslogd@vsbc1 at Jun 14 04:52:06 ...
> kernel:[ 6815.854134] Kernel panic - not syncing: Fatal exception
> --
> Regards,
> Souvik
>
>
>
> -----------------------------------------------------------------------------------------------------------------------
> Notice: This e-mail together with any attachments may contain information
> of Ribbon Communications Inc. that
> is confidential and/or proprietary for the sole use of the intended
> recipient.  Any review, disclosure, reliance or
> distribution by others or forwarding without express permission is
> strictly prohibited.  If you are not the intended
> recipient, please notify the sender immediately and then delete all
> copies, including any attachments.
>
> -----------------------------------------------------------------------------------------------------------------------
>

      reply	other threads:[~2019-07-05  7:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14 18:30 [dpdk-dev] kernel crash with DPDK 18.11 Dey, Souvik
2019-07-05  7:54 ` chetan bhasin [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=CACZZ+Y6oqE3OrV-rn3ADk4znM9B9njtG_JyTdiiUELRMvvgSrQ@mail.gmail.com \
    --to=chetan.bhasin017@gmail.com \
    --cc=dev@dpdk.org \
    --cc=sodey@rbbn.com \
    /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).