Date: Thu, 09 Jan 2020 09:59:10 +0000 From: Poul-Henning Kamp <phk@phk.freebsd.dk> To: current@freebsd.org Subject: M_TEMP trouble in 13.0-CURRENT #0 r355131M Message-ID: <4164.1578563950@critter.freebsd.dk>
next in thread | raw e-mail | index | archive | help
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=
.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4164.1578563950>