Date: Fri, 12 Mar 2021 13:01:03 +0100 From: =?utf-8?Q?S=C3=B8ren_Schmidt?= <soren.schmidt@gmail.com> To: Emmanuel Vadot <manu@bidouilliste.com> Cc: Jesper Schmitz Mouridsen <jsm@FreeBSD.org>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: problem with dwmmc ? panic's on bad filesystem... Message-ID: <33616974-30A2-41E5-B177-8259CC08F60D@gmail.com> In-Reply-To: <20210312110930.9091f4fb9cea65a6ca7933e0@bidouilliste.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12 Mar 2021, at 11.09, Emmanuel Vadot <manu@bidouilliste.com> wrote: >=20 > On Fri, 12 Mar 2021 09:47:40 +0100 > S=C3=B8ren Schmidt <soren.schmidt@gmail.com> wrote: >=20 >> On 11 Mar 2021, at 23.30, Jesper Schmitz Mouridsen <jsm@FreeBSD.org> = wrote: >>>=20 >>>=20 >>> On 11.03.2021 21.29, S=C3=B8ren Schmidt wrote: >>>> Hi >>>>=20 >>>> 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 ? >>>>=20 >>>> 13-stable of today, but problem has been around for a long time.. >>>>=20 >>> <snip> >>>=20 >>> Check under known issues https://wiki.freebsd.org/arm/RockChip. >>>=20 >>> Should be fixed in = https://cgit.freebsd.org/src/commit/?id=3D8727c174b0fe44766bb7ea765dac6d5f= 82818103 >>>=20 >>> But perhaps it is not included in stable/13 or it is not totally = fixed? >>=20 >> That fix is indeed in stable13, so it looks like its not really = fixed, or this is another problem... >>=20 >> -- >> S=C3=B8ren Schmidt >> sos@deepcore.dk / sos@freebsd.org >> "So much code to hack, so little time" >=20 > 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.=20 >=20 > --=20 > Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org> -- S=C3=B8ren Schmidt sos@deepcore.dk / sos@freebsd.org "So much code to hack, so little time"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?33616974-30A2-41E5-B177-8259CC08F60D>