Re: [dpdk-dev] rte_eal_init() causes PANIC using latest DPDK code.

["Qiu, Michael" <michael.qiu@intel.com>]

On 2015/1/19 18:06, Tetsuya Mukawa wrote:
> On 2015/01/19 18:49, Qiu, Michael wrote:
>> Hi Tetsuya,
>>
>> I see two lines log like:
>>
>> EAL:   cannot open VFIO container, error 2 (No such file or directory)
>> EAL: VFIO support could not be initialized
>>
>> It should not happen as I have a patch merged to master branch.
>>
>> There should have something wrong, could you please help me to debug this?
>>
>> All I needed are the results of:
>> 1.  cat /proc/modules
>> 2. lsmod | grep vfio
>> 3. ls -al /dev/vfio
>> 4. uname -a
> Because I got the log while running bisect, I guess your patch was not
> be applied at the time.
> (But "Fix rte_is_power_of_2" was applied.)
>
> I tried to run testpmd using latest code again, and I didn't see above
> warnings.
> So your patch works fine. Sorry for confusion.
>
> Thanks,
> Tetsuya
>
>> Thanks,
>> Michael
>>
>> On 2015/1/19 16:54, Doherty, Declan wrote:
>>>> -----Original Message-----
>>>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Tetsuya Mukawa
>>>> Sent: Monday, January 19, 2015 7:11 AM
>>>> To: dev@dpdk.org
>>>> Subject: [dpdk-dev] rte_eal_init() causes PANIC using latest DPDK code.
>>>>
>>>> Hi,
>>>>
>>>> I've got following error using latest DPDK code.
>>>> Does someone face the same issue?
>>>> In my environment, It seems almost all DPDK apps (at lease l2fwd and
>>>> testpmd) cannot work.
>>>>
>>>> --------------------------------------------
>>>> EAL: Support maximum 128 logical core(s) by configuration.
>>>> EAL: Detected 8 lcore(s)
>>>> EAL:   cannot open VFIO container, error 2 (No such file or directory)
>>>> EAL: VFIO support could not be initialized
>>>> EAL: Setting up memory...
>>>> EAL: Ask a virtual area of 0x280000000 bytes
>>>> EAL: Virtual area found at 0x7ffd40000000 (size = 0x280000000)
>>>> EAL: Requesting 10 pages of size 1024MB from socket 0
>>>> RING: Cannot reserve memory for tailq
>>>> EAL: rte_eal_common_log_init(): cannot create log_history mempool
>>>> PANIC in rte_eal_init():
>>>> Cannot init logs
>>>> 6: [./build/l2fwd() [0x41cf53]]
>>>> 5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)
>>>> [0x7ffff7105ec5]]
>>>> 4: [./build/l2fwd(main+0x1c) [0x41c52c]]
>>>> 3: [./build/l2fwd(rte_eal_init+0x1073) [0x46a653]]
>>>> 2: [./build/l2fwd(__rte_panic+0xc9) [0x41c3ff]]
>>>> 1: [./build/l2fwd(rte_dump_stack+0x18) [0x471828]]
>>>> --------------------------------------------
>>>>
>>>> I tried bisect, and it seems below patch causes this.
>>>> "eal: fix check for power of 2 in 0 case".

OK, that's fine.

Thanks,
Michael
>>>>
>>>> Thanks,
>>>> Tetsuya
>>>>
>>>>
>>> Hey Tetsuya, 
>>>
>>> This is the issue which my patch (http://dpdk.org/dev/patchwork/patch/2333/) submitted on Friday addresses.
>>>
>>>
>
>