From owner-freebsd-x11@FreeBSD.ORG Thu Mar 14 22:00:11 2013 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 953589D9; Thu, 14 Mar 2013 22:00:11 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) by mx1.freebsd.org (Postfix) with ESMTP id 538C0E2D; Thu, 14 Mar 2013 22:00:10 +0000 (UTC) Received: from pool-141-154-241-44.bos.east.verizon.net ([141.154.241.44] helo=homobox.opal.com) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1UGGC2-000KE6-BT; Thu, 14 Mar 2013 22:00:10 +0000 Received: from shibato (pool-173-52-167-161.nycmny.east.verizon.net [173.52.167.161]) (authenticated bits=0) by homobox.opal.com (8.14.4/8.14.4) with ESMTP id r2EM05Wb020792 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 14 Mar 2013 18:00:06 -0400 (EDT) (envelope-from fbsd@opal.com) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 141.154.241.44 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/Of+6pBtsMy9GtaIzrRK/2 Date: Thu, 14 Mar 2013 17:59:55 -0400 From: "J.R. Oldroyd" To: Adam K Kirchhoff Subject: Re: New AMD drm code Message-ID: <20130314175955.4d1061b2@shibato> In-Reply-To: <20130311161345.00005499@unknown> References: <20130311001858.61224bf6@shibato> <20130311101005.000007d1@unknown> <20130311102210.0b9aa7a3@shibato> <20130311161345.00005499@unknown> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.6; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/RFD5/Op4PThc1MHPGhbD4dF"; protocol="application/pgp-signature" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (homobox.opal.com [141.154.241.44]); Thu, 14 Mar 2013 18:00:07 -0400 (EDT) X-Spam-Status: No, score=3.9 required=5.0 tests=AWL,BAYES_00, FH_HOST_EQ_VERIZON_P,FSL_HELO_NON_FQDN_1,RCVD_IN_PBL,RCVD_IN_RP_RNBL, RDNS_DYNAMIC shortcircuit=no autolearn=no version=3.3.2 X-Spam-Level: *** X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on homobox.opal.com Cc: "freebsd-x11@freebsd org" , Adam K Kirchhoff , =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2013 22:00:11 -0000 --Sig_/RFD5/Op4PThc1MHPGhbD4dF Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 11 Mar 2013 16:13:45 -0400 Adam K Kirchhoff wrote: > > Thanks, that got it working. I haven't had a chance to actually test > anything that uses DRI, but the module loads: >=20 Sorry, been a bit busy this week. There are a bunch of of memory leaks in the code as it is at the moment. I suspect you have noticed that the server gets slow and eventually stops. If you haven't, try opening two xterms. Run "top" in one. Run "ls -l /usr/local/bin" a few times in the other. Observe the Wired and Free counts in the top display. (It's probably a good idea to reboot before either runs out.) Earlier this week I fixed all the Wired page leaks and sent that patch to dumbbell@. It's not committed yet, though. I have also just fixed a bunch of places where a null pointer is freed and I've fixed a couple of the Free page leaks too. I'll be sending an updated patch to dumbbell tomorrow evening. With any luck, dumbbell will have time to commit some of these patches to the git repo soon. Maybe this weekend. There are fifteen major leaks remaining, although some of these may be related to one another. I.e., there may be <=3D 15 bugs still to find. It'd be great to have others help track some of these leaks down. My time will be limited next week. The codepaths here are rather convoluted, so it's a bit time-consuming. I have a lot of trace info about which mallocs are being leaked that I can send to anyone who can help. -jr --Sig_/RFD5/Op4PThc1MHPGhbD4dF Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlFCSGQACgkQls33urr0k4nn/QCfTGALhUOcw0zrU7iIWsYh8Ujp HRkAoKhXqw3x44dekrhIASNrSN9fBbCY =zJrI -----END PGP SIGNATURE----- --Sig_/RFD5/Op4PThc1MHPGhbD4dF--