Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 3 May 2016 08:27:52 -0600
From:      Scott Long <scott4long@yahoo.com>
To:        Mark Johnston <markj@FreeBSD.org>
Cc:        Steve Wills <swills@FreeBSD.org>, FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>, freebsd-current@freebsd.org, scottl@FreeBSD.org, Warner Losh <imp@bsdimp.com>
Subject:   Re: wired memory leak at r298785
Message-ID:  <E7308871-DC4F-4DB2-867C-271AF01F8DD6@yahoo.com>
In-Reply-To: <20160503062031.GA2209@raichu>
References:  <572756DF.1010809@FreeBSD.org> <5727F71E.20101@FreeBSD.org> <20160503062031.GA2209@raichu>

next in thread | previous in thread | raw e-mail | index | archive | help

> On May 3, 2016, at 12:20 AM, Mark Johnston <markj@FreeBSD.org> wrote:
>=20
> On Mon, May 02, 2016 at 08:55:58PM -0400, Steve Wills wrote:
>> Hi,
>>=20
>> On 05/ 2/16 09:32 AM, Steve Wills wrote:
>>> Hi,
>>>=20
>>> Just did my monthly update and r298785 seems to be leaking wired =
memory
>>> rather rapidly. My system has 8gb of RAM and the amount of wired =
memory
>>> just goes up and up continuously. It takes about 12 hours before it
>>> exhausts all the RAM and sort of locks up (though shutdown still =
works).
>>>=20
>>> I also made one other change to the system at the same time as =
updating,
>>> which was to add another disk and configure it using ZFS. Perhaps =
this
>>> is a ZFS on PowerPC64 issue? My amd64 box running the same rev of
>>> CURRENT doesn't have the issue.
>>>=20
>>=20
>> I've rebooted the box and started repeatedly logging the output of
>> vmstat -m. It seems to show CAM CCB using a lot of memory and growing
>> rather rapidly. For example, here's a few lines of diff output:
>>=20
>> - CAM CCB 91418 182836K - 187149 2048
>> + CAM CCB 447070 894140K - 900292 2048
>>=20
>> from two samples that are 60 minutes apart.
>>=20
>> The box is isn't terribly busy, it's just running the monitoring =
daemons
>> running (snmpd, collectd), whatever web requests are hitting it (very
>> few if any), this logging process, and my shell, etc.
>=20
> This was causing problems on one of my amd64 systems, so it's not
> specific to powerpc64. It turns out to be due to r298004: the CCB
> allocated in cam_periph_devctl_notify() never gets freed. The patch
> below seems to fix it.

Thanks Mark, that looks like the right fix.  I=E2=80=99ll put it in =
today.

Scott




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E7308871-DC4F-4DB2-867C-271AF01F8DD6>