netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 196889] New: kernel panic net_rx_action+0x21e/0x22d
Date: Sun, 10 Sep 2017 10:32:05 -0700	[thread overview]
Message-ID: <20170910103205.2f8c8819@xeon-e3> (raw)



Begin forwarded message:

Date: Sun, 10 Sep 2017 12:21:13 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 196889] New: kernel panic net_rx_action+0x21e/0x22d


https://bugzilla.kernel.org/show_bug.cgi?id=196889

            Bug ID: 196889
           Summary: kernel panic net_rx_action+0x21e/0x22d
           Product: Networking
           Version: 2.5
    Kernel Version: 4.13.0+
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
          Assignee: stephen@networkplumber.org
          Reporter: pstaszewski@itcare.pl
        Regression: No

Created attachment 258289
  --> https://bugzilla.kernel.org/attachment.cgi?id=258289&action=edit  
kernel panic screenshoot

Hardware:
Intel E5-2670
Network controllers
2x 10G Intel 82599
1x 100G Mellanox Connectx-5

Test scenario:
Packet generator -> (RX traffix on Mellanox 100G / 12Mpps UDP random
destination ip / random port )Tested HOST (TX traffix from Intel 82599 on 20
vlans attached to ethernet) -> Sink



Kernal panic occured after 5 minutes from start to send traffic by packet
generator.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2017-09-10 17:32 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=20170910103205.2f8c8819@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=netdev@vger.kernel.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).