From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pd0-f178.google.com (mail-pd0-f178.google.com [209.85.192.178]) by dpdk.org (Postfix) with ESMTP id 019525A7A for ; Mon, 19 Jan 2015 09:56:39 +0100 (CET) Received: by mail-pd0-f178.google.com with SMTP id r10so35295135pdi.9 for ; Mon, 19 Jan 2015 00:56:39 -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=L7w0QsbtbGWY5ROSDAelsCKtKluoH9kbcnrkj4Ze0jU=; b=lJSOUYM7gUbQq8cIEbgoT1HYlrEsKlvSZKnl8/8PHcN/GE1goUq9wyM346A+9ejRhp lyvHRnEEJ+enSuDeJWeIVeeW8EmR5zfvelHMGITlzz01Dm/mLEk1NC7oanER4LfSt6RB jSsWRcQDmj9IO6xJJ4c/XRWcNoObYwvnDtLN8LMkIhZuAcBsMYAGD3EEw1bOaAs69ju3 K+S/I04bwQtJ3ifm05t1zEYGBXpvZsWCWJ2S6Cbl2uE4LXqqZSpWcupt8KzPD5bWJjBy bSMh5P3+P/0d0pZ01NivfayNiIQ/9111gQmBS8KTyDxskIlTVjx4a5Bx1Is2cNw6Ez29 izdQ== X-Gm-Message-State: ALoCoQl6J4Rux+9dC5dSLODS1uZyVd3BUjUi8+i1m8Cz30aJqhA0jwhd3p28B2fA7+ZpNYZgkJwD X-Received: by 10.68.135.226 with SMTP id pv2mr43025453pbb.48.1421657799142; Mon, 19 Jan 2015 00:56:39 -0800 (PST) Received: from [10.16.129.101] (napt.igel.co.jp. [219.106.231.132]) by mx.google.com with ESMTPSA id mm9sm6937054pbc.76.2015.01.19.00.56.37 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Jan 2015 00:56:38 -0800 (PST) Message-ID: <54BCC6C6.2050301@igel.co.jp> Date: Mon, 19 Jan 2015 17:56:38 +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: "Doherty, Declan" , "dev@dpdk.org" References: <54BCADF3.1020908@igel.co.jp> <345C63BAECC1AD42A2EC8C63AFFC3ADC27480FA1@IRSMSX101.ger.corp.intel.com> In-Reply-To: <345C63BAECC1AD42A2EC8C63AFFC3ADC27480FA1@IRSMSX101.ger.corp.intel.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit 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 08:56:40 -0000 Hi Doherty, On 2015/01/19 17:53, 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". >> >> >> 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