Date: Fri, 12 Mar 2021 09:47:40 +0100 From: =?utf-8?Q?S=C3=B8ren_Schmidt?= <soren.schmidt@gmail.com> To: Jesper Schmitz Mouridsen <jsm@FreeBSD.org> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: problem with dwmmc ? panic's on bad filesystem... Message-ID: <ACA1B34D-2C53-4733-9E7F-5DFC5F3FE84E@gmail.com> In-Reply-To: <246a8c2f-bec7-2880-56f6-2baa677e4b2d@FreeBSD.org> References: <794EB96E-2F5D-4F41-BAD8-DEFDB9BDE530@gmail.com> <246a8c2f-bec7-2880-56f6-2baa677e4b2d@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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=E2=80=99t 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=E2=80=A6 That fix is indeed in stable13, so it looks like its not really fixed, = or this is another problem... -- 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?ACA1B34D-2C53-4733-9E7F-5DFC5F3FE84E>