Re: port-amd64/54988: possible memory leaks/swap problems

[mlh%goathill.org@localhost (MLH)]

The following reply was made to PR port-amd64/54988; it has been noted by GNATS.

From: mlh%goathill.org@localhost (MLH)
To: gnats-bugs%netbsd.org@localhost
Cc: ad%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, 
 mlh%goathill.org@localhost
Subject: Re: port-amd64/54988: possible memory leaks/swap problems
Date: Sun, 23 Feb 2020 17:30:23 -0500 (EST)

 Andrew Doran wrote:
 > The following reply was made to PR port-amd64/54988; it has been noted by GNATS.
 > 
 >  What is the file system / disk configuration on this machine?  Are you
 >  running any processes that consume a lot of wired memory by chance?
 
 $ df
 Filesystem    1K-blocks       Used      Avail %Cap Mounted on
 /dev/wd0a      71714288   38691140   29437434  56% /
 /dev/wd1f     946611748  285748620  613532544  31% /opt
 kernfs                1          1          0 100% /kern
 ptyfs                 1          1          0 100% /dev/pts
 procfs                4          4          0 100% /proc
 tmpfs           1044332          0    1044332   0% /var/shm
 
 Result is the same without /opt
 
 / is a completely new installation of NetBSD 9.99.46 GENERIC with
 HDMI audio compile option with my previous /etc environment merged
 with it but works the same with a GENERIC kernel. I repartitioned
 the drive and reformatted wd0a before installing.
 
 [     5.259157] wd0 at atabus2 drive 0
 [     5.259157] wd0: <ST380011A>
 [     5.259157] wd0: drive supports 16-sector PIO transfers, LBA48 addressing
 [     5.259157] wd0: 76319 MB, 155061 cyl, 16 head, 63 sec, 512 bytes/sect x 156301488 sectors
 [     5.319178] wd0: 32-bit data port
 [     5.319178] wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
 [     5.319178] wd0(jmide0:1:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using DMA)
 [     5.319178] wd1 at atabus3 drive 0
 [     5.319178] wd1: <ST1000DM003-1ER162>
 [     5.319178] wd1: drive supports 16-sector PIO transfers, LBA48 addressing
 [     5.319178] wd1: 931 GB, 1938021 cyl, 16 head, 63 sec, 512 bytes/sect x 1953525168 sectors
 [     5.379200] wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133), WRITE DMA FUA, NCQ (32 tags)
 [     5.379200] wd1(ahcisata1:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA), NCQ (31 tags)
 
 I also can have wd2/3 in a raid configuration mounted but the
 behavior is similar without it except that when mounted, the system
 runs out of phymem more quickly
 
 [     5.379200] wd2 at atabus5 drive 0
 [     5.379200] wd2: <ST4000DM004-2CV104>
 [     5.379200] wd2: drive supports 16-sector PIO transfers, LBA48 addressing
 [     5.379200] wd2: 3726 GB, 7752021 cyl, 16 head, 63 sec, 512 bytes/sect x 7814037168 sectors
 [     5.399207] wd2: GPT GUID: f10e8bb0-de35-4b54-b365-6571da54d265
 [     5.399207] dk0 at wd2: "boot0", 100000 blocks at 34, type: ffs
 [     5.399207] dk1 at wd2: "swap0", 10000000 blocks at 100034, type: swap
 [     5.399207] dk2 at wd2: "raidw0", 7803937101 blocks at 10100034, type: raidframe
 [     5.409211] wd2: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133), WRITE DMA FUA, NCQ (32 tags)
 [     5.409211] wd2(ahcisata1:4:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA), NCQ (31 tags)
 [     5.409211] wd3 at atabus6 drive 0
 [     5.409211] wd3: <ST4000DM004-2CV104>
 [     5.409211] wd3: drive supports 16-sector PIO transfers, LBA48 addressing
 [     5.409211] wd3: 3726 GB, 7752021 cyl, 16 head, 63 sec, 512 bytes/sect x 7814037168 sectors
 [     5.429218] wd3: GPT GUID: b3d4301a-cbfe-414e-ac61-16571d17d548
 [     5.429218] dk3 at wd3: "boot1", 100000 blocks at 34, type: ffs
 [     5.429218] dk4 at wd3: "swap1", 10000000 blocks at 100034, type: swap
 [     5.429218] dk5 at wd3: "raidw1", 7803937101 blocks at 10100034, type: raidframe
 
 I also get similar results when booting off of dk6(raid0) without
 wd0/1 mounted.  The raid0 has the same install environment as wd0a
 but it also failed the same way right after it was pristeenly
 installed, without any of my older environment and with a GENERIC
 kernel.