From nobody Sun Nov 03 00:45:55 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 4XgwrP4BLTz5b5js for ; Sun, 03 Nov 2024 00:45:57 +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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XgwrN2hHfz4YG2 for ; Sun, 3 Nov 2024 00:45:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1730594756; 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=4a5rEbE3RCmz4Eg6kP9SCX4J+/4nEeFz1H7GG0V1stY=; b=r6tSTG0BbA/Zr0W+6x6P/qAAWZ9nIkNzHWGqsJXs4U48JWoe4G7lOKPetNQNXh66G7Gcj/ BKEIYZdv605IuuPYwEU3xPKsRwFkcAqVh+bcPAjCfrRHGJNAMsdhMTZWMaWZmXWou8/mlz 2eX6mAXBDhpABQgdx9i5B0dpHJ8LFmUa9BrX0tQzRzvY7O49TiqGwaGlyac3VmipeyRX6f 1ER0VbhqyUx2Mm7/kgMan4lDcXjSmXI9p+zZQn+jno1V7PMaNkWH8UYB6sphbKwhZr13HA xLFRoMsQ2z6ESjGPXbJR5z/NMcu4fU9Av9MwFlU9U/Zmjr0T17NYv5kKrGpQow== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1730594756; a=rsa-sha256; cv=none; b=CjeWrpyeF3iVWfCGuVDRtvaMIBiprK38iBut1w8u2jPdl9cdB9IZ4Ea5H3muVyIh8U0WwA aRwRmN6JfNxzVL7J+zazCvn0UPaQojtXYxffiAM67BKxrydVJGW/uxpoW9WtJaDBFDFvJr NiaRExeeGSgijksY9NG0fY/f/gCxwm6HvPqRw7pgArFTcWkfd1viAJ/KP3/ve39gWkKyzG FZAKFstsOjkqL1NXvkI7SDamNlyTS2+75NgovBGvZkuoVZ1pbJOsmMM3aX3lrVI2fxyA22 Qq9ev/eSOYmKuDyC3vNCdkA1EVQlFJSAeHDVqLKzMsP/ymny0JrsT40GLCZAUQ== 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 4XgwrN2HnCzRvl for ; Sun, 3 Nov 2024 00:45:56 +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 4A30julh015338 for ; Sun, 3 Nov 2024 00:45:56 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 4A30jujQ015337 for bugs@FreeBSD.org; Sun, 3 Nov 2024 00:45:56 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: Sun, 03 Nov 2024 00:45:55 +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 #42 from Mark Millard --- I just checked a more recent PkgBase kernel & world based system on the 32 GiByte Windows Dev Kit 2023 without swap space being enabled. USB3 UFS boot media with separate USB3 ZFS media imported later. (Each: U.2 adapter to large Optane media.) The read activity quickly got OOM activity. (The iozone.DUMMY.* files existed from a prior boot and were reused.) My personal variant of top showed: Mem: 132568Ki Active, 250168Ki Inact, 30802Mi Wired, 248328Ki Buf, 116268Ki Free, 132568Ki MaxObsActive, 30802Mi MaxObsWired, 30932Mi MaxObs(Act+Wir+Ln= dry) ARC: 28008Mi Total, 1963Mi MFU, 25813Mi MRU, 79723Ki Header, 158558Ki Other 26405Mi Compressed, 27557Mi Uncompressed, 1.04:1 Ratio as of when it was killed. Note that "Max(imum)Obs(erved)..." figures ones that I added and I changed the number/units output style: more significant digits and explicitly powers of 1024 based. Note the "30802Mi Wired" and "ARC: 28008Mi Total" and "25813Mi MRU" and "26405Mi Compressed": the figures are not staying in reasonable bounds for the RAM available. This was from: # iozone -w -i 1 -l 512 -r 4k -s 1g The kills left me without any normal access, including via the (plain text) console and via ssh. But I could break into ddb via the console keyboard. . . . Nov 2 16:08:16 aarch64-main-pbase kernel: pid 4639 (top), jid 0, uid 0, was killed: failed to reclaim memory Nov 2 16:08:33 aarch64-main-pbase kernel: pid 4640 (sshd), jid 0, uid 0, w= as killed: failed to reclaim memory Nov 2 16:08:46 aarch64-main-pbase kernel: pid 4630 (sshd), jid 0, uid 0, w= as killed: failed to reclaim memory Nov 2 16:08:59 aarch64-main-pbase kernel: pid 4353 (ntpd), jid 0, uid 0, w= as killed: failed to reclaim memory Nov 2 16:09:12 aarch64-main-pbase kernel: pid 4515 (sh), jid 0, uid 0, was killed: failed to reclaim memory Nov 2 16:09:24 aarch64-main-pbase kernel: pid 4085 (devd), jid 0, uid 0, w= as killed: failed to reclaim memory Nov 2 16:09:35 aarch64-main-pbase kernel: pid 4507 (login), jid 0, uid 0, = was killed: a thread waited too long to allocate a page Nov 2 16:09:37 aarch64-main-pbase kernel: pid 4443 (mountd), jid 0, uid 0,= was killed: failed to reclaim memory Nov 2 16:09:56 aarch64-main-pbase kernel: pid 4316 (rpcbind), jid 0, uid 0, was killed: failed to reclaim memory Nov 2 16:10:09 aarch64-main-pbase kernel: pid 127 (adjkerntz), jid 0, uid = 0, was killed: failed to reclaim memory Nov 2 16:10:21 aarch64-main-pbase kernel: pid 3887 (dhclient), jid 0, uid = 65, was killed: failed to reclaim memory Nov 2 16:10:31 aarch64-main-pbase dhclient[3778]: connection closed Nov 2 16:10:34 aarch64-main-pbase kernel: pid 3781 (dhclient), jid 0, uid = 0, was killed: failed to reclaim memory Nov 2 16:10:41 aarch64-main-pbase dhclient[3778]: exiting. Nov 2 16:10:47 aarch64-main-pbase kernel: pid 3778 (dhclient), jid 0, uid = 0, was killed: failed to reclaim memory Nov 2 16:10:59 aarch64-main-pbase kernel: pid 4513 (getty), jid 0, uid 0, = was killed: failed to reclaim memory Nov 2 16:11:12 aarch64-main-pbase kernel: pid 4512 (getty), jid 0, uid 0, = was killed: failed to reclaim memory Nov 2 16:11:25 aarch64-main-pbase kernel: pid 4510 (getty), jid 0, uid 0, = was killed: failed to reclaim memory Nov 2 16:11:36 aarch64-main-pbase kernel: pid 4508 (getty), jid 0, uid 0, = was killed: a thread waited too long to allocate a page Nov 2 16:11:38 aarch64-main-pbase kernel: pid 4514 (getty), jid 0, uid 0, = was killed: failed to reclaim memory Nov 2 16:11:50 aarch64-main-pbase kernel: pid 4511 (getty), jid 0, uid 0, = was killed: failed to reclaim memory Nov 2 16:12:01 aarch64-main-pbase kernel: pid 4509 (getty), jid 0, uid 0, = was killed: a thread waited too long to allocate a page Nov 2 16:12:03 aarch64-main-pbase kernel: pid 4037 (moused), jid 0, uid 0,= was killed: failed to reclaim memory Nov 2 16:12:16 aarch64-main-pbase kernel: pid 4445 (nfsd), jid 0, uid 0, w= as killed: failed to reclaim memory Nov 2 16:12:28 aarch64-main-pbase kernel: pid 4446 (nfsd), jid 0, uid 0, w= as killed: failed to reclaim memory Nov 2 16:12:41 aarch64-main-pbase kernel: pid 5173 (iozone), jid 0, uid 0,= was killed: failed to reclaim memory Nov 2 16:12:54 aarch64-main-pbase kernel: pid 5172 (iozone), jid 0, uid 0,= was killed: failed to reclaim memory Nov 2 16:13:03 aarch64-main-pbase kernel: ugen0.6: at usbus0 (disconnected) Nov 2 16:13:03 aarch64-main-pbase kernel: ums0: at uhub3, port 2, addr 5 (disconnected) Nov 2 16:13:03 aarch64-main-pbase kernel: ums0: detached Nov 2 16:13:05 aarch64-main-pbase kernel: ugen0.6: at usbus0 Nov 2 16:13:05 aarch64-main-pbase kernel: ums0 on uhub3 Nov 2 16:13:05 aarch64-main-pbase kernel: ums0: on usbus0 Nov 2 16:13:05 aarch64-main-pbase kernel: ums0: 3 buttons and [XYZ] coordinates ID=3D0 Nov 2 16:13:06 aarch64-main-pbase kernel: pid 5171 (iozone), jid 0, uid 0,= was killed: failed to reclaim memory Nov 2 16:13:19 aarch64-main-pbase kernel: pid 5170 (iozone), jid 0, uid 0,= was killed: failed to reclaim memory Nov 2 16:13:32 aarch64-main-pbase kernel: pid 5169 (iozone), jid 0, uid 0,= was killed: failed to reclaim memory Nov 2 16:13:44 aarch64-main-pbase kernel: pid 5168 (iozone), jid 0, uid 0,= was killed: failed to reclaim memory Nov 2 16:13:57 aarch64-main-pbase kernel: pid 5167 (iozone), jid 0, uid 0,= was killed: failed to reclaim memory . . . Nov 2 16:43:09 aarch64-main-pbase kernel: pid 4986 (iozone), jid 0, uid 0,= was killed: failed to reclaim memory Nov 2 16:43:22 aarch64-main-pbase kernel: pid 4985 (iozone), jid 0, uid 0,= was killed: failed to reclaim memory Nov 2 16:43:34 aarch64-main-pbase kernel: pid 4984 (iozone), jid 0, uid 0,= was killed: a thread waited too long to allocate a page Nov 2 16:43:35 aarch64-main-pbase kernel: pid 4983 (iozone), jid 0, uid 0,= was killed: failed to reclaim memory Nov 2 16:43:47 aarch64-main-pbase kernel: pid 4982 (iozone), jid 0, uid 0,= was killed: failed to reclaim memory Nov 2 16:43:58 aarch64-main-pbase kernel: pid 4981 (iozone), jid 0, uid 0,= was killed: a thread waited too long to allocate a page Nov 2 16:43:58 aarch64-main-pbase kernel: ugen0.6: at usbus0 (disconnected) Nov 2 16:43:58 aarch64-main-pbase kernel: ums0: at uhub3, port 2, addr 5 (disconnected) Nov 2 16:43:58 aarch64-main-pbase kernel: ums0: detached Nov 2 16:43:59 aarch64-main-pbase kernel: ugen0.6: at usbus0 Nov 2 16:43:59 aarch64-main-pbase kernel: ums0 on uhub3 Nov 2 16:43:59 aarch64-main-pbase kernel: ums0: on usbus0 Nov 2 16:43:59 aarch64-main-pbase kernel: ums0: 3 buttons and [XYZ] coordinates ID=3D0 Nov 2 16:44:00 aarch64-main-pbase kernel: pid 4980 (iozone), jid 0, uid 0,= was killed: failed to reclaim memory . . . Definitely a denial of service context. For reference: # uname -apKU FreeBSD aarch64-main-pbase 15.0-CURRENT FreeBSD 15.0-CURRENT main-n273174-8b2e7da70855 GENERIC-NODEBUG arm64 aarch64 1500026 1500026 So this is after the fix to the system accounting of laundry to span both swappable and unswappable for the sysctl that top is based on for such. --=20 You are receiving this mail because: You are the assignee for the bug.=