On 2014/10/15 18:08, Richardson, Bruce wrote:
>
>
>> -Original Message-
>> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Lilijun
>> Sent: Wednesday, October 15, 2014 10:43 AM
>> To: dev at dpdk.org; stephen at networkplumber.org
>> Subject: R
> -Original Message-
> From: Lilijun [mailto:jerry.lilijun at huawei.com]
> Sent: Thursday, October 16, 2014 3:40 AM
> To: Richardson, Bruce; dev at dpdk.org; stephen at networkplumber.org
> Subject: Re: [dpdk-dev] kernel panic when stop my test demo
>
> On 2014/10
Hi all,
After adding unmap uio resources operations in process signal handler functions,
An new error was found as follows:
Call Trace:
[] uio_release+0x40/0x60 [uio]
[] __fput+0xe9/0x270
[] fput+0xe/0x10
[] task_work_run+0xa7/0xe0
[] do_notify_resume+0x97/0xb0
[] int_signal+0x12/0x17
T
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Lilijun
> Sent: Wednesday, October 15, 2014 10:43 AM
> To: dev at dpdk.org; stephen at networkplumber.org
> Subject: Re: [dpdk-dev] kernel panic when stop my test demo
>
> Hi all,
>
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
Hi ereryone, I have a problem when I stop my test demo with ?CTRL+C?, and
then kernel panic.
Any suggestions?
BTW, I?m using the version 1.4.1-7 in RHEL6.4, kernel version is 3.2.28
uio device registered with irq 33
general protection fault: [#1] SMP
CPU 2
Modules linked i
Does your application have a signal handler and stop the device
on shutdown? Since DPDK app's have raw access to the hardware it
is critical to stop the hardware on exit. Other wise the Ethernet
device can overwrite random memory.
Perhaps the igb_uio driver should also have a fail safe and
write
7 matches
Mail list logo
