DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 14] Kernel Crash bug of ixgbevf kernel module in "Intel(R) 10GbE PCI Express Virtual Function Driver Version: 4.0.3 Release: 1" and the latest version
Date: Fri, 02 Feb 2018 02:43:43 +0000	[thread overview]
Message-ID: <bug-14-3@http.dpdk.org/tracker/> (raw)

https://dpdk.org/tracker/show_bug.cgi?id=14

            Bug ID: 14
           Summary: Kernel Crash bug of ixgbevf kernel module in "Intel(R)
                    10GbE PCI Express Virtual Function Driver Version:
                    4.0.3 Release: 1" and the latest version
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: CONFIRMED
          Severity: critical
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: batmanustc@gmail.com
  Target Milestone: ---

Created attachment 3
  --> https://dpdk.org/tracker/attachment.cgi?id=3&action=edit
vmcore-dmesg.txt

Hi all,

There is a kernel crash bug of ixgbevf kernel module in "Intel(R) 10GbE PCI
Express Virtual Function Driver Version: 4.0.3 Release: 1"

How to produce:
1. Use SRIOV, like this:
sudo /usr/local/share/openvswitch/scripts/dpdk_nic_bind --status

Network devices using DPDK-compatible driver
============================================
0000:01:00.0 'Ethernet Controller 10-Gigabit X540-AT2' drv=igb_uio unused=ixgbe
0000:01:00.1 'Ethernet Controller 10-Gigabit X540-AT2' drv=igb_uio unused=ixgbe

Network devices using kernel driver
===================================
0000:01:10.0 'X540 Ethernet Controller Virtual Function' if=enp1s16 drv=ixgbevf
unused=bak,igb_uio
0000:01:10.1 'X540 Ethernet Controller Virtual Function' if=enp1s16f1
drv=ixgbevf unused=bak,igb_uio
0000:08:00.0 'I350 Gigabit Network Connection' if=eth2 drv=igb unused=igb_uio
0000:08:00.1 'I350 Gigabit Network Connection' if=eth3 drv=igb unused=igb_uio

Other network devices
=====================
<none>

2. bond enp1s16 and enp1s16f1 into bond1, by /etc/sysconfig/ifcfg-bond1.
3. bond 0000:01:00.0 and 0000:01:00.1 in ovs-dpdk into dpdkb2, by dpdk api.
4. stop bond1(ifdown bond1), stop dpdkb2(rte_eth_dev_stop), sleep 5 second,
start dpdkb2(rte_eth_dev_start), start bond1(ifup bond1).

After several times, bug happens, attachment is vmcore-dmesg.txt

similar bug, refer to 
https://sourceforge.net/p/e1000/mailman/message/35173093/

looks like an old bug, please do not hid bug, to fix it.

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

                 reply	other threads:[~2018-02-02  2:43 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=bug-14-3@http.dpdk.org/tracker/ \
    --to=bugzilla@dpdk.org \
    --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).