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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9B1D1C433F5 for ; Tue, 8 Mar 2022 07:55:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344558AbiCHH4o (ORCPT ); Tue, 8 Mar 2022 02:56:44 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41612 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231175AbiCHH4m (ORCPT ); Tue, 8 Mar 2022 02:56:42 -0500 Received: from esa.microchip.iphmx.com (esa.microchip.iphmx.com [68.232.154.123]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EAFA93CFD7 for ; Mon, 7 Mar 2022 23:55:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=microchip.com; i=@microchip.com; q=dns/txt; s=mchp; t=1646726146; x=1678262146; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=2p67ZeSQEYzJN6+IMZ2DPIeSrmku0WOj8oNcBKLz79U=; b=jJHq3BmqVZA/bqjsGQ3c84ly8Wj0Uo7QgKTeI+fYOnCnmCRfSrmRLhea MwV1RWlRSA+fu3fFRF/G2zJVanWESz0tS2L8of3sOGYqxpFeXzjnFIkka S18b7krpp6uDDJd2m515Yva9rb2Xq6fPBjr90NQMLKYex0jDWQNJ2m1kx bVFIusDbq7WNHdFBfk8aTbJIAiZKoPzX1rIX7DCLEaVvhl75wxdXiEnBO ldxRgqXIhiHuDBhDiSIRWLETRXTt5i7YS7queo4qXN3EKzHFCJEAJf14v kfpxn5Oa/kilxLu+25jaYxSJElMvVqe9t5hR98g8y1pEER9czZugHMHyf w==; X-IronPort-AV: E=Sophos;i="5.90,163,1643698800"; d="scan'208";a="151206599" Received: from smtpout.microchip.com (HELO email.microchip.com) ([198.175.253.82]) by esa2.microchip.iphmx.com with ESMTP/TLS/AES256-SHA256; 08 Mar 2022 00:55:45 -0700 Received: from chn-vm-ex03.mchp-main.com (10.10.85.151) by chn-vm-ex03.mchp-main.com (10.10.85.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.17; Tue, 8 Mar 2022 00:55:45 -0700 Received: from [10.12.73.60] (10.10.115.15) by chn-vm-ex03.mchp-main.com (10.10.85.151) with Microsoft SMTP Server id 15.1.2375.17 via Frontend Transport; Tue, 8 Mar 2022 00:55:43 -0700 Message-ID: Date: Tue, 8 Mar 2022 08:55:42 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: Regression: memory corruption on Atmel SAMA5D31 Content-Language: en-US To: Peter Rosin , , CC: , , , , , References: <13c6c9a2-6db5-c3bf-349b-4c127ad3496a@axentia.se> <69bb004f-0bb4-ec56-479c-5deab0ece00f@axentia.se> <7edb467a-c8b4-fe29-9947-f71c655caa9f@axentia.se> <8484ce66-639c-03f5-c5db-3574ea26690c@microchip.com> <075a196f-79c2-0d58-15f9-ad5e33e2306b@axentia.se> <3beb80ad-d6f8-8c6a-e17d-e40a644bba07@microchip.com> <9e24034e-f586-a721-9031-179601a69abb@axentia.se> <7214ea3d-1445-c0fb-2620-cdc3d6167bcc@axentia.se> From: Nicolas Ferre Organization: microchip In-Reply-To: <7214ea3d-1445-c0fb-2620-cdc3d6167bcc@axentia.se> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/03/2022 at 21:32, Peter Rosin wrote: > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe > > On 2022-03-07 12:32, Peter Rosin wrote: >> On 2022-03-07 10:45, Tudor.Ambarus@microchip.com wrote: >>> Peter, would it worth to do on your board a similar test to what I did? >>> I'm thinking whether the source of interrupts matters or not. So can you >>> disable your USB and use a mtd NAND stress test as a source of interrupts? >>> mtd_stresstest together with scp or hexdump. >> >> That's not a quick test for me, since I don't have modules enabled. >> I have located my SAMA5D31 evaluation kit, and I think I will try >> to get that running instead. > > Hi again! > > I got my SAMA5D31EK board running, using a freshly built at91bootstrap > and u-boot according to linux4sam.org and using the cross compiler I > have used from buildroot 2021.08, i.e. gcc 10.3.0, then using the > dtb for the ME20 from the original post and the same kernel and userspace > as I have used previously. Now, that dtb describes things that may not > actually be there etc etc, and I will try with a proper dtb as well > tomorrow, so this was just a quick-n-dirty test. I also added mem=64MB > to the kernel command line, to mimic our "Linea" CPU module and get a > bit quicker turnaround in the page cache. > > Anyway, with that setup I can reproduce the problem on the EK board. > > $ while :; do cat testfile | sha256sum; done > 5a939c69dd60a1f991e43d278d2e824a0e7376600a6b20c8e8b347871c546f9b - > 7bf74cf37c8bf81ad4f8e86da8eb129a8ae0ee0f5a22ac584ad39233b97acb4d - > 7bf74cf37c8bf81ad4f8e86da8eb129a8ae0ee0f5a22ac584ad39233b97acb4d - > 250556db0a6ac3c3e101ae2845da48ebb39a0c12d4c9b9eec5ea229c426bcce9 - > 874c694ed002b04b67bf354a95ee521effd07e198f363e02cd63069a94fd4df8 - > 7bf74cf37c8bf81ad4f8e86da8eb129a8ae0ee0f5a22ac584ad39233b97acb4d - > c3a918a923ff2d504a45ffa51289e69fb6d8aa1140cca3fd9f30703b18d9e509 - > 1577ed72d2f296f9adc50707e0e56547ecb311fa21ad875a3d55ca908c440307 - > 7bf74cf37c8bf81ad4f8e86da8eb129a8ae0ee0f5a22ac584ad39233b97acb4d - > 7bf74cf37c8bf81ad4f8e86da8eb129a8ae0ee0f5a22ac584ad39233b97acb4d - > > > But apparently only if I have an FTDI usb-serial adapter attached > while I boot. I also start to get good hashes if I remove and > reinsert the FTDI adapter, which is interesting. > > $ while :; do cat testfile | sha256sum; done > 7bf74cf37c8bf81ad4f8e86da8eb129a8ae0ee0f5a22ac584ad39233b97acb4d - > 7bf74cf37c8bf81ad4f8e86da8eb129a8ae0ee0f5a22ac584ad39233b97acb4d - > 7bf74cf37c8bf81ad4f8e86da8eb129a8ae0ee0f5a22ac584ad39233b97acb4d - > ... > *snip many dozens of lines* > ... > 7bf74cf37c8bf81ad4f8e86da8eb129a8ae0ee0f5a22ac584ad39233b97acb4d - > > It's of course hard to prove the absence of trouble, but it feels > like it is working from both of those latter cases... > > (for the "real" case the FTDI usb-serial adapter is soldered in, > with no easy way to make it go away, so it is not as easy to do the > same test there.) > > I'll try to reduce the number of local parts of the setup further > tomorrow, such as the dtb mentioned above and the rootfs. I was > hoping for a binary download of prebuilt parts, but some links on > > https://www.linux4sam.org/bin/view/Linux4SAM/Sama5d3xekMainPage > > are bogus. E.g. > > ftp://twiki.lnx4mchp_backend/pub/demo/linux4sam_4.7/linux4sam-poky-sama5d3xek-4.7.zip Okay, that's a bug in the TWiki page. > What's up with that twiki.lnx4mchp_backend "host"? URL must be: https://files.linux4sam.org/pub/demo/linux4sam_4.7/linux4sam-poky-sama5d3xek-4.7.zip Regards, Nicolas -- Nicolas Ferre 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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id 43822C433F5 for ; Tue, 8 Mar 2022 07:57:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Content-Type: Content-Transfer-Encoding:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:From:References:CC:To:Subject: MIME-Version:Date:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=JrB/qJfyX2WQM275GV2wdPnhrqSPxYeOGndekpOIIS0=; b=kBYXvfFUT+qizk vhB0GtOmhvxET27Ctc1p8g43Wx7qhrBOi1piJlBP7a20Qmh3hfhEtQx/v+nmY03VxuGACoTLQazCz CluZlmZE18+kWDJ6GFwJZ67njLGTK8Mw6FLccBSsIO1xkPHu0RrpEHP55Yhop3sgnHl/SjRWPtTrD C/NqSe4Hiog+B5YMeAvs9KXok7qVnwz+q0xhQhddtV9LZn35MzDb4ZcuSFExQBs4jKMPC9EtHMa/C 8PxtLGaZLnl0s/r+D9TtW+Fgpvr1w1lqo2ga6ve+vLZBgWSQZfSyMT0jRovuf5XYB8EB4PrWtRO6k yAAhdOlCv5y+PWXNGj6Q==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nRUhF-0037at-0e; Tue, 08 Mar 2022 07:55:53 +0000 Received: from esa.microchip.iphmx.com ([68.232.154.123]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nRUhA-0037ZC-J3 for linux-arm-kernel@lists.infradead.org; Tue, 08 Mar 2022 07:55:50 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=microchip.com; i=@microchip.com; q=dns/txt; s=mchp; t=1646726148; x=1678262148; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=2p67ZeSQEYzJN6+IMZ2DPIeSrmku0WOj8oNcBKLz79U=; b=O2XmUutTpICstDDh54oaQYWzh2L0X8PdI/XtdIHBWpfZp+LNUiH0gFgW 6K81yTcqlY7l8WXsNuq0IBpMhiTT9K8uhxFU5z5g3iQ7Nn+gelAaxdOz/ OVw8UrhEHZyz6YJPmpGrwFwfV2fUhfBkg9cObQp9O6BA55FfCzWqhYyx0 aHP1f+0hkKZBIc+XFiy8Al3jt1A68dp1fgZfYSY2yaYVw0a14zlpuX+NV Z2fETRaZelAp9UxhsBhwSVs9w7lMpiYiz+c+kaHWjTU9nU7wCyltwaLYw HLuRAgm+EQq2xALlpJgr9aNbvBoJesMarjhb7AyffBKfAVbqccvP7azZr Q==; X-IronPort-AV: E=Sophos;i="5.90,163,1643698800"; d="scan'208";a="151206599" Received: from smtpout.microchip.com (HELO email.microchip.com) ([198.175.253.82]) by esa2.microchip.iphmx.com with ESMTP/TLS/AES256-SHA256; 08 Mar 2022 00:55:45 -0700 Received: from chn-vm-ex03.mchp-main.com (10.10.85.151) by chn-vm-ex03.mchp-main.com (10.10.85.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.17; Tue, 8 Mar 2022 00:55:45 -0700 Received: from [10.12.73.60] (10.10.115.15) by chn-vm-ex03.mchp-main.com (10.10.85.151) with Microsoft SMTP Server id 15.1.2375.17 via Frontend Transport; Tue, 8 Mar 2022 00:55:43 -0700 Message-ID: Date: Tue, 8 Mar 2022 08:55:42 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: Regression: memory corruption on Atmel SAMA5D31 Content-Language: en-US To: Peter Rosin , , CC: , , , , , References: <13c6c9a2-6db5-c3bf-349b-4c127ad3496a@axentia.se> <69bb004f-0bb4-ec56-479c-5deab0ece00f@axentia.se> <7edb467a-c8b4-fe29-9947-f71c655caa9f@axentia.se> <8484ce66-639c-03f5-c5db-3574ea26690c@microchip.com> <075a196f-79c2-0d58-15f9-ad5e33e2306b@axentia.se> <3beb80ad-d6f8-8c6a-e17d-e40a644bba07@microchip.com> <9e24034e-f586-a721-9031-179601a69abb@axentia.se> <7214ea3d-1445-c0fb-2620-cdc3d6167bcc@axentia.se> From: Nicolas Ferre Organization: microchip In-Reply-To: <7214ea3d-1445-c0fb-2620-cdc3d6167bcc@axentia.se> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220307_235548_880159_1432AC58 X-CRM114-Status: GOOD ( 31.18 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 07/03/2022 at 21:32, Peter Rosin wrote: > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe > > On 2022-03-07 12:32, Peter Rosin wrote: >> On 2022-03-07 10:45, Tudor.Ambarus@microchip.com wrote: >>> Peter, would it worth to do on your board a similar test to what I did? >>> I'm thinking whether the source of interrupts matters or not. So can you >>> disable your USB and use a mtd NAND stress test as a source of interrupts? >>> mtd_stresstest together with scp or hexdump. >> >> That's not a quick test for me, since I don't have modules enabled. >> I have located my SAMA5D31 evaluation kit, and I think I will try >> to get that running instead. > > Hi again! > > I got my SAMA5D31EK board running, using a freshly built at91bootstrap > and u-boot according to linux4sam.org and using the cross compiler I > have used from buildroot 2021.08, i.e. gcc 10.3.0, then using the > dtb for the ME20 from the original post and the same kernel and userspace > as I have used previously. Now, that dtb describes things that may not > actually be there etc etc, and I will try with a proper dtb as well > tomorrow, so this was just a quick-n-dirty test. I also added mem=64MB > to the kernel command line, to mimic our "Linea" CPU module and get a > bit quicker turnaround in the page cache. > > Anyway, with that setup I can reproduce the problem on the EK board. > > $ while :; do cat testfile | sha256sum; done > 5a939c69dd60a1f991e43d278d2e824a0e7376600a6b20c8e8b347871c546f9b - > 7bf74cf37c8bf81ad4f8e86da8eb129a8ae0ee0f5a22ac584ad39233b97acb4d - > 7bf74cf37c8bf81ad4f8e86da8eb129a8ae0ee0f5a22ac584ad39233b97acb4d - > 250556db0a6ac3c3e101ae2845da48ebb39a0c12d4c9b9eec5ea229c426bcce9 - > 874c694ed002b04b67bf354a95ee521effd07e198f363e02cd63069a94fd4df8 - > 7bf74cf37c8bf81ad4f8e86da8eb129a8ae0ee0f5a22ac584ad39233b97acb4d - > c3a918a923ff2d504a45ffa51289e69fb6d8aa1140cca3fd9f30703b18d9e509 - > 1577ed72d2f296f9adc50707e0e56547ecb311fa21ad875a3d55ca908c440307 - > 7bf74cf37c8bf81ad4f8e86da8eb129a8ae0ee0f5a22ac584ad39233b97acb4d - > 7bf74cf37c8bf81ad4f8e86da8eb129a8ae0ee0f5a22ac584ad39233b97acb4d - > > > But apparently only if I have an FTDI usb-serial adapter attached > while I boot. I also start to get good hashes if I remove and > reinsert the FTDI adapter, which is interesting. > > $ while :; do cat testfile | sha256sum; done > 7bf74cf37c8bf81ad4f8e86da8eb129a8ae0ee0f5a22ac584ad39233b97acb4d - > 7bf74cf37c8bf81ad4f8e86da8eb129a8ae0ee0f5a22ac584ad39233b97acb4d - > 7bf74cf37c8bf81ad4f8e86da8eb129a8ae0ee0f5a22ac584ad39233b97acb4d - > ... > *snip many dozens of lines* > ... > 7bf74cf37c8bf81ad4f8e86da8eb129a8ae0ee0f5a22ac584ad39233b97acb4d - > > It's of course hard to prove the absence of trouble, but it feels > like it is working from both of those latter cases... > > (for the "real" case the FTDI usb-serial adapter is soldered in, > with no easy way to make it go away, so it is not as easy to do the > same test there.) > > I'll try to reduce the number of local parts of the setup further > tomorrow, such as the dtb mentioned above and the rootfs. I was > hoping for a binary download of prebuilt parts, but some links on > > https://www.linux4sam.org/bin/view/Linux4SAM/Sama5d3xekMainPage > > are bogus. E.g. > > ftp://twiki.lnx4mchp_backend/pub/demo/linux4sam_4.7/linux4sam-poky-sama5d3xek-4.7.zip Okay, that's a bug in the TWiki page. > What's up with that twiki.lnx4mchp_backend "host"? URL must be: https://files.linux4sam.org/pub/demo/linux4sam_4.7/linux4sam-poky-sama5d3xek-4.7.zip Regards, Nicolas -- Nicolas Ferre _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel