From: <Tudor.Ambarus@microchip.com> To: <regressions@leemhuis.info>, <peda@axentia.se>, <Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com> Cc: <du@axentia.se>, <Patrice.Vilchez@microchip.com>, <Cristian.Birsan@microchip.com>, <Ludovic.Desroches@microchip.com>, <linux-kernel@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <gregkh@linuxfoundation.org>, <saravanak@google.com> Subject: Re: Regression: memory corruption on Atmel SAMA5D31 Date: Mon, 20 Jun 2022 08:43:51 +0000 [thread overview] Message-ID: <6b1bae01-d8fb-1676-3dee-9d5d376e37f1@microchip.com> (raw) In-Reply-To: <bfb4cb27-e2e1-e709-1c27-d938e4d30eab@leemhuis.info> On 6/20/22 10:04, Thorsten Leemhuis wrote: > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe > > On 18.05.22 09:51, Peter Rosin wrote: >> 2022-05-18 at 08:21, Tudor.Ambarus@microchip.com wrote: >>> On 5/17/22 17:50, Peter Rosin wrote: >>>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe >>>> >>>> 2022-04-11 at 08:21, Tudor.Ambarus@microchip.com wrote: >>>>> There are some concurrency bugs in the at-hdmac (DMA) driver, I'm handling them >>>>> and will come with a resolution. Disabling the DMA showed the bug is no more >>>>> reproducible. >>>> >>>> Any news? >>> >>> I'm now allocated on this, so I started looking around what has to be done. >>> I'm thinking of using virt-dma to manage the channels and the request queues. >>> Will get back to you after I'll have something working. >> >> Sounds good, thanks! > > That was about a month ago. Has any progress been made to get this > regression fixed? Hi, Thorsten, Peter, I was mostly out of office last month, and I'll still be offline this week. I made some progress, tried to address the bugs in an incremental way. I now encounter the memory corruption less often, but I still hit it. I made some drafts at [1] if someone is curios. Anyway, I'm modifying the driver to use virt-dma and also I'm trying to move the election of a new transfer in the irq handler instead of in tasklet. I couldn't find a quick non-invasive fix, so still in progress. Cheers, ta git@github.com:ambarus/linux-0day.git, branch dma-regression-hdmac-v5.18-rc7-4th-attempt > > Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) > > P.S.: As the Linux kernel's regression tracker I deal with a lot of > reports and sometimes miss something important when writing mails like > this. If that's the case here, don't hesitate to tell me in a public > reply, it's in everyone's interest to set the public record straight. > > #regzbot poke > >
WARNING: multiple messages have this Message-ID (diff)
From: <Tudor.Ambarus@microchip.com> To: <regressions@leemhuis.info>, <peda@axentia.se>, <Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com> Cc: <du@axentia.se>, <Patrice.Vilchez@microchip.com>, <Cristian.Birsan@microchip.com>, <Ludovic.Desroches@microchip.com>, <linux-kernel@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <gregkh@linuxfoundation.org>, <saravanak@google.com> Subject: Re: Regression: memory corruption on Atmel SAMA5D31 Date: Mon, 20 Jun 2022 08:43:51 +0000 [thread overview] Message-ID: <6b1bae01-d8fb-1676-3dee-9d5d376e37f1@microchip.com> (raw) In-Reply-To: <bfb4cb27-e2e1-e709-1c27-d938e4d30eab@leemhuis.info> On 6/20/22 10:04, Thorsten Leemhuis wrote: > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe > > On 18.05.22 09:51, Peter Rosin wrote: >> 2022-05-18 at 08:21, Tudor.Ambarus@microchip.com wrote: >>> On 5/17/22 17:50, Peter Rosin wrote: >>>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe >>>> >>>> 2022-04-11 at 08:21, Tudor.Ambarus@microchip.com wrote: >>>>> There are some concurrency bugs in the at-hdmac (DMA) driver, I'm handling them >>>>> and will come with a resolution. Disabling the DMA showed the bug is no more >>>>> reproducible. >>>> >>>> Any news? >>> >>> I'm now allocated on this, so I started looking around what has to be done. >>> I'm thinking of using virt-dma to manage the channels and the request queues. >>> Will get back to you after I'll have something working. >> >> Sounds good, thanks! > > That was about a month ago. Has any progress been made to get this > regression fixed? Hi, Thorsten, Peter, I was mostly out of office last month, and I'll still be offline this week. I made some progress, tried to address the bugs in an incremental way. I now encounter the memory corruption less often, but I still hit it. I made some drafts at [1] if someone is curios. Anyway, I'm modifying the driver to use virt-dma and also I'm trying to move the election of a new transfer in the irq handler instead of in tasklet. I couldn't find a quick non-invasive fix, so still in progress. Cheers, ta git@github.com:ambarus/linux-0day.git, branch dma-regression-hdmac-v5.18-rc7-4th-attempt > > Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) > > P.S.: As the Linux kernel's regression tracker I deal with a lot of > reports and sometimes miss something important when writing mails like > this. If that's the case here, don't hesitate to tell me in a public > reply, it's in everyone's interest to set the public record straight. > > #regzbot poke > > _______________________________________________ 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-06-20 8:44 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 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 [this message] 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=6b1bae01-d8fb-1676-3dee-9d5d376e37f1@microchip.com \ --to=tudor.ambarus@microchip.com \ --cc=Cristian.Birsan@microchip.com \ --cc=Ludovic.Desroches@microchip.com \ --cc=Nicolas.Ferre@microchip.com \ --cc=Patrice.Vilchez@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=regressions@leemhuis.info \ --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.