From owner-freebsd-arm@freebsd.org Fri Mar 12 12:18:57 2021 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E6D32577E20 for ; Fri, 12 Mar 2021 12:18:57 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (cross.sbone.de [195.201.62.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DxlGn5F9dz3mDv; Fri, 12 Mar 2021 12:18:57 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 9F07F8D4A156; Fri, 12 Mar 2021 12:18:49 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id AD707E70818; Fri, 12 Mar 2021 12:18:48 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id vyrgDQDOuk4t; Fri, 12 Mar 2021 12:18:47 +0000 (UTC) Received: from [127.0.0.1] (unknown [IPv6:fde9:577b:c1a9:4902:2025:26da:3720:f724]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id BA882E707D0; Fri, 12 Mar 2021 12:18:46 +0000 (UTC) From: "Bjoern A. Zeeb" To: "=?utf-8?q?S=C3=B8ren?= Schmidt" Cc: "Emmanuel Vadot" , freebsd-arm , "Michal Meloun" Subject: Re: problem with dwmmc ? panic's on bad filesystem... Date: Fri, 12 Mar 2021 12:18:45 +0000 X-Mailer: MailMate (2.0BETAr6151) Message-ID: In-Reply-To: <33616974-30A2-41E5-B177-8259CC08F60D@gmail.com> References: <794EB96E-2F5D-4F41-BAD8-DEFDB9BDE530@gmail.com> <246a8c2f-bec7-2880-56f6-2baa677e4b2d@FreeBSD.org> <20210312110930.9091f4fb9cea65a6ca7933e0@bidouilliste.com> <33616974-30A2-41E5-B177-8259CC08F60D@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4DxlGn5F9dz3mDv X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; TAGGED_RCPT(0.00)[]; REPLY(-4.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Porting FreeBSD to ARM processors List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Mar 2021 12:18:58 -0000 On 12 Mar 2021, at 12:01, S=C3=B8ren Schmidt wrote: > On 12 Mar 2021, at 11.09, Emmanuel Vadot = > wrote: >> >> On Fri, 12 Mar 2021 09:47:40 +0100 >> S=C3=B8ren Schmidt wrote: >> >>> On 11 Mar 2021, at 23.30, Jesper Schmitz Mouridsen = >>> wrote: >>>> >>>> >>>> On 11.03.2021 21.29, S=C3=B8ren 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.. >>>>> >>>> >>>> >>>> Check under known issues https://wiki.freebsd.org/arm/RockChip. >>>> >>>> Should be fixed in = >>>> https://cgit.freebsd.org/src/commit/?id=3D8727c174b0fe44766bb7ea765d= ac6d5f82818103 >>>> >>>> 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=C3=B8ren 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