From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 60028] Post-3.7.x memory leak, Radeon Evergreen, bisected Date: Wed, 30 Jan 2013 13:10:05 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1803764552==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id E1931E5FC2 for ; Wed, 30 Jan 2013 05:10:04 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1803764552== Content-Type: multipart/alternative; boundary="1359551404.Cb3ED80.28625"; charset="us-ascii" --1359551404.Cb3ED80.28625 Date: Wed, 30 Jan 2013 13:10:04 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=60028 --- Comment #8 from Dave Witbrodt --- (In reply to comment #7) > This is indeed more likely an issue in Mesa than in the kernel. The commit > you bisected also bumps KMS_DRIVER_MINOR in radeon_drv.c, which may cause > the Mesa code to use different code paths. In my two attempted manual reverts, I didn't know what effect the code in radeon_drv.c actually had. When looking at later DRM changes (after the one identified by the bisection) I saw that the value of KMS_DRIVER_MINOR was incremented further, so I thought I should leave the value unchanged. > Does current Mesa Git still leak? After updating/merging to the current HEAD (commit 02b6da1e of Jan. 29), I built new Mesa packages and installed them. I am currently relying the last kernel from my local tree which does not leak, so I rebooted to the kernel I had built that is most current with the upstream DRM changes: stable 3.7.4 + many commits from drm-next/drm-fixes up to commit 014b3440 of Jan. 21 in drm-fixes. Yes, it still leaks. Would it be good for me to bisect Mesa? I would use my most up-to-date kernel, try to find an older version of Mesa which does not leak, and then identify the first patch to Mesa which causes the leaking. The testing I have done so far was assuming the problem was in the kernel, but I was planning to look at Mesa as well. I decided to report the bug before continuing, hoping for some guidance from the experts. If there really is a memory leak caused by the kernel DRI, then I would like to help get it fixed before 3.8 is released; or, if there is a problem in Mesa I would like to help get it fixed for 9.1. -- You are receiving this mail because: You are the assignee for the bug. --1359551404.Cb3ED80.28625 Date: Wed, 30 Jan 2013 13:10:04 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 8 on bug 60028 from 
(In reply to comment #7)
> This is indeed more likely an issue in Mesa than in the kernel. The commit
> you bisected also bumps KMS_DRIVER_MINOR in radeon_drv.c, which may cause
> the Mesa code to use different code paths.

In my two attempted manual reverts, I didn't know what effect the code in
radeon_drv.c actually had.  When looking at later DRM changes (after the one
identified by the bisection) I saw that the value of KMS_DRIVER_MINOR was
incremented further, so I thought I should leave the value unchanged.


> Does current Mesa Git still leak?

After updating/merging to the current HEAD (commit 02b6da1e of Jan. 29), I
built new Mesa packages and installed them.

I am currently relying the last kernel from my local tree which does not leak,
so I rebooted to the kernel I had built that is most current with the upstream
DRM changes:  stable 3.7.4 + many commits from drm-next/drm-fixes up to commit
014b3440 of Jan. 21 in drm-fixes.

Yes, it still leaks.


Would it be good for me to bisect Mesa?  I would use my most up-to-date kernel,
try to find an older version of Mesa which does not leak, and then identify the
first patch to Mesa which causes the leaking.

The testing I have done so far was assuming the problem was in the kernel, but
I was planning to look at Mesa as well.  I decided to report the bug before
continuing, hoping for some guidance from the experts.  If there really is a
memory leak caused by the kernel DRI, then I would like to help get it fixed
before 3.8 is released; or, if there is a problem in Mesa I would like to help
get it fixed for 9.1.

You are receiving this mail because:
  • You are the assignee for the bug.
--1359551404.Cb3ED80.28625-- --===============1803764552== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1803764552==--