All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 37168] Regression: Kernel hard-lock when running Second Life
Date: Fri, 13 May 2011 16:27:44 -0700 (PDT)	[thread overview]
Message-ID: <20110513232744.7CA8E13004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-37168-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=37168

--- Comment #2 from Sean McNamara <gm.potato.ul@gmail.com> 2011-05-13 16:27:44 PDT ---
(In reply to comment #1)
> (In reply to comment #0)
> > 
> > Mesa 7.10.2 tarball OR Mesa 7.10 branch from git: Correct rendering; no
> > crashing.
> 
> Can you bisect mesa and see what commits between 7.10 and master broke it?

debc45bca07a5dfad4199079f080b35c19f00e85 starts the memory leaks (very
noticeable on this commit, just watch gnome-system-monitor's total memory usage
grow by 25 - 100 MB/s)

I got two kernel hard-locks with 8c631cfeae29b5236928f759e222aa35e6e4984c also,
but it doesn't seem to have the memory leak.

Anyway, I'm not sure *exactly* which commit because I was fighting hardlocks
and memory leaks at the same time, and sometimes they are intermittent, but if
you look at the r600g commit series by Marek on or around January 28 - 29, I
think the problem lies somewhere in there. That's my best guess, and it's
certainly more relevant than what I came up with the last time I bisected,
which was the merge of dricore support (and I'm not even using dricore, btw).

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2011-05-13 23:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-13 10:40 [Bug 37168] New: Regression: Kernel hard-lock when running Second Life bugzilla-daemon
2011-05-13 16:10 ` [Bug 37168] " bugzilla-daemon
2011-05-13 23:27 ` bugzilla-daemon [this message]
2011-05-20  7:36 ` bugzilla-daemon
2011-06-07 17:13 ` bugzilla-daemon
2011-06-09 13:57 ` bugzilla-daemon
2011-06-10 14:34 ` bugzilla-daemon
2011-06-10 21:56 ` bugzilla-daemon
2011-06-10 22:02 ` bugzilla-daemon
2011-06-10 22:04 ` bugzilla-daemon
2011-06-10 22:16 ` bugzilla-daemon
2011-06-10 22:28 ` bugzilla-daemon
2011-06-10 22:30 ` [Bug 37168] Regression: Severe memory leak " bugzilla-daemon
2011-06-11  1:02 ` bugzilla-daemon
2011-06-11  1:17 ` bugzilla-daemon
2011-06-11  5:40 ` bugzilla-daemon
2011-06-13 14:51 ` 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=20110513232744.7CA8E13004F@annarchy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.