From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 12952C7618B for ; Tue, 23 Jul 2019 10:01:40 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id D50B32239F for ; Tue, 23 Jul 2019 10:01:39 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="mPElDhMM"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=nvidia.com header.i=@nvidia.com header.b="GWGBJFlV" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D50B32239F Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=nvidia.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date: Message-ID:From:References:To:Subject:Reply-To:Content-ID:Content-Description :Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=/L0R9Xnp9cM6cF186FVXk4uu9osInd/TzjiOqOTWr8A=; b=mPElDhMMKk/ZL2 IDfa6eSPoNfZoQg0rl8XB2OCfDEUas6P91jrecm39hPTfINhC5YFkmgCMwx2amUXAYDaD7a18Xibk YLnDi9v6CbC/yCzhFgrYJVD8QlxYArDKEDjD0ZUrbybZ+adPlA+yOaovJ0E6ZvSvgHuv9FDmwMw7v 7EXdMC1vN1wkHdmJuhsx6xHoC68526TReLBjrzRHOYMVt66F2ZXE6eRX7Xy4gI8fKYBxRId0OOy38 cEjkv6EHiLL3jnrQoZ+a7q8cd3bHBmitZOHhX751yofJsNYpd+vQ9XTkPRp2wOZDVFg7KOPACaJPB DpUSWYmYHzgI1cFIAs9w==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1hprc1-0007HL-Qx; Tue, 23 Jul 2019 10:01:37 +0000 Received: from hqemgate16.nvidia.com ([216.228.121.65]) by bombadil.infradead.org with esmtps (Exim 4.92 #3 (Red Hat Linux)) id 1hprby-0007GM-EY for linux-arm-kernel@lists.infradead.org; Tue, 23 Jul 2019 10:01:36 +0000 Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqemgate16.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Tue, 23 Jul 2019 03:01:27 -0700 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate101.nvidia.com (PGP Universal service); Tue, 23 Jul 2019 03:01:30 -0700 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Tue, 23 Jul 2019 03:01:30 -0700 Received: from [10.21.132.148] (10.124.1.5) by HQMAIL107.nvidia.com (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 23 Jul 2019 10:01:26 +0000 Subject: Re: [PATCH net-next 3/3] net: stmmac: Introducing support for Page Pool To: Jose Abreu , Lars Persson , Ilias Apalodimas References: <1b254bb7fc6044c5e6e2fdd9e00088d1d13a808b.1562149883.git.joabreu@synopsys.com> <29dcc161-f7c8-026e-c3cc-5adb04df128c@nvidia.com> <20190722101830.GA24948@apalos> <11557fe0-0cba-cb49-0fb6-ad24792d4a53@nvidia.com> From: Jon Hunter Message-ID: Date: Tue, 23 Jul 2019 11:01:24 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: X-Originating-IP: [10.124.1.5] X-ClientProxiedBy: HQMAIL105.nvidia.com (172.20.187.12) To HQMAIL107.nvidia.com (172.20.187.13) Content-Language: en-US DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1563876087; bh=egy5lIg2QcRmIaxcvymArPwrBaGWeS0BY9hTg1rDFtQ=; h=X-PGP-Universal:Subject:To:CC:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:X-Originating-IP: X-ClientProxiedBy:Content-Type:Content-Language: Content-Transfer-Encoding; b=GWGBJFlVEnm2Ted4BVDkDxLiVC0T9dTzRx5z3HLyjd+XFZIxMB3+HMQ3V2n8TOFFe uv+KmlQFlVmL2mvbNG8Ts5rjNn/sR/iLxsKt7m6G7yAG67IcF63U5sG8kTPlI7rqWW O6BnQicD7myht1gWcsRTm6i0Is+yU77G11VyLoIaqpZCNn3VysXT8RVEmPXplSUnRB H5LJw3eRYSj9eXFoWgR/O9DwM4mePv0AijfUT5QOqPxOYZdBVSdWC4LYxWLqGLZP3a bMe1g2IPQChTtM0zpzKwaXNPhqeL0B45qyYBhM5Ob5f4kobU63l3/wQhxcMMyciKjo vAFvnmgMVO7QQ== X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190723_030134_501004_714E9DD6 X-CRM114-Status: GOOD ( 16.53 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Joao Pinto , Alexandre Torgue , Maxime Ripard , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-stm32@st-md-mailman.stormreply.com" , Chen-Yu Tsai , Maxime Coquelin , linux-tegra , Giuseppe Cavallaro , "David S . Miller" , "linux-arm-kernel@lists.infradead.org" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 23/07/2019 09:14, Jose Abreu wrote: > From: Jose Abreu > Date: Jul/22/2019, 15:04:49 (UTC+00:00) > >> From: Jon Hunter >> Date: Jul/22/2019, 13:05:38 (UTC+00:00) >> >>> >>> On 22/07/2019 12:39, Jose Abreu wrote: >>>> From: Lars Persson >>>> Date: Jul/22/2019, 12:11:50 (UTC+00:00) >>>> >>>>> On Mon, Jul 22, 2019 at 12:18 PM Ilias Apalodimas >>>>> wrote: >>>>>> >>>>>> On Thu, Jul 18, 2019 at 07:48:04AM +0000, Jose Abreu wrote: >>>>>>> From: Jon Hunter >>>>>>> Date: Jul/17/2019, 19:58:53 (UTC+00:00) >>>>>>> >>>>>>>> Let me know if you have any thoughts. >>>>>>> >>>>>>> Can you try attached patch ? >>>>>>> >>>>>> >>>>>> The log says someone calls panic() right? >>>>>> Can we trye and figure were that happens during the stmmac init phase? >>>>>> >>>>> >>>>> The reason for the panic is hidden in this one line of the kernel logs: >>>>> Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b >>>>> >>>>> The init process is killed by SIGSEGV (signal 11 = 0xb). >>>>> >>>>> I would suggest you look for data corruption bugs in the RX path. If >>>>> the code is fetched from the NFS mount then a corrupt RX buffer can >>>>> trigger a crash in userspace. >>>>> >>>>> /Lars >>>> >>>> >>>> Jon, I'm not familiar with ARM. Are the buffer addresses being allocated >>>> in a coherent region ? Can you try attached patch which adds full memory >>>> barrier before the sync ? >>> >>> TBH I am not sure about the buffer addresses either. The attached patch >>> did not help. Same problem persists. >> >> OK. I'm just guessing now at this stage but can you disable SMP ? I tried limiting the number of CPUs to one by setting 'maxcpus=0' on the kernel command line. However, this did not help. >> We have to narrow down if this is coherency issue but you said that >> booting without NFS and then mounting manually the share works ... So, >> can you share logs with same debug prints in this condition in order to >> compare ? > > Jon, I have one ARM based board and I can't face your issue but I > noticed that my buffer addresses are being mapped using SWIOTLB. Can you > disable IOMMU support on your setup and let me know if the problem > persists ? This appears to be a winner and by disabling the SMMU for the ethernet controller and reverting commit 954a03be033c7cef80ddc232e7cbdb17df735663 this worked! So yes appears to be related to the SMMU being enabled. We had to enable the SMMU for ethernet recently due to commit 954a03be033c7cef80ddc232e7cbdb17df735663. Cheers Jon -- nvpublic _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel