From nobody Sat Feb 18 23:49:32 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PK5576pXPz3s4cP for ; Sat, 18 Feb 2023 23:49:47 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic304-25.consmr.mail.gq1.yahoo.com (sonic304-25.consmr.mail.gq1.yahoo.com [98.137.68.206]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PK5574F30z3vKN for ; Sat, 18 Feb 2023 23:49:47 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1676764185; bh=T+P6IBI2SqS5iInSYaxtVRZmerZTyYrxvY2TGcwljxc=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=kEofEwmJfBj01NH6OkhIeWhDJdeLXXl4H1YRBW02eUuZ1anJLPpmQE7rGenalG1SMHZAHP9pEkvVAq63Aa7TKBPvkq7L06OsG57NKTlVqmpbmXpO0C+hLaCcAYNrRHdCD6rdapAs0eX1b9vwoP98qoq+9Czut/vQ7N1oyVJzIxqr5ygykCaZOAWwSSf15RmZYeD5GY4Yo15gvMAE1sDH6j0sabrjdHaoHxH+7ldtash+tMvyFEkLEUjA6kL3sBGcCId2zCmss3w20AZLwnp4u4i39Vph1XzHAhkaA3D4Z0p8tO7LcgdzhfIK3HLdpLwxNiBP/FY0jDzWJkeNhiaIGw== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1676764185; bh=b4XFchI9Z0NHspa6TNx3obq40y8b5GKYEt7juV/7qIr=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=gbg9qJ4eXG//+Ua4zWlv5Sw/+i451hNh/9y9gZecoim6WCeUrj0z9vvb9WWFMWUnUQfBisMK9pqTU9NJBCVFBMOHwJNBkTlYoBXG5C2OlP002O+KjRwtKmRE3EECADjUR5PoTrHKFW3arbHLnJ7vOLThjo/JMHdIVdlIrkA9NYx15lcdXNlNUzrUVrNkejWJw35jTxd2oO3pMm9/zsgin47KpQY//QqtW75dDlkcVkXX+xnVur1hiiFjNIF6ROqYfqh0iuMwre2nP8gNsCMJurUAeLpfqtNJ1JweqAv5dZfr4PXeSb6L7f5KplrdLLOoNEOtKnpdXOtW3aMLjG25FA== X-YMail-OSG: hnEt6CoVM1m8HrheQdMNNtWgbJR5xeY6lYRfBL5c1p1yWTp1kpBEogeSfJuOLtT kWX7b3gB10DFH3EP69jddrIjCTdE_0Fd47lhXXQpbsk4eBZoXyjBN8OvMIRQiQyU33ZWIj10nZdv Nd_TccU_gsOpT9SLeCpjOeJPkQVII0dZcxcPRYRiJRMjc9cgHUbs2XrBhN5Je0eq2t5T_VXEbbbb k.D0Lox7JHhRYMUaNEamCeOXHcei4MaxgrJjCeEm6se.t6QEwMDZ0xQVOLf3ITKuvUMxKJWHQWNp HR_3ZVF38gyP9lsQ7wBQmwvsUfvYslBQOAH3H2MZz6oOSWuSDuqLTRhTKKe8YUB2OA1mwzdw.1zO 0eX_PV8JcjXkCT4CciEk8uqqas6s5CsP3fSBpZH_uLJLs8KtKJv0wyjwxci5diWZ_KMsVVejARcl XWg6WuzLs2CNTMUf6o8VQ3WbNUtm0.WnEV.AbBzv_3ao1f2an4H7kopK2ozGYY_s9Q.wM18afEVZ sggQuJn.R0ZDp886B3SBM3Jl_zGIf3xz1JI9BjDd6oMa.0GnhM8M6jgmGyt8RUDkVOM80GDjxlY5 _cwBKsvFsvJ0ahVN8Ef8IPLE_ufT3Mtp6C9RPw1kQI95egijLGZq3rT2mFa.DQQB.D.YVnYlpSY1 Qge3iu6LLpi6SBq.UOFOf36NFojzFyFnzdskCM4h20sBmfXxCn.CKaFd86MQZJ.nEqKpUcodRV8W cRINymZQsWTC2edEbe6.T6omGmkvZfEmeJpLmzBMY5tLFqUVpjneBXGUPHf8SGZaT6cPfBlMS7LT J8WA8p3ND95OONNJB5w9rzsB_3NzlXyWgj3.uRrLqvN8ZIcbD1fRomvKRNkI3ptBVGg5ZeRdL.VM 6ovrJbVry2XETEeMKEHmxkQ1SB478RdvVCcVsY6Qy3jybBNZf3ciQZAcMxRWx.mjf3ODcWxwMAnf 0CmpYTJAPcLVlc438vEMVaGh5qyWrEbVkoN4khiwz3lOufe6WjhBhiVxMdExuruozIjK0dCI7nIT m1aUCxmFABe.kHL8aMrFC48x4sIHS7aUO6DAx1Go4Td5Q345qdl_fAMDK6CGYn..kMAyOlSQxM.i 37g6lMNAHykjtsjpwgQy4IcIcVRX2kGS2NxRyv3Nhl7fhY8NNBoLQjf53PJB_XWBuYs3IGem_qCI msQDVVOxrg4pcxGtp3tkVohq8dtRKIqdACaHx3t.G3g36x4.FeAsN7jflhns.Nr37DsNeuDTFEdT loIU8PSDjIGbETk5ec6obXW5WRuINpU8jl8fOHOj5ICVGaJLtfnpkL7IB4SFzh75VT3ow4pGYvaI NvI3hkoZKyANPZB9V2io4.x85e.yu1fwVzu3vove2iss7mMsfqrQT_AkRWp7RlxMdvXg9xh1iXCQ ntvIQzVhH2OSsPYVt0xwD5Hfomg2VQKUSYlhlz0In.7j_nb03pDmRgLfamiuiozGz3Dr5F2erOz3 J.Od9V9S_R0itApwlpnoF12QZIA46M_Y93tgIgLjNfe2Pu1dJtBINK_phW0eTLc_I.V5fJELvT3G Ium4Mj10gOPLQdighxHZHKwlM1Vcbn2ZcZ30vQ1CA.4Ql_HX3ke7tUnz2J2D02s5CtilYsy7Yiv_ oYwih9JmsJqvCrrtJufeKBaIDHuV57VPI46Hcbj6xXPpZN.VazHQDgIPGPZ9qWXs83IbW_qbTUl1 qU8uq53dTeZH8rW5GUMKA4OKTi.v42vZdCbJOdBSss97CVCpr9803e106nwGmfJ3rKuAhVkcCu2y k.2DR6MKb1niM23G2T3tcNLCjV7ZDiHURFw0fRGwklqoi1aHHcZtwUOmgpymK19BCaH_YKaKVFX6 PpvNQqMzeIeMvDUVwetwTKZe1m2NyUJ3KrfMZR5c3FbkD61Fy_CJ1Ul__xoGw0sQ6VixSWhWyHRM vTx5q8Ol0aGzyK.fqO7j1Mv1vIiSmZgOl7QtY2oTyfNuoqZZFVqXO3Ej0ioBGEdMNLCNnRLXy87K bl7YAyEjohYyGKLm2j3LSBcqArO9cWzQPlDm1bp6gLFb_FsBtWbkL0V48znw328Pm1I0CV_4Relj m9y3Lel3sJa4ZtnGrOaLoP2D9YHsbJFDMOy6Qo1cfMtCIHBhyFy2Jf1qwjNT7P7axri_oJw4JsPl xGR1CN51PUF5Xs.6kaq0roBCydZtOv2v0IGBOwNTAR9hWWRke3tNNRR9liPZxM.oZIIX1nAnr2ft SvL4b_mtoMyHEE2ZO_Sg7hSTdnjy2tyFF9IhzVNjqht1t9qk.OBbIKblE2DXOXbC3FIRYoVbJrKQ - X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.gq1.yahoo.com with HTTP; Sat, 18 Feb 2023 23:49:45 +0000 Received: by hermes--production-bf1-57c96c66f6-7qgxj (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID c8f6972ec1109afbc54849f08b95684e; Sat, 18 Feb 2023 23:49:43 +0000 (UTC) Content-Type: text/plain; charset=us-ascii List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\)) Subject: Re: fsck segfaults on rpi3 running 13-stable (and on 14-CURRENT analyzing the same file system that resulted from the 13-STABLE crash) From: Mark Millard In-Reply-To: <20230218210610.GA50074@www.zefox.net> Date: Sat, 18 Feb 2023 15:49:32 -0800 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: <940E58F8-4EC4-4DDB-9428-F6D13ED3132F@yahoo.com> References: <20230214161415.GA28276@www.zefox.net> <20230214183827.GG95670@funkthat.com> <20230214210601.GA28959@www.zefox.net> <20230214232746.GI95670@funkthat.com> <20230215154424.GA34278@www.zefox.net> <20230215190856.GA34665@www.zefox.net> <20230217232537.GA46176@www.zefox.net> <5FFA8C73-4F9B-4633-897C-75368FA9FD4F@yahoo.com> <20230218210610.GA50074@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3731.400.51.1.1) X-Rspamd-Queue-Id: 4PK5574F30z3vKN X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Feb 18, 2023, at 13:06, bob prohaska wrote: > On Fri, Feb 17, 2023 at 04:23:59PM -0800, Mark Millard wrote: > [huge snip] >> Looks like that is one of the messages for problems >> fsck_ffs does not attempt to deal with (probably for >> good reasons in each case/context). > > Since there wasn't much to lose I tried deleting > the bad inodes using fsdb clri and re-running fsck. > > After maybe a dozen cycles fsck reported the filesystem > clean and, to a superficial inspection, intact. > > The disk rebooted, ran git reset --hard and is now running > buildworld. Fingers and toes are now fully crossed 8-) > > Is it possible to continue updating the -current Pi3 using > git while preserving the hand-applied changes to /sbin/fsck? Making some presumptions about your source path ( /usr/src/ ) . . . (Beware that I do not use git pull but do fetch and merge --ff-only separately. So I'm guessing some below.) # git -C /usr/src/ status (Any surprises? Deal with such. YOu might want to restore sources that you know you will just want the newer official content of.) # git -C /usr/src/ stash push # git -C /usr/src/ pull # git -C /usr/src/ stash apply AT THIS POINT IT MIGHT INDICATE CONFLICTS IF THE fsck_fft SOURCE HAS BEEN UPDATED. There is more to it if/when that happens. You might choose to restore the official source, for example. I'm not listing explicit steps for any alternatives. Sometime later when things are known okay but likely before the next stash push: # git -C /usr/src/ stash drop I'll note that you could first "cd /usr/src/" instead of using "-C /usr/src/" on the command lines. > Simply running git pull results in complaints about unstaged > changes. IIRC, subversion didn't care. > > [another huge snip} > > >> >> Beyond that, things with floating-point use in >> multi-threading contexts looks to be significantly >> broken in main [so: 14] for now. (This was involved >> in your FreeBSD crash based on the the backtrace >> showed.) >> >> If you try to set up another armv7 context, I suggest, >> for now, staying before: >> >> commit 6926e2699ae55080f860488895a2a9aa6e6d9b4d >> Author: Kornel Dul??ba >> AuthorDate: 2023-02-04 12:59:30 +0000 >> Commit: Kornel Dul??ba >> CommitDate: 2023-02-04 19:21:43 +0000 >> >> arm: Add support for using VFP in kernel >> >> This would be until a list of issues have been >> addressed. I've reported how to produce 3 >> distinct failures, 2 of which hit KASSERT >> panics, and the other one is for ending up with >> floating-point values from the wrong thread >> (but same process). More may be identified >> and fixed before things generally work again >> for main for armv7 FreeBSD. > > The relative merits of aarch64 vs armv7 are a bit > muddy from my point of view. The only real objection > to aarch64 on the Pi3 is running out of memory > during buildworld. Using armv7 on an RPi3B runs out of RAM+SWAP sooner because it only allows a much smaller swapspace due to the armv7 code's addressing limitations, as I understand. (It also ends up mistuned at a much smaller swap space size.) So to allow (near) maximum RAM+SWAP for a reasonably tuned context: use aarch64 on RPi3B's. > On a "production" machine that > happens infrequently and needn't be fast, so -j2 > solves the problem. I was interested in trying to > use armv7 on the Pi3, but unless it works "out of > the box" it's probably more trouble than benefit. All sufficiently recent main native-armv7 kernels are broken because of the VFP handling changes, at least for hardware with VFP. Your original report was for the buildworld failure on a RPi2. Was that v1.1 so armv7-only (no aarch64 present)? The original backtrace indicates a problem that is tied to the armv7 kernel new VFP handling that is not working well yet. That would also apply to a RPi3B using an armv7 kernel. FYI: I did my how-to-reproduce investigations on a OrPi+2e armv7, not on a RPi* . === Mark Millard marklmi at yahoo.com