From: Sam <batmanustc@gmail.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] Kernel Crash bug of ixgbevf kernel module in "Intel(R) 10GbE PCI Express Virtual Function Driver Version: 4.0.3 Release: 1"
Date: Wed, 31 Jan 2018 16:59:13 +0800 [thread overview]
Message-ID: <CAOE=1Z0AYMdL9S_sK+mKmO8Gz4oxDVQLgtM0Ok0ZXzvs1d3V8g@mail.gmail.com> (raw)
In-Reply-To: <CAOE=1Z1a3Pm5NneOMphh576ugPdMogHb0a6BuTX07W-oGsd25g@mail.gmail.com>
I don't know if it's because ixgbevf driver call "ixgbevf_close()" by
"dev_close()" without rtnl_lock().
Refer to log "bond1: Releasing active interface enp1s16f1", bond is
releasing its slaves, then call "dev_close()" function without rtnl_lock().
At the same time, "ixgbevf_service_task()" loop to
"ixgbevf_reinit_locked()" function. Then two thread operate same address,
then bug happens.
2018-01-31 15:44 GMT+08:00 Sam <batmanustc@gmail.com>:
> wrong order, actually is this:
> 4. stop bond1(ifdown bond1), stop dpdkb2(rte_eth_dev_stop), sleep 5 second,
> start dpdkb2(rte_eth_dev_start), start bond1(ifup bond1).
>
> 2018-01-31 15:34 GMT+08:00 Sam <batmanustc@gmail.com>:
>
>> 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 dpdkb2(rte_eth_dev_stop), stop bond1(ifdown bond1), sleep 5
>> second, start bond1(ifup bond1), start dpdkb2(rte_eth_dev_start).
>>
>> After several times, bug happens, attachment is vmcore-dmesg.txt
>>
>
>
prev parent reply other threads:[~2018-01-31 8:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOE=1Z1X=EDxGSghBhzUHGxjDEiOAvtF=z-QA+HnhmxO7Nfe9w@mail.gmail.com>
2018-01-31 7:44 ` Sam
2018-01-31 8:59 ` Sam [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='CAOE=1Z0AYMdL9S_sK+mKmO8Gz4oxDVQLgtM0Ok0ZXzvs1d3V8g@mail.gmail.com' \
--to=batmanustc@gmail.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).