From: Nicolas Ferre <nicolas.ferre@microchip.com> To: Peter Rosin <peda@axentia.se>, <Tudor.Ambarus@microchip.com>, <saravanak@google.com> Cc: <alexandre.belloni@bootlin.com>, <gregkh@linuxfoundation.org>, <linux-kernel@vger.kernel.org>, <du@axentia.se>, <Ludovic.Desroches@microchip.com>, <linux-arm-kernel@lists.infradead.org> Subject: Re: Regression: memory corruption on Atmel SAMA5D31 Date: Tue, 8 Mar 2022 08:55:42 +0100 [thread overview] Message-ID: <b5c57978-212f-55c4-2f0b-b38a8f157ca3@microchip.com> (raw) In-Reply-To: <7214ea3d-1445-c0fb-2620-cdc3d6167bcc@axentia.se> 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
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@microchip.com> To: Peter Rosin <peda@axentia.se>, <Tudor.Ambarus@microchip.com>, <saravanak@google.com> Cc: <alexandre.belloni@bootlin.com>, <gregkh@linuxfoundation.org>, <linux-kernel@vger.kernel.org>, <du@axentia.se>, <Ludovic.Desroches@microchip.com>, <linux-arm-kernel@lists.infradead.org> Subject: Re: Regression: memory corruption on Atmel SAMA5D31 Date: Tue, 8 Mar 2022 08:55:42 +0100 [thread overview] Message-ID: <b5c57978-212f-55c4-2f0b-b38a8f157ca3@microchip.com> (raw) In-Reply-To: <7214ea3d-1445-c0fb-2620-cdc3d6167bcc@axentia.se> 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
next prev parent reply other threads:[~2022-03-08 7:55 UTC|newest] Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-03 0:29 Regression: memory corruption on Atmel SAMA5D31 Peter Rosin 2022-03-03 3:02 ` Saravana Kannan 2022-03-03 3:02 ` Saravana Kannan 2022-03-03 9:17 ` Peter Rosin 2022-03-03 9:17 ` Peter Rosin 2022-03-04 3:55 ` Saravana Kannan 2022-03-04 3:55 ` Saravana Kannan 2022-03-04 6:57 ` Peter Rosin 2022-03-04 6:57 ` Peter Rosin 2022-03-04 10:57 ` Peter Rosin 2022-03-04 10:57 ` Peter Rosin 2022-03-04 11:12 ` Tudor.Ambarus 2022-03-04 11:12 ` Tudor.Ambarus 2022-03-04 12:38 ` Peter Rosin 2022-03-04 12:38 ` Peter Rosin 2022-03-04 16:48 ` Tudor.Ambarus 2022-03-04 16:48 ` Tudor.Ambarus 2022-03-07 9:45 ` Tudor.Ambarus 2022-03-07 9:45 ` Tudor.Ambarus 2022-03-07 11:32 ` Peter Rosin 2022-03-07 11:32 ` Peter Rosin 2022-03-07 20:32 ` Peter Rosin 2022-03-07 20:32 ` Peter Rosin 2022-03-08 7:55 ` Nicolas Ferre [this message] 2022-03-08 7:55 ` Nicolas Ferre 2022-03-09 8:30 ` Peter Rosin 2022-03-09 8:30 ` Peter Rosin [not found] ` <6d9561a4-39e4-3dbe-5fe2-c6f88ee2a4c6@axentia.se> [not found] ` <ed24a281-1790-8e24-5f5a-25b66527044b@microchip.com> [not found] ` <d563c7ba-6431-2639-9f2a-2e2c6788e625@axentia.se> [not found] ` <e5a715c5-ad9f-6fd4-071e-084ab950603e@microchip.com> 2022-03-10 9:58 ` Peter Rosin 2022-03-10 9:58 ` Peter Rosin 2022-03-10 10:40 ` Peter Rosin 2022-03-10 10:40 ` Peter Rosin 2022-04-09 13:02 ` Thorsten Leemhuis 2022-04-09 13:02 ` Thorsten Leemhuis 2022-04-11 6:21 ` Tudor.Ambarus 2022-04-11 6:21 ` Tudor.Ambarus 2022-05-17 14:50 ` Peter Rosin 2022-05-17 14:50 ` Peter Rosin 2022-05-18 6:21 ` Tudor.Ambarus 2022-05-18 6:21 ` Tudor.Ambarus 2022-05-18 7:51 ` Peter Rosin 2022-05-18 7:51 ` Peter Rosin 2022-06-20 7:04 ` Thorsten Leemhuis 2022-06-20 7:04 ` Thorsten Leemhuis 2022-06-20 8:43 ` Tudor.Ambarus 2022-06-20 8:43 ` Tudor.Ambarus 2022-06-20 14:22 ` Tudor.Ambarus 2022-06-20 14:22 ` Tudor.Ambarus 2022-06-21 7:00 ` Peter Rosin 2022-06-21 7:00 ` Peter Rosin 2022-06-21 10:46 ` Peter Rosin 2022-06-21 10:46 ` Peter Rosin 2022-06-27 12:26 ` Tudor.Ambarus 2022-06-27 12:26 ` Tudor.Ambarus 2022-06-27 16:53 ` Tudor.Ambarus 2022-06-27 16:53 ` Tudor.Ambarus 2022-06-30 5:20 ` Peter Rosin 2022-06-30 5:20 ` Peter Rosin 2022-06-30 9:23 ` Tudor.Ambarus 2022-06-30 9:23 ` Tudor.Ambarus 2022-06-30 10:20 ` Tudor.Ambarus 2022-06-30 10:20 ` Tudor.Ambarus 2022-07-13 16:01 ` Tudor.Ambarus 2022-07-13 16:01 ` Tudor.Ambarus 2022-07-28 7:45 ` Tudor.Ambarus 2022-07-28 7:45 ` Tudor.Ambarus 2022-07-28 8:39 ` Tudor.Ambarus 2022-07-28 8:39 ` Tudor.Ambarus 2022-07-29 20:09 ` Peter Rosin 2022-07-29 20:09 ` Peter Rosin 2022-07-30 11:37 ` Peter Rosin 2022-07-30 11:37 ` Peter Rosin 2022-07-31 3:44 ` Tudor.Ambarus 2022-07-31 3:44 ` Tudor.Ambarus 2022-03-04 20:06 ` Saravana Kannan 2022-03-04 20:06 ` Saravana Kannan 2022-03-04 8:00 ` Thorsten Leemhuis 2022-03-04 8:00 ` Thorsten Leemhuis
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=b5c57978-212f-55c4-2f0b-b38a8f157ca3@microchip.com \ --to=nicolas.ferre@microchip.com \ --cc=Ludovic.Desroches@microchip.com \ --cc=Tudor.Ambarus@microchip.com \ --cc=alexandre.belloni@bootlin.com \ --cc=du@axentia.se \ --cc=gregkh@linuxfoundation.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=peda@axentia.se \ --cc=saravanak@google.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.