From nobody Thu Nov 28 18:16:16 2024 X-Original-To: freebsd-current@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 4Xzkz64RSzz5f4bG; Thu, 28 Nov 2024 18:16:34 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xzkz63gg7z4fMy; Thu, 28 Nov 2024 18:16:34 +0000 (UTC) (envelope-from scf@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1732817794; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=DvxOhPNGi/OvPPZ+dkB4Is8Cfmm8yLU56rHq7zAXA5o=; b=KRUFIxmU9Cap4NnzEqd0CqUsYWqSAHn3MsQytr0q9YfIjphH7383HlJ5Phsr3BSWm4jNsC HzXfbJNqvJeqgSympoQiLItJTWgQAyljpXXZXI1aIAM5qijOCTezcl8wY4T+TMS0EcnyQE uBWCy1VraXy2NGcC96IkbQW3tY+dbQXB1oh7HhVulLD6/SlHJgbrcb+bcYp2wuAA0L5wgB SY+hGLc0mSQQOTGbXwlmVTn+0I6U3WV7ugmm4ynilYQcT72wosuErpa2rampnFk7uCQvjE Aum7qLJpH+E2gg0umRcCVXJ0gh8E8FQ5uMRyg4XoT4Dd2PElapGXUkudsHbT8w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1732817794; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=DvxOhPNGi/OvPPZ+dkB4Is8Cfmm8yLU56rHq7zAXA5o=; b=V/ep+BfTkCqPP8Spzs4xLGRdAN5hdYKguUtfB+eCpxKvX3nI7EW4R/vyjkY6DUqRlufyOG PLSdWPfdchwpaMBbJk/Radbdhxx2cpNzFgtmL82z8coBeOOePBqrXB/24tMObZcV4BB/U2 nquqdPNYvMp0yVL0QHbjlGl36CqeSkmCx8xnt/9DjJTUal+oP6hCARuPK/5dEfxhhdNNo2 MSmte12T9Ljkp0OEC2Mo6DO8/kHtNzGbs//v+GO0CJoIXDSh3RvZLDLECjC1K+yHbaJVuF Tkx4zuDvba6InOuBAzQC1giCt4EeA32NHnBo68QJtJvZZ6c/QPRk49E+QtcTMQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1732817794; a=rsa-sha256; cv=none; b=ZaYI/2jIgw8J/BSdGNo4HeEJM89syWO179lH2AE5Qp90ZRhjLvSnX6oSBKXSUum+7TtoTb uTa15lR7tqdGz/74YRn/zRPKXs0inPB7vRGZUKPyYhfLVguB6LwhRX0uHP22s3JqN7smzp YG0tye1NoPIKApe4PDUzxHICDj3gQUJwxm+C7BSvqMQfab7UI6OrUZEdKaNvxusg4E5XBG xxBFchKDlKGCb6p54H0eVL68riz9VsWrQnhS86Rqka26NDIzYh2HEz0dtnoqEi5ISLQ/8l u0jWTgSodPXUsmy38LZ+Jennuyxg3PCq2z87tKiJKzGyYvPgE14+0WOHjJR3nA== Received: from thor.farley.org (1609341-v107.1360-static.crmlinaa.metronetinc.net [104.254.222.35]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: scf/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Xzkz62GLSz16GT; Thu, 28 Nov 2024 18:16:34 +0000 (UTC) (envelope-from scf@FreeBSD.org) Date: Thu, 28 Nov 2024 13:16:16 -0500 (EST) From: "Sean C. Farley" To: freebsd-ports@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: port binary dumping core on recent head in poudriere [tmpfs corruptions involving blocks of zeros that should not be all zeros] In-Reply-To: <0690CFB1-6A6D-4B63-916C-BAB7F6256000@yahoo.com> Message-ID: <813bef1e-0189-27b2-9ee1-8ebb57a82296@FreeBSD.org> References: <7c9c3cf5-bbd1-4642-8d04-33aa07a4db02@madpilot.net> <9df256a8-c6ed-46d9-b955-fc2657c12d36@madpilot.net> <5c502054-7353-4a1e-8350-c403482e9c0d@madpilot.net> <3127C3BA-FC93-4636-ADDB-89518DE9C60D@FreeBSD.org> <86ed2zsp6l.fsf@ltc.des.dev> <5f24a570-26e0-4c0a-817f-591a234fd07b@madpilot.net> <5918C6A1-8FDB-40CA-8C86-EB7B7BE75A2E@yahoo.com> <86ed2zc8r5.fsf@ltc.des.dev> <45098ccf-4dc6-426c-849a-c923805d6723@madpilot.net> <38658C0D-CA33-4010-BBE1-E68D253A3DF7@FreeBSD.org> <1004a753-9a3c-4aa2-bfa8-4a0c471fe3ea@madpilot.net> <0690CFB1-6A6D-4B63-916C-BAB7F6256000@yahoo.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/mixed; BOUNDARY="3279119474-871193679-1732816971=:34935" Content-ID: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --3279119474-871193679-1732816971=:34935 Content-Type: text/plain; CHARSET=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT Content-ID: On Mon, 25 Nov 2024, Mark Millard wrote: > On Nov 25, 2024, at 18:05, Mark Millard wrote: > >> Top posting going in a different direction that >> established a way to control the behavior in my >> context . . . > > For folks new to the discoveries: the context here > is poudriere bulk builds, for USE_TMPFS=all vs. > USE_TMPFS=no . My test context is amd64 on a > 7950X3D system with 192 GiBytes of RAM. Others have > other contexts, including an Intel system. I have been seeing some odd behavior from Firefox as well as with poudriere builds on my system. Both of which are touching a tmpfs system as I have setup /tmp as tmpfs, which Firefox uses, and USE_TMPFS=all. The system has been an experiment, for me, with undervolting. I have been attributing any flakiness to the undervolting, but I have reduced that a lot while the instability has been consistent as in it has stayed rare. I cannot tell how many times I have run memtest86 on this system. System setup: - FreeBSD 14.2-STABLE - i7-14700K (latest BIOS which *should* fix Intel power-related bugs) - 128 GiB RAM - ZFS (mirrored drives) - 2 encrypted swap partitions (64 GiB each, lightly used) - Lightly undervolted (-0.06 offset to Global Core SVID Voltage) - /tmp is tmpfs - ${HOME}/.cache is tmpfs - Poudriere: - USE_TMPFS=all - ccache - jail version in sync with host - /usr/ports is mounted with nullfs I have wondered if it was swap-related, but recently I noticed a build failure with games/veloren-weekly where swap was available but zero bytes were used. The system was under little load at the time so less chance of undervolting being an issue. Build failure: ----------------------------- portpicker = { path = '/wrkdirs/usr/ports/games/veloren-weekly/work/portpicker-rs-df6b37872f3586ac3b21d08b56c8ec7cd92fb172' } ===> Updating Cargo.lock error: checksum for `windows_x86_64_msvc v0.42.2` changed between lock files this could be indicative of a few possible errors: * the lock file is corrupt * a replacement source in use (e.g., a mirror) returned a different checksum * the source itself may be corrupt in one way or another unable to verify that `windows_x86_64_msvc v0.42.2` is the same as when the lockfile was generated *** Error code 101 ----------------------------- Restarting the build finished successfully. >> I changed USE_TMPFS=all to USE_TMPFS=no : >> >> USE_TMPFS=all gets the failure *snip* >> vs. >> USE_TMPFS=no works just fine >> >> So it is a FreeBSD system error associated with >> use of tmpfs . > > Recent work on tmpfs includes: > > Mon, 09 Sep 2024 > • git: 8fa5e0f21fd1 - main - tmpfs: Account for whiteouts during rename/rmdir Jason A. Harmening > Fri, 04 Oct 2024 > • git: 75734c4360fc - main - tmpfs: check residence in data_locked Doug Moore > Sun, 13 Oct 2024 > • git: ec22e705c266 - main - tmpfs: remove duplicate flags check in tmpfs_rmdir Alan Somers > Thu, 24 Oct 2024 > • git: db08b0b04dec - main - tmpfs_vnops: move swap work to swap_pager Doug Moore > > swap_pager (given the reference to it above): > > Tue, 08 Oct 2024 > • git: d0b225d16418 - main - swap_pager: use iterators in swp_pager_meta_build Doug Moore > Fri, 11 Oct 2024 > • git: 1107834090be - main - swap_pager: swapoff detecting object death Doug Moore > Thu, 24 Oct 2024 > • git: 34951b0b9e78 - main - swap_pager: move scan_all_shadowed, use iterators Doug Moore > • git: 02e85d1c8a41 - main - swap_pager: fix assert in seek_data Doug Moore > • git: faa9356f97d2 - main - swap_pager: fix seek_hole assert Doug Moore > Sat, 26 Oct 2024 > • git: 39f6d1e7f835 - main - swap_pager: iter in haspage, lookup, getpages Doug Moore > Wed, 13 Nov 2024 > • git: d11d407aee48 - main - swap_pager: Ensure that swapoff puts swapped-in pages in page queues Mark Johnston > > I do not know at this time when the corruptions started. The > above is only suggestive. Thank you for listing those. I need to find some time to look over those changes although I am no kernel guru by a long shot. However, I see now that it looks like much more knowledgeable people are already looking on the current mailing list at the issue. Sean -- scf@FreeBSD.org --3279119474-871193679-1732816971=:34935--