From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60028] Post-3.7.x memory leak, Radeon Evergreen, bisected
Date: Wed, 30 Jan 2013 13:10:05 +0000 [thread overview]
Message-ID: <bug-60028-502-VE8z9gBLTn@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-60028-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1781 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=60028
--- Comment #8 from Dave Witbrodt <dawitbro@sbcglobal.net> ---
(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.
[-- Attachment #1.2: Type: text/html, Size: 2667 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-01-30 13:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 16:00 [Bug 60028] New: Post-3.7.x memory leak, Radeon Evergreen, bisected bugzilla-daemon
2013-01-29 16:02 ` [Bug 60028] " bugzilla-daemon
2013-01-29 16:08 ` bugzilla-daemon
2013-01-29 16:10 ` bugzilla-daemon
2013-01-29 16:11 ` bugzilla-daemon
2013-01-29 16:12 ` bugzilla-daemon
2013-01-29 16:13 ` bugzilla-daemon
2013-01-29 16:21 ` bugzilla-daemon
2013-01-30 13:10 ` bugzilla-daemon [this message]
2013-01-30 14:03 ` bugzilla-daemon
2013-01-31 13:27 ` bugzilla-daemon
2013-01-31 13:39 ` bugzilla-daemon
2013-01-31 13:43 ` bugzilla-daemon
2013-01-31 13:44 ` [Bug 60028] r600g: Htile memory leak bugzilla-daemon
2013-01-31 14:43 ` bugzilla-daemon
2013-01-31 15:58 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-60028-502-VE8z9gBLTn@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox