Date: Fri, 12 Mar 2021 13:53:05 +0100 From: Michal Meloun <meloun.michal@gmail.com> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, =?UTF-8?Q?S=c3=b8ren_Schmidt?= <soren.schmidt@gmail.com> Cc: Emmanuel Vadot <manu@bidouilliste.com>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: problem with dwmmc ? panic's on bad filesystem... Message-ID: <5c717a50-d18d-088d-97ef-0a8043e96e86@freebsd.org> In-Reply-To: <C54FDFB7-8500-4257-B2C6-F7D7A5BCDD8E@lists.zabbadoz.net> References: <794EB96E-2F5D-4F41-BAD8-DEFDB9BDE530@gmail.com> <246a8c2f-bec7-2880-56f6-2baa677e4b2d@FreeBSD.org> <ACA1B34D-2C53-4733-9E7F-5DFC5F3FE84E@gmail.com> <20210312110930.9091f4fb9cea65a6ca7933e0@bidouilliste.com> <33616974-30A2-41E5-B177-8259CC08F60D@gmail.com> <C54FDFB7-8500-4257-B2C6-F7D7A5BCDD8E@lists.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12.03.2021 13:18, Bjoern A. Zeeb wrote: > On 12 Mar 2021, at 12:01, Søren Schmidt wrote: > >> On 12 Mar 2021, at 11.09, Emmanuel Vadot <manu@bidouilliste.com> wrote: >>> >>> On Fri, 12 Mar 2021 09:47:40 +0100 >>> Søren Schmidt <soren.schmidt@gmail.com> wrote: >>> >>>> On 11 Mar 2021, at 23.30, Jesper Schmitz Mouridsen <jsm@FreeBSD.org> >>>> wrote: >>>>> >>>>> >>>>> On 11.03.2021 21.29, Søren Schmidt wrote: >>>>>> Hi >>>>>> >>>>>> I have had this panic several times on rk3399 based systems when >>>>>> the filesystem has gone bad (and just needs a fsck). >>>>>> It doesn?t happen on Marvell a3720, so its not arm64 specific, >>>>>> more likely dwmmc specific or maybe the dma on the rk3399 ? >>>>>> >>>>>> 13-stable of today, but problem has been around for a long time.. >>>>>> >>>>> <snip> >>>>> >>>>> Check under known issues https://wiki.freebsd.org/arm/RockChip. >>>>> >>>>> Should be fixed in >>>>> https://cgit.freebsd.org/src/commit/?id=8727c174b0fe44766bb7ea765dac6d5f82818103 >>>>> >>>>> >>>>> But perhaps it is not included in stable/13 or it is not totally >>>>> fixed? >>>> >>>> That fix is indeed in stable13, so it looks like its not really >>>> fixed, or this is another problem... >>>> >>>> -- >>>> Søren Schmidt >>>> sos@deepcore.dk / sos@freebsd.org >>>> "So much code to hack, so little time" >>> >>> Seems like it's the same issue. >>> Your hitting EFBIG from bus_dmamap_load. >>> Does that happens everytime ? >> >> Yes it does. >> >>> Does that happens if you disable journaling or softupdate ? >> >> Journalling seems to be what triggers this error. >> >> The last (error) request contains 0 segs and a non %blocksize length >> if that helps. > > This sounded familiar; I am not sure what happened to the comments from > this: https://reviews.freebsd.org/D26735 > > It was reincarnated to https://cgit.freebsd.org/src/commit/sys/arm64/arm64/busdma_bounce.c?id=f635cef2a4206fb4e077412c493f218a6a26a3daSøren, is the problem reproducible also on current ? If yes are you able to dump VA and size of buffer passed to last call to bus_dmamap_load? Michal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5c717a50-d18d-088d-97ef-0a8043e96e86>