From owner-freebsd-x11@freebsd.org Mon Oct 12 06:42:16 2020 Return-Path: Delivered-To: freebsd-x11@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 350EA42DF5C for ; Mon, 12 Oct 2020 06:42:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4C8py00BFNz3VVZ for ; Mon, 12 Oct 2020 06:42:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 064D942DF5B; Mon, 12 Oct 2020 06:42:16 +0000 (UTC) Delivered-To: x11@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0610842DF5A for ; Mon, 12 Oct 2020 06:42: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 "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C8pxz5cvCz3VPW for ; Mon, 12 Oct 2020 06:42:15 +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 9F47E87CF for ; Mon, 12 Oct 2020 06:42:15 +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 09C6gF4D033277 for ; Mon, 12 Oct 2020 06:42:15 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 09C6gFF5033276 for x11@FreeBSD.org; Mon, 12 Oct 2020 06:42:15 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: x11@FreeBSD.org Subject: [Bug 250226] graphics/drm-fbsd12.0-kmod: massive memory leak Date: Mon, 12 Oct 2020 06:42:15 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: bennett@sdf.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: x11@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: cc 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 MIME-Version: 1.0 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Oct 2020 06:42:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250226 Scott Bennett changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bennett@sdf.org --- Comment #1 from Scott Bennett --- Your description matches that of a collection of bugs present in 11.2 = to 11.4 and 12.x that others began complaining of on other lists within days of the release of 11.2. I have complained on the x11 and stable lists about them a few times this year because they are still a problem and because the FreeBSD developers have not addressed them. Over time others have found a number of sysctl workarounds, and I have found a few others and have accumulated seve= ral that, in combination, allow me to keep my system usable for weeks at a time, rather than a day to three or four days. They do not fix the bugs, however. One glaring bug is that vm.max_wired is now ignored by the kernel. Wi= th vm.max_wired=3D786432 I have seen the amount of real memory tied up in page= fixing (a.k.a. "wiring" in Berkeley dialect) exceed 6700 MB on an 8 GB machine. My view is that vm.max_wired should either be honored or removed from the source code tree. It is worth noting that ZFS ARC does not appear to be to blame. It ra= rely exceeds the quasi-limit of vfs.zfs.arc_max by more than ~200 MB. The following sysctl variables, when set to very increased values from their default values, seem to help keep a system able to do work or to be recover= able to such condition without the necessity of a reboot: vm.v_free_min, vm.pageout_wakeup_thresh, vm.pageout_oom_seq. Reducing the value of vfs.zfs.arc_max may also help, depending upon your system's configuration. Also, be aware that maintaining a large ccache directory tree to use with "= make buildworld", "make buildkernel", or "portmaster -a" will save you a great d= eal of time, but will also hasten the day when a reboot will be necessary. My advice for those cases is to keep CCACHE_DIR and, for buildworld and buildkernel, /usr/ports or other DESTDIR, in a file system that can be easi= ly unmounted and, perhaps, remounted in order to free up its associated buffer cache memory (most of which should have been pagefreed immediately upon completion of an I/O operation long since anyway). There is not enough pagefreeing being done by the kernel anymore that used to be done at appropriate times or so it appears. Also, if you use ZFS, it will help to reduce the l= imit on ZFS ARC size by setting vfs.zfs.arc_max. Note, however, that that is me= rely a crutch to give you more operational time before you have to intervene manually. FWIW, my speculation is that this mess of bugs of the kind that should have vanished from FreeBSD by release 1.x was introduced into 13-CURRENT and lat= er backported into 11.2 and 12.x. (I am aware that it affects 12.1, but I do = not know whether 12.0 was affected. I currently am running 11.4-STABLE at r364= 474. I do not think these bugs have much, if anything, to do with the graphics stack, but rather appear to be VM subsystem bugs. My system still suffers from th= em, even though there is no safe-to-use graphics support for a Radeon HD 5770 c= ard, and therefore my system is not running X11. :-( --=20 You are receiving this mail because: You are the assignee for the bug.=