From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by dpdk.org (Postfix) with ESMTP id DBD907E78 for ; Tue, 14 Oct 2014 13:51:17 +0200 (CEST) Received: from 172.24.2.119 (EHLO szxeml456-hub.china.huawei.com) ([172.24.2.119]) by szxrg03-dlp.huawei.com (MOS 4.4.3-GA FastPath queued) with ESMTP id AVO08041; Tue, 14 Oct 2014 19:58:58 +0800 (CST) Received: from [127.0.0.1] (10.177.19.236) by szxeml456-hub.china.huawei.com (10.82.67.199) with Microsoft SMTP Server id 14.3.158.1; Tue, 14 Oct 2014 19:58:45 +0800 Message-ID: <543D0FF3.6020306@huawei.com> Date: Tue, 14 Oct 2014 19:58:43 +0800 From: Lilijun User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: "dev@dpdk.org" , References: <20130813225821.3e23ad90@nehalam.linuxnetplumber.net> In-Reply-To: <20130813225821.3e23ad90@nehalam.linuxnetplumber.net> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.177.19.236] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.543D1003.00ED, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-05-26 15:14:31, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 71753cff9712b8159e7fd2347ff1df36 Cc: "zhangsha.zhang@huawei.com" Subject: Re: [dpdk-dev] kernel panic when stop my test demo X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Oct 2014 11:51:19 -0000 Hi Stephen and all, I have a same problem as this older email describes on Aug 14, 2013. Any help will be appreciated. The details is shown as follows. The key step implementation of my demo is: 1. Firstly, call rte_eal_init() to do some initialization. 2. Switch the driver of my Intel 82599 NIC from ixgbe.ko to igb_uio.ko like tools/dpdk_nic_bind.py written in C source code. 3. Configure rte_dev and start it. 4. Do some rx/tx tests. 5. call rte_eth_dev_stop(dpdk_port_id) to stop the hardware as your history emails. 6. Switch the driver of the NIC from igb_uio.ko to ixgbe.ko. 7. Kill the demo using commands: kill -9. Then kernel panics at random points when do something later. One of them as follows: general protection fault: 0000 [#1] SMP Modules linked in: tun igb_uio(OF) uio mlx4_ib ib_sa task: ffff881fd0d6a220 ti: ffff881fd0cf8000 task.ti: ffff881fd0cf8000 RIP: 0010:[] [] dcbnl_rtnl_policy+0x1b111f/0x1e3f70 RSP: 0000:ffff881fd0cf9c38 EFLAGS: 00013282 RAX: ffffffff819770a0 RBX: ffff881fe7b49fa0 RCX: 0000000000000001 RDX: ffffffff8183d851 RSI: ffff881fe7f20da1 RDI: ffffffff819770a0 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: ffff881fe7f20da0 R11: ffff881fd0da0310 R12: ffff881fe811e6c0 R13: 0000000000000000 R14: ffff881fe6d14180 R15: ffff881fe7af4a20 FS: 0000000000000000(0000) GS:ffff88203fc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 00007f2702d3f9e0 CR3: 00000000018ce000 CR4: 00000000000007e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Stack: ffffffffa0235524 ffff881fd0da0300 0000000000000008 ffff881fe7f20da0 ffff881fd0cf9ca0 ffffffff811b1329 ffff881fe7f20da0 ffff881fd0da0310 ffff881fd0da0200 ffffffff81c9be80 ffff881fd0d6a9f0 ffff881fd0d6a220 Call Trace: [] ? uio_release+0x34/0x60 [uio] [] ? __fput+0xe9/0x270 [] ? ____fput+0xe/0x10 [] ? task_work_run+0xc4/0xe0 [] ? do_exit+0x2cb/0xa60 [] ? _raw_spin_unlock_irqrestore+0x1b/0x40 [] ? do_group_exit+0x3f/0xa0 [] ? get_signal_to_deliver+0x1d0/0x6e0 [] ? tun_chr_aio_read+0xa4/0xc0 [tun] [] ? do_signal+0x57/0x600 [] ? kprobe_flush_task+0xd0/0x170 [] ? finish_task_switch+0x14a/0x170 [] ? do_notify_resume+0x69/0xb0 [] ? retint_signal+0x48/0x8c Thanks, Jerry