From owner-freebsd-bugs@freebsd.org Wed Jan 2 07:44:46 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 83E51143961E for ; Wed, 2 Jan 2019 07:44:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1B25480058 for ; Wed, 2 Jan 2019 07:44:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id D2C71143961D; Wed, 2 Jan 2019 07:44:45 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B04B3143961C for ; Wed, 2 Jan 2019 07:44:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3964680056 for ; Wed, 2 Jan 2019 07:44:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 801CC103DE for ; Wed, 2 Jan 2019 07:44:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x027iiOv061858 for ; Wed, 2 Jan 2019 07:44:44 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x027iixJ061857 for bugs@FreeBSD.org; Wed, 2 Jan 2019 07:44:44 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 234559] memory reporting inconsistency 12-STABLE vs. 11-STABLE Date: Wed, 02 Jan 2019 07:44:44 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: freebsd@oldach.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: 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-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jan 2019 07:44:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234559 Bug ID: 234559 Summary: memory reporting inconsistency 12-STABLE vs. 11-STABLE Product: Base System Version: 12.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: freebsd@oldach.net Created attachment 200695 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D200695&action= =3Dedit memory graph I have recently upgrade from 11-STABLE to 12-STABLE. While the total memory (active+inactive+laundry+wired+cache+free) in 11-STABLE was fixed, this sum seems to be somewhat floating in 12-STABLE. Occasionally it even appears to= be above physical memory! Please see attached graph (similar to what is produced by munin): The pictu= re is covering the last 14 days with the oldest data to the left; reboot to 12-STABLE was last Sunday afternoon (where the gap is visible). Before the upgrade (running 11-STABLE) there is almost a flat total, after the upgrade (running 12-STABLE) the total is jumpy. Also the top(1) output is weird on this machine with 4G DRAM: # top -n | fgrep Mem Mem: 269M Active, 2083M Inact, 15M Laundry, 700M Wired, 336M Buf, 1073M Free # echo $((269+2083+15+700+1073)) 4140 # Clearly this cannot be just a rounding issue - it appears the stats counters are not updated appropriately in 12-STABLE: # sysctl -a vm.stats.vm | fgrep _count vm.stats.vm.v_cache_count: 0 vm.stats.vm.v_laundry_count: 3926 vm.stats.vm.v_inactive_count: 533266 vm.stats.vm.v_active_count: 76185 vm.stats.vm.v_wire_count: 179345 vm.stats.vm.v_free_count: 267048 vm.stats.vm.v_page_count: 980845 # echo $((0+3926+533266+76185+179345+267048)) 1059770 # echo $(($(sysctl -n vm.stats.vm.v_page_size)/1024)) 4 # echo $((1059770*4)) 4239080 # --=20 You are receiving this mail because: You are the assignee for the bug.=