Date: Fri, 19 Mar 2021 09:49:14 +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: newfs segfault (was:nvme dma returns EFBIG (27)) Message-ID: <D15728CC-D0BF-44C5-87AD-32D6DC8F892E@gmail.com> In-Reply-To: <0b47bc28-5541-ef9a-7883-952a8a5713f0@FreeBSD.org> References: <15cc2f1d-b8e5-5df3-a05a-4f3014074918@FreeBSD.org> <20210210230833.d8ed42bcdf4707ebf0d2aea6@bidouilliste.com> <e4110cb3-8c11-7bbc-506d-3375406cac1c@FreeBSD.org> <2AAF8FF6-F4F1-4221-BA88-FBDD5463B84F@yahoo.com> <cf860573-987d-a524-805c-a66250cf3c0a@FreeBSD.org> <b2f873b3-39b5-44f9-cf04-a1afff329b84@FreeBSD.org> <0b47bc28-5541-ef9a-7883-952a8a5713f0@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13 Feb 2021, at 21.09, Jesper Schmitz Mouridsen <jsm@FreeBSD.org> = wrote: >=20 >=20 > <snip> >=20 > building newfs with -00 on the pinebook pro itself is a workaround for = me. >=20 > now on 14-CURRENT a62dc346f617 >=20 > The question is if it is a power issue as S=C3=B8ren Schmidt sos@ = suggests or a compiler issue. >=20 > zfs worked all the time. >=20 > I tried with the pinebook pros battery out, it still segfaults with = -02 and works with -00 >=20 > How would I investegate further? >=20 > /Jesper Did you ever find a solution to this problem ? I=E2=80=99m now facing the exact same problem, after having updated to = latest -stable13 sources. Are we looking into a compiler problem on aarch64 ? -- 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?D15728CC-D0BF-44C5-87AD-32D6DC8F892E>