From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pd0-f171.google.com (mail-pd0-f171.google.com [209.85.192.171]) by dpdk.org (Postfix) with ESMTP id D1AB15A95 for ; Mon, 19 Jan 2015 11:06:31 +0100 (CET) Received: by mail-pd0-f171.google.com with SMTP id fp1so14368454pdb.2 for ; Mon, 19 Jan 2015 02:06:31 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ePjQ8CgSXvkWJLid+UCSAmAIpMZKBlAj3JKoMvalScY=; b=SHhuFsFnn75wvW2AhkDddp/C7XHGN0BTnU3iyuW4s/DWBZfK1S45JIWL7pHGgmQn1v 52xehvLdCbkNEHEyOr+NLu6yAjzniIhyJaUsmpQ1aomhyNrI7J7ZDIZoW5bWYXI9+iIT 8/jGvvtEmMFBWwtHmPOVvNMq7daat2ZeYzu+C8QJLIhS1qeoYqwTUJpflihPrUcn96wX nGv4/fL+CC2sjB3ZVF/nQXC246fw7TfSTtSqR99Co+7ZburpDpXBqJGXvV1fDxoGMZ6r PgJQ9dc9K7NyQd9t84lVyfl3gI4SU3USygxLQzUhowKZApxC6sg+oYzi2Iij2NCCJIYq 3BNA== X-Gm-Message-State: ALoCoQnIn6O62vfb3NjeIELdi8mPbygsDzOK0cBaiMK4JqXXQWhSZCoTITvT/AYOosvlAaS0ZYhC X-Received: by 10.68.129.229 with SMTP id nz5mr42757308pbb.144.1421661990918; Mon, 19 Jan 2015 02:06:30 -0800 (PST) Received: from [10.16.129.101] (napt.igel.co.jp. [219.106.231.132]) by mx.google.com with ESMTPSA id id1sm11193855pbc.80.2015.01.19.02.06.19 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Jan 2015 02:06:20 -0800 (PST) Message-ID: <54BCD71C.1010303@igel.co.jp> Date: Mon, 19 Jan 2015 19:06:20 +0900 From: Tetsuya Mukawa User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: "Qiu, Michael" , "Doherty, Declan" , "dev@dpdk.org" References: <54BCADF3.1020908@igel.co.jp> <345C63BAECC1AD42A2EC8C63AFFC3ADC27480FA1@IRSMSX101.ger.corp.intel.com> <533710CFB86FA344BFBF2D6802E60286CB7507@SHSMSX101.ccr.corp.intel.com> In-Reply-To: <533710CFB86FA344BFBF2D6802E60286CB7507@SHSMSX101.ccr.corp.intel.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 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 10:06:32 -0000 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 th= is? > > 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 cod= e. >>> >>> 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 =3D 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 >>> >>> >> Hey Tetsuya,=20 >> >> This is the issue which my patch (http://dpdk.org/dev/patchwork/patch/= 2333/) submitted on Friday addresses. >> >>