Date: Wed, 27 Nov 2013 12:45:19 -0800 From: Craig Rodrigues <rodrigc@FreeBSD.org> To: Adrian Chadd <adrian@freebsd.org> Cc: thierry.herbelot@free.fr, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: VIMAGE: Freed UMA keg was not empty Message-ID: <CAG=rPVf=u7t3o0mzHys5Kw9XAGJRv-pFpEr7GCOYYZb0FgSFDQ@mail.gmail.com> In-Reply-To: <CAJ-VmonPZosKJ7dySRhCMPb0USsmaH9JNzNOZz_T0Z=8NPxNhw@mail.gmail.com> References: <CAG=rPVc4dYcXXjSy%2BTV_GhrxKqszQ8JF5B56tUPQN-QmuDv7NA@mail.gmail.com> <CAJ-VmonPZosKJ7dySRhCMPb0USsmaH9JNzNOZz_T0Z=8NPxNhw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 27, 2013 at 2:05 AM, Adrian Chadd <adrian@freebsd.org> wrote: > > Well, the first step is figuring out which UMA zones are actually > problematic. Isn't it logging which zones aren't empty? The error messages on the console look like this: Freed UMA keg was not empty (203 items). Lost 1 pages of memory. Freed UMA keg was not empty (36 items). Lost 2 pages of memory. That doesn't really tell which UMA zone isn't empty. Is there some technqiue to figure this out? I tried "vmstat -z" and "vmstat -m", but while those gave clues, it didn't point to which UMA zone was leaking. Is there some other technique or tool that I can use? -- Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG=rPVf=u7t3o0mzHys5Kw9XAGJRv-pFpEr7GCOYYZb0FgSFDQ>