rte_eal_init() causes PANIC using latest DPDK code.

DISCUSSION Tetsuya Mukawa 4 participants 7 messages Jan 19, 2015 4 messages not in the archive

Share & tools

Tetsuya Mukawa

author

2015-01-19 07:10 UTC #0 lore raw

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".

Thanks,
Tetsuya

Doherty, Declan

2015-01-19 08:53 UTC #2 lore raw

In reply to a message not in the archive

Quoted 36 lines

-----Original Message-----
From: dev [mailto:[email protected]] On Behalf Of Tetsuya Mukawa
Sent: Monday, January 19, 2015 7:11 AM
To: [email protected]
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]]
--------------------------------------------

Quoted 8 lines

I tried bisect, and it seems below patch causes this. "eal: fix check for power of 2 in 0 case".
Thanks,
Tetsuya

Hey Tetsuya,

This is the issue which my patch (http://dpdk.org/dev/patchwork/patch/2333/) submitted on Friday addresses.

Tetsuya Mukawa

author

2015-01-19 08:56 UTC #4 lore raw

In reply to a message not in the archive

Hi Doherty,

Quoted 39 lines · Declan

Quoted 39 lines
-----Original Message-----
From: dev [mailto:[email protected]] On Behalf Of Tetsuya Mukawa
Sent: Monday, January 19, 2015 7:11 AM
To: [email protected]
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".

Quoted 8 lines

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

Thanks.
I could resolve the issue.

Regards,
Tetsuya

Thomas Monjalon

2015-01-19 09:03 UTC #6 lore raw

In reply to a message not in the archive

2015-01-19 17:56, Tetsuya Mukawa:

Quoted 34 lines · Declan

Quoted 33 lines
From: dev [mailto:[email protected]] On Behalf Of Tetsuya Mukawa
Quoted 32 lines
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".

Quoted 6 lines

Quoted 3 lines
Hey Tetsuya,
This is the issue which my patch (http://dpdk.org/dev/patchwork/patch/2333/) submitted on Friday addresses.
Thanks.
I could resolve the issue.

It should be fixed now:

	http://dpdk.org/browse/dpdk/commit/?id=8e3e06501660

Thanks for reporting

Signature · 1 line

Thomas

Qiu, Michael

2015-01-19 09:49 UTC #7 lore raw

In reply to Doherty, Declan

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

Thanks,
Michael

Quoted 48 lines · Declan

Quoted 35 lines
-----Original Message-----
From: dev [mailto:[email protected]] On Behalf Of Tetsuya Mukawa
Sent: Monday, January 19, 2015 7:11 AM
To: [email protected]
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]]
--------------------------------------------
Quoted 8 lines
I tried bisect, and it seems below patch causes this. "eal: fix check for power of 2 in 0 case".
Thanks,
Tetsuya
Hey Tetsuya,
This is the issue which my patch (http://dpdk.org/dev/patchwork/patch/2333/) submitted on Friday addresses.

Tetsuya Mukawa

author

2015-01-19 10:06 UTC #9 lore raw

In reply to a message not in the archive

Quoted 9 lines · Michael

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.

Quoted 7 lines

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

Quoted 52 lines

Thanks,
Michael
Quoted 48 lines · Declan
Quoted 35 lines
-----Original Message-----
From: dev [mailto:[email protected]] On Behalf Of Tetsuya Mukawa
Sent: Monday, January 19, 2015 7:11 AM
To: [email protected]
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]]
--------------------------------------------
Quoted 8 lines
I tried bisect, and it seems below patch causes this. "eal: fix check for power of 2 in 0 case".
Thanks,
Tetsuya
Hey Tetsuya,
This is the issue which my patch (http://dpdk.org/dev/patchwork/patch/2333/) submitted on Friday addresses.

Qiu, Michael

2015-01-19 13:00 UTC #10 lore raw

Quoted 21 lines · Tetsuya Mukawa

Quoted 9 lines · Michael
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.
Quoted 7 lines
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.)

Quoted 48 lines

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
Quoted 41 lines
Thanks,
Michael
Quoted 37 lines · Declan
Quoted 37 lines
-----Original Message-----
From: dev [mailto:[email protected]] On Behalf Of Tetsuya Mukawa
Sent: Monday, January 19, 2015 7:11 AM
To: [email protected]
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

Quoted 12 lines

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