From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 2258C5A85 for ; Mon, 19 Jan 2015 14:00:14 +0100 (CET) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga103.jf.intel.com with ESMTP; 19 Jan 2015 04:56:15 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.09,426,1418112000"; d="scan'208";a="639308094" Received: from kmsmsx152.gar.corp.intel.com ([172.21.73.87]) by orsmga001.jf.intel.com with ESMTP; 19 Jan 2015 05:00:08 -0800 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by KMSMSX152.gar.corp.intel.com (172.21.73.87) with Microsoft SMTP Server (TLS) id 14.3.195.1; Mon, 19 Jan 2015 21:00:06 +0800 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.64]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.173]) with mapi id 14.03.0195.001; Mon, 19 Jan 2015 21:00:05 +0800 From: "Qiu, Michael" To: Tetsuya Mukawa , "Doherty, Declan" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] rte_eal_init() causes PANIC using latest DPDK code. Thread-Index: AQHQM7ccOqCdlq3WjE227bbNvqat8Q== Date: Mon, 19 Jan 2015 13:00:05 +0000 Message-ID: <533710CFB86FA344BFBF2D6802E60286CB75E9@SHSMSX101.ccr.corp.intel.com> References: <54BCADF3.1020908@igel.co.jp> <345C63BAECC1AD42A2EC8C63AFFC3ADC27480FA1@IRSMSX101.ger.corp.intel.com> <533710CFB86FA344BFBF2D6802E60286CB7507@SHSMSX101.ccr.corp.intel.com> <54BCD71C.1010303@igel.co.jp> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] rte_eal_init() causes PANIC using latest DPDK code. 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: Mon, 19 Jan 2015 13:00:15 -0000 On 2015/1/19 18:06, Tetsuya Mukawa wrote:=0A= > On 2015/01/19 18:49, Qiu, Michael wrote:=0A= >> Hi Tetsuya,=0A= >>=0A= >> I see two lines log like:=0A= >>=0A= >> EAL: cannot open VFIO container, error 2 (No such file or directory)= =0A= >> EAL: VFIO support could not be initialized=0A= >>=0A= >> It should not happen as I have a patch merged to master branch.=0A= >>=0A= >> There should have something wrong, could you please help me to debug thi= s?=0A= >>=0A= >> All I needed are the results of:=0A= >> 1. cat /proc/modules=0A= >> 2. lsmod | grep vfio=0A= >> 3. ls -al /dev/vfio=0A= >> 4. uname -a=0A= > Because I got the log while running bisect, I guess your patch was not=0A= > be applied at the time.=0A= > (But "Fix rte_is_power_of_2" was applied.)=0A= >=0A= > I tried to run testpmd using latest code again, and I didn't see above=0A= > warnings.=0A= > So your patch works fine. Sorry for confusion.=0A= >=0A= > Thanks,=0A= > Tetsuya=0A= >=0A= >> Thanks,=0A= >> Michael=0A= >>=0A= >> On 2015/1/19 16:54, Doherty, Declan wrote:=0A= >>>> -----Original Message-----=0A= >>>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Tetsuya Mukawa=0A= >>>> Sent: Monday, January 19, 2015 7:11 AM=0A= >>>> To: dev@dpdk.org=0A= >>>> Subject: [dpdk-dev] rte_eal_init() causes PANIC using latest DPDK code= .=0A= >>>>=0A= >>>> Hi,=0A= >>>>=0A= >>>> I've got following error using latest DPDK code.=0A= >>>> Does someone face the same issue?=0A= >>>> In my environment, It seems almost all DPDK apps (at lease l2fwd and= =0A= >>>> testpmd) cannot work.=0A= >>>>=0A= >>>> --------------------------------------------=0A= >>>> EAL: Support maximum 128 logical core(s) by configuration.=0A= >>>> EAL: Detected 8 lcore(s)=0A= >>>> EAL: cannot open VFIO container, error 2 (No such file or directory)= =0A= >>>> EAL: VFIO support could not be initialized=0A= >>>> EAL: Setting up memory...=0A= >>>> EAL: Ask a virtual area of 0x280000000 bytes=0A= >>>> EAL: Virtual area found at 0x7ffd40000000 (size =3D 0x280000000)=0A= >>>> EAL: Requesting 10 pages of size 1024MB from socket 0=0A= >>>> RING: Cannot reserve memory for tailq=0A= >>>> EAL: rte_eal_common_log_init(): cannot create log_history mempool=0A= >>>> PANIC in rte_eal_init():=0A= >>>> Cannot init logs=0A= >>>> 6: [./build/l2fwd() [0x41cf53]]=0A= >>>> 5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)=0A= >>>> [0x7ffff7105ec5]]=0A= >>>> 4: [./build/l2fwd(main+0x1c) [0x41c52c]]=0A= >>>> 3: [./build/l2fwd(rte_eal_init+0x1073) [0x46a653]]=0A= >>>> 2: [./build/l2fwd(__rte_panic+0xc9) [0x41c3ff]]=0A= >>>> 1: [./build/l2fwd(rte_dump_stack+0x18) [0x471828]]=0A= >>>> --------------------------------------------=0A= >>>>=0A= >>>> I tried bisect, and it seems below patch causes this.=0A= >>>> "eal: fix check for power of 2 in 0 case".=0A= =0A= OK, that's fine.=0A= =0A= Thanks,=0A= Michael=0A= >>>>=0A= >>>> Thanks,=0A= >>>> Tetsuya=0A= >>>>=0A= >>>>=0A= >>> Hey Tetsuya, =0A= >>>=0A= >>> This is the issue which my patch (http://dpdk.org/dev/patchwork/patch/2= 333/) submitted on Friday addresses.=0A= >>>=0A= >>>=0A= >=0A= >=0A= =0A=