From owner-freebsd-current@freebsd.org Thu Jan 9 09:59:20 2020 Return-Path: Delivered-To: freebsd-current@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 A86FA22FADF for ; Thu, 9 Jan 2020 09:59:20 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 47thRD2CS1z3NxG for ; Thu, 9 Jan 2020 09:59:20 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: by mailman.nyi.freebsd.org (Postfix) id 4BBC022FADE; Thu, 9 Jan 2020 09:59:20 +0000 (UTC) Delivered-To: current@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 4B82022FADD for ; Thu, 9 Jan 2020 09:59:20 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47thRC2PKHz3NxF for ; Thu, 9 Jan 2020 09:59:18 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (v-critter.freebsd.dk [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id B7BD31AF137 for ; Thu, 9 Jan 2020 09:59:10 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id 0099xAJK004166 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Thu, 9 Jan 2020 09:59:10 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id 0099xAru004165; Thu, 9 Jan 2020 09:59:10 GMT (envelope-from phk) To: current@freebsd.org Subject: M_TEMP trouble in 13.0-CURRENT #0 r355131M From: Poul-Henning Kamp MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4163.1578563950.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Thu, 09 Jan 2020 09:59:10 +0000 Message-ID: <4164.1578563950@critter.freebsd.dk> X-Rspamd-Queue-Id: 47thRC2PKHz3NxF X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of phk@critter.freebsd.dk designates 130.225.244.222 as permitted sender) smtp.mailfrom=phk@critter.freebsd.dk X-Spamd-Result: default: False [-1.86 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.987,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.92)[-0.918,0]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[freebsd.dk]; IP_SCORE(0.04)[ip: (0.07), ipnet: 130.225.0.0/16(0.07), asn: 1835(0.09), country: EU(-0.01)]; FORGED_SENDER(0.30)[phk@phk.freebsd.dk,phk@critter.freebsd.dk]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:1835, ipnet:130.225.0.0/16, country:EU]; FROM_NEQ_ENVFROM(0.00)[phk@phk.freebsd.dk,phk@critter.freebsd.dk]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jan 2020 09:59:20 -0000 I noticed yesterday that M_TEMP stats are screwed up, and rebooted my laptop for reasons of safety. However, it's back again now: critter phk> vmstat -m | grep temp temp 18446744073709546036 18014398509476380K - 963239 16,32,6= 4,128,256,512,1024,2048,4096,8192,16384,32768,65536 FreeBSD critter.freebsd.dk 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r355131M: = Wed Nov 27 16:44:48 UTC 2019 root@critter.freebsd.dk:/usr/obj/freebsd/= src/amd64.amd64/sys/GENERIC-NODEBUG amd64 I mentioned this on IRC yesterday and noted I had a "disk full" on a tmpfs mount, but that can now be disregarded as a false lead. On this kernel I have had an instance where X got killed for out-of-swap, at a time where that certainly should not have been the case. Am I the only one seeing this ? -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence= .