From nobody Fri Jul 23 20:56:49 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 82F4F12AE08A for ; Fri, 23 Jul 2021 20:56:49 +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 4GWhSx385zz3Ch5 for ; Fri, 23 Jul 2021 20:56:49 +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 54FE02B861 for ; Fri, 23 Jul 2021 20:56:49 +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 16NKune6078353 for ; Fri, 23 Jul 2021 20:56:49 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 16NKunV0078352 for bugs@FreeBSD.org; Fri, 23 Jul 2021 20:56:49 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: Fri, 23 Jul 2021 20:56:49 +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 #23 from Mark Millard --- (In reply to Michael from comment #20) > all messages I pasted, I copied in original sequence starting with first = occurrence in log Of which exact type of message? If it was a kill message, then it was already too late to see the RAM use around the time just before the kill was done. One of the problems with trying to monitor the system is that, for example, large changes in the amount of attempted memory use (and RAM use) being attempted could occur multiple times per second. But if such happens, it is difficult to observe usefully to even detect that such is the type of context. Some folks try having top running in a loop, sleeping between runs, logging to a file so there is at least a history-sequence (presuming this does not end up killed before the file system updates). A similar point goes for gstat output. But these also end up competing with the paging/swapping activity for I/O resource use. So far as I can tell, the best next evidence that we could get is the patched-in messaging about exactly which condition initiated each kill. The patch does not attempt to prevent the kills or make things work for you, but just reports what condition in the kernel lead to each. --=20 You are receiving this mail because: You are the assignee for the bug.=