NetBSD Problem Report #54374

From wiz@yt.nih.at  Sun Jul 14 07:59:40 2019
Return-Path: <wiz@yt.nih.at>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id CC98A7A162
	for <gnats-bugs@gnats.NetBSD.org>; Sun, 14 Jul 2019 07:59:40 +0000 (UTC)
Message-Id: <20190714070656.7D29C2AC101@yt.nih.at>
Date: Sun, 14 Jul 2019 09:06:56 +0200 (CEST)
From: Thomas Klausner <wiz@NetBSD.org>
Reply-To: Thomas Klausner <wiz@NetBSD.org>
To: gnats-bugs@NetBSD.org
Subject: long-running 'systat vm' reports malloc errors
X-Send-Pr-Version: 3.95

>Number:         54374
>Category:       bin
>Synopsis:       long-running 'systat vm' reports malloc errors
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jul 14 08:00:01 +0000 2019
>Closed-Date:    Tue Mar 03 07:44:23 +0000 2020
>Last-Modified:  Tue Mar 03 09:15:01 +0000 2020
>Originator:     Thomas Klausner
>Release:        NetBSD 8.99.50
>Organization:
Curiosity is the very basis of education and if you tell me that
curiosity killed the cat, I say only that the cat died nobly.
- Arnold Edinborough
>Environment:


Architecture: x86_64
Machine: amd64
>Description:
I've been monitoring an unstable machine by running 'systat vm' in a ssh connection
to it. Usually, after a couple of hours, the bottom line shows

can't get buffers: Cannot allocate memory

Pressing 'space' gets rid of it, but it usually reappears in the next hours.

The machine is far from running out of memory as far as I can tell.
(128 GB RAM, usually >90G free; no swap configured though).

No other process reports running out of memory (bulk build, top).
>How-To-Repeat:
Run 'systat vm' for some hours.
>Fix:
No idea.

>Release-Note:

>Audit-Trail:
From: Thomas Klausner <wiz@NetBSD.org>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: bin/54374: long-running 'systat vm' reports malloc errors
Date: Sun, 14 Jul 2019 10:34:15 +0200

 There is another error message I have seen a couple of times:

 can't get buffers: Resource temporarily unavailable

State-Changed-From-To: open->closed
State-Changed-By: wiz@NetBSD.org
State-Changed-When: Tue, 03 Mar 2020 07:44:23 +0000
State-Changed-Why:
A fix to systat was committed recently; assume this is fixed until I see it again.


From: matthew green <mrg@eterna.com.au>
To: gnats-bugs@netbsd.org
Cc: gnats-admin@netbsd.org, netbsd-bugs@netbsd.org, wiz@NetBSD.org
Subject: re: bin/54374 (long-running 'systat vm' reports malloc errors)
Date: Tue, 03 Mar 2020 20:09:56 +1100

 > State-Changed-From-To: open->closed
 > State-Changed-By: wiz@NetBSD.org
 > State-Changed-When: Tue, 03 Mar 2020 07:44:23 +0000
 > State-Changed-Why:
 > A fix to systat was committed recently; assume this is fixed until I see=
  it again.

 if it does, increase the two new 1000's to 2000 or 5000 or so.
 until the next time ;)


 .mrg.

>Unformatted:

Home	PR Database Search