From nobody Mon Mar 18 06:43:06 2024 X-Original-To: bugs@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 4Tylff1fqhz5CmVk for ; Mon, 18 Mar 2024 06:43:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Tylff0WMZz4SbR for ; Mon, 18 Mar 2024 06:43:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1710744186; a=rsa-sha256; cv=none; b=eiudqem1rrDEGEpu5cyxTCab25v7QHLAFamHH57yR9pHhRWnDKfcLKcYAFoNnzy0mctmrn A11DJs9gOtsMfAxd3BZsXCs+OqWyRhQNIKUKHVG3OqlW/2JzgEoh3kAUoNaQ9EhlO3dbB9 /89wTKrrJzhjzrkrHO0WoILgRbzpmP2j+0KitsXaHfA95bRVHltKZ+XP2wBQjW23M2lJud sRoyh6cdlIVDIVcTF3xY2OFwS75iUH5ex+PgWgpLGozmwVsDulFpxKstiTZab9y6C2TzSo HlbxvkkooxccUPJUUYPKQJ102T3BCUeGzhrWcpaON8K/dtd5zMweMYuoIny3Cg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1710744186; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=jlcwfkSx3hD45EOxjatK1yvIAppy9shqoUz1yWEdXx4=; b=Yd8Kqeu/Kx3SHOpvodg9mhAq1IG9to78fMPOzr8m5euTiZVv+FQx3XLYF0KNYGqG9n7wTB DMTH9w095jVyrneJhyGcZzElRvT4MLvZaQ/njqCJyGO2WC5ycJeuyjdr86VVhKoDr+Ctbj LzTXuwmV0CFiZOAo7L8cojO7n+He5VkaDvAw0ZN2Br6rwWM1+oIj4NHOITY6xxKa8+7cFv KHBfCJQaePUbrb7UTK0CrfhyHG26LYfvDp+a1FlHaXejEyhfWGuvmPb3NWhmsMqtKY9bmD HoxCQu9q0+dDYFXfk058YR16IPz3JjqkUqfMJCoB3/fEuB00JvRTCcPQxMFZpw== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Tylff02sDz1Brh for ; Mon, 18 Mar 2024 06:43:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 42I6h5Qa058872 for ; Mon, 18 Mar 2024 06:43:05 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 42I6h5Go058871 for bugs@FreeBSD.org; Mon, 18 Mar 2024 06:43:05 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 277389] Reproduceable low memory freeze on 14.0-RELEASE-p5 Date: Mon, 18 Mar 2024 06:43:06 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 14.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D277389 --- Comment #34 from Mark Millard --- FYI: With vfs.nullfs.cache_vnodes=3D0 I instead got the "failed to reclaim memory" type of failure, losing control because of what had been killed. So the nullfs VNODE caching is not a fundamental part of the problem. nullfs VNODE caching can contribute to variability in the failure details since it changes the memory use pattern, or so it appears. --=20 You are receiving this mail because: You are the assignee for the bug.=