From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id E777BDED for ; Tue, 1 May 2018 10:59:45 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4525822451; Tue, 1 May 2018 04:59:45 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 01 May 2018 04:59:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=iRgQvMD5XBmrz/oBUD5DL8pd87 m4LqjR5SsrdQJaOlg=; b=pU/M3XiJFGqLwp7HIQoE2lVvpdRTOkFUFLZtqY//6S Dft33h18wp1ro1n7oZJuF3biKrBEiB464HrW9Haf1BUAQyyqID0j/a0KggDutm7S +PDwDH3FlYD6d2IAJCgJ+BXHJVWKY/iIH+N7CmJ1gDzmr4N3IdeQpofNK5DgwV2m w= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=iRgQvM D5XBmrz/oBUD5DL8pd87m4LqjR5SsrdQJaOlg=; b=U1XmomBWNmsO1ipXYQWUFJ C7CQ6I9oUXdQ3siIXZS6+TtEhPYbXJfWhlm8F7V5lend19oRIvyfxqcAueZZ3DXk WfC6oxY1Ah93L8+eSOd5v5tNJGtaek3GXW+Os/b38cU68uaknIQY8DROPYcu2jSz Ac5nUp3e/spHvpJYOawftBEIY9gshWmgU7MgAkmf8v+WL8w7sr1IAx4EIsB7xlUt MrkTZS7T9HoSH5EwAD/A9oaYduA/PTl1rCiTjMHb9JBj3ix7J74vlNE3HQgyRELy 0zYJXkFQicdPY8rk5dechupqtHdQx2P5V/wIm36WeIXuZEcYyx8ziGf+7NI2KWug == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 79B3FE4350; Tue, 1 May 2018 04:59:44 -0400 (EDT) From: Thomas Monjalon To: Olivier Matz , Maxime Coquelin , Anatoly Burakov , Jianfeng Tan Cc: dev@dpdk.org Date: Tue, 01 May 2018 10:59:43 +0200 Message-ID: <1580976.iMHpXaYNWk@xps> In-Reply-To: <4256B2F0-EF9D-4B22-AC1A-D440C002360A@6wind.com> References: <20180403130439.11151-1-olivier.matz@6wind.com> <4256B2F0-EF9D-4B22-AC1A-D440C002360A@6wind.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Subject: Re: [dpdk-dev] pthread_barrier_deadlock in -rc1 (was: "Re: [PATCH v3 0/5] fix control thread affinities") X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 May 2018 08:59:46 -0000 30/04/2018 20:46, Olivier Matz: > Le 30 avril 2018 17:45:52 GMT+02:00, Maxime Coquelin a =E9crit : > >I face a deadlock issue with your series, that Jianfeng patch does not > >resolve ("eal: fix threads block on barrier"). Reverting the series and > >Jianfeng patch makes the issue to disappear. [...] > >I don't have more info for now. >=20 > Thanks for the feedback on this issue. I don't see obvious reason for thi= s deadlock yet. >=20 > I'll investigate it asap (not tomorrow, but wednesday). In the worst case= , we can revert the series if I cannot find the root cause rapidly. Guys, thanks for working on it. There are so many big bugs in RC1 that we need to have an early RC2 today or tomorrow. Maybe someone else, working today, can investigate?