From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 37168] Regression: Kernel hard-lock when running Second Life
Date: Thu, 9 Jun 2011 06:57:06 -0700 (PDT) [thread overview]
Message-ID: <20110609135707.1B4A713004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-37168-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=37168
Sven Arvidsson <sa@whiz.se> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sa@whiz.se
--- Comment #5 from Sven Arvidsson <sa@whiz.se> 2011-06-09 06:57:06 PDT ---
I tried to reproduce this on my 5670, but couldn't.
I don't get a memory leak or a hard lock, instead the viewer (tried both SL and
Imprudence) segfaults after a short while. This is with current git master,
with 7.10 everything seems to be working.
I will try to bisect and file a new bug in case it's not the same problem.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-06-09 13:57 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
2011-05-20 7:36 ` bugzilla-daemon
2011-06-07 17:13 ` bugzilla-daemon
2011-06-09 13:57 ` bugzilla-daemon [this message]
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=20110609135707.1B4A713004F@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).