From nobody Sun Jul 25 16:46:16 2021 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 D484312D02D2 for ; Sun, 25 Jul 2021 16:46:16 +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 4GXppw5NYRz3Ngx for ; Sun, 25 Jul 2021 16:46:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 8E5EA26FBC for ; Sun, 25 Jul 2021 16:46:16 +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 16PGkGO8073681 for ; Sun, 25 Jul 2021 16:46:16 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 16PGkGiB073680 for bugs@FreeBSD.org; Sun, 25 Jul 2021 16:46:16 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 257314] FBSD 13 crash after some KDE parts crash supposing out of swap space Date: Sun, 25 Jul 2021 16:46:16 +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: 13.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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D257314 --- Comment #31 from Mark Millard --- (In reply to Michael from comment #30) > in some way my pC became unusable, it's like > slow motion all reactions on mouse or keyboard > come after minutes (no exageration) This is normal if the free RAM stays low and the system is paging extensively to media that is not fast for the purpose. Those are kinds of conditions that can also eventually lead to the kills. One of the tunables that I've indicated delays the kills, making the conditions last longer in order to avoid the kills. But, until I can see the output lines of the patched kernel I can not tell which of the 4 conditions are occurring. So, without that output I've basically no chance to be of more help. Also, as I've indicated before, we would need to see top output from shortly before the kills happen to see which processes are using what memory at the time. Looking at top output after the kills start does no good. As for: Solaris: WARNING: ignoring tunable zfs_arc_min (using 0 instead) Solaris: WARNING: ignoring tunable zfs_arc_min (using 0 instead) There is: /* Valid range: 32M - */ if ((zfs_arc_min) && (zfs_arc_min !=3D arc_c_min) && (zfs_arc_min >=3D 2ULL << SPA_MAXBLOCKSHIFT) && (zfs_arc_min <=3D arc_c_max)) { arc_c_min =3D zfs_arc_min; arc_c =3D MAX(arc_c, arc_c_min); } WARN_IF_TUNING_IGNORED(zfs_arc_min, arc_c_min, verbose); As far as I can tell this happens from having too little RAM for the overall configuration, so that 32M is not even reasonable. (But I'm no ZFS tuning expert.) With defaults, as I remember, the standard recommendation is to have at least 8 GiBytes of RAM for ZFS. For less, some ZFS tuning expertise is needed (that I do not have). If you have done some zfs tuning, you should add notes to the bugzilla about what your settings are and what the machine has for RAM and such. Someone with ZFS tuning expertise might comment based on such information. --=20 You are receiving this mail because: You are the assignee for the bug.=