From owner-freebsd-current@freebsd.org  Fri Jan  6 17:14:39 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3D3D3CA2A30
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Fri,  6 Jan 2017 17:14:39 +0000 (UTC)
 (envelope-from mmacy@nextbsd.org)
Received: from sender163-mail.zoho.com (sender163-mail.zoho.com
 [74.201.84.163])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 24D6F16ED;
 Fri,  6 Jan 2017 17:14:38 +0000 (UTC)
 (envelope-from mmacy@nextbsd.org)
Received: from mail.zoho.com by mx.zohomail.com
 with SMTP id 1483722867312486.0919474075347;
 Fri, 6 Jan 2017 09:14:27 -0800 (PST)
Date: Fri, 06 Jan 2017 09:14:27 -0800
From: Matthew Macy <mmacy@nextbsd.org>
To: "Jonathan Anderson" <jonathan@FreeBSD.org>
Cc: "" <markj@freebsd.org>, "" <alc@freebsd.org>, 
 "freebsd-current Current" <freebsd-current@freebsd.org>
Message-ID: <15974c6426d.12945df5e62589.5931208946643250381@nextbsd.org>
In-Reply-To: <74A6C6D0-90A4-4DB2-8D89-5D2B1E495F88@FreeBSD.org>
References: <CAMGEAwBknRjecXFyyFGWFQtstX1OiOUvQoVsb9RXj7rmMQ6dDA@mail.gmail.com>
 <1596d0f6d6d.1266583c3319360.3590554896761456790@nextbsd.org>
 <74A6C6D0-90A4-4DB2-8D89-5D2B1E495F88@FreeBSD.org>
Subject: Re: PQ_LAUNDRY: unexpected behaviour
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: Medium
User-Agent: Zoho Mail
X-Mailer: Zoho Mail
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jan 2017 17:14:39 -0000


 > > Please try the drm-next branch now. Up until very recently, the  
 > > shrinkers responsible for culling ttm/gem allocations were never run.  
 > > I've now implemented the shrinker, but it's driven from vm_lowmem, so  
 > > you'll probably still see what looks like a leak until you hit low  
 > > memory conditions. The shrinker should probably be run from  
 > > uma_timeout, but there isn't an eventhandler for that and I haven't  
 > > looked any further. 
 > > 
 > > -M 
 >  
 > Hi, 
 >  
 > I am now testing the `drm-next` branch, but I'm finding it crashes much  
 > more frequently (a la  
 > https://github.com/FreeBSDDesktop/freebsd-base-graphics/issues/96) than  
 > `drm-next-4.7`. While the 4.7 branch would sometimes only last a few  
 > minutes, it would sometimes run for a day or more. On `drm-next`,  
 > however, I think I'm yet to have 20 minutes of uptime. So, I haven't run  
 > into the memory shrinker yet because I haven't had enough uptime to use  
 > lots of memory. :) I will continue testing... any specific things I  
 > ought to be doing? 
 >  
 


I just did the merge and it's using a relatively untested new KPI so regressions aren't too surprising I'm afraid. #96 is more or less content free in terms of providing useful information. Getting a core + backtrace would be a lot more helpful. See the repo's wiki for details on improving your odds of getting a core.

-M