From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 37168] Regression: Kernel hard-lock when running Second Life
Date: Fri, 10 Jun 2011 15:28:49 -0700 (PDT) [thread overview]
Message-ID: <20110610222849.CD13D13004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-37168-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=37168
Sean McNamara <gm.potato.ul@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #11 from Sean McNamara <gm.potato.ul@gmail.com> 2011-06-10 15:28:49 PDT ---
(In reply to comment #10)
> (In reply to comment #6)
> > Created an attachment (id=47812)
View: https://bugs.freedesktop.org/attachment.cgi?id=47812
Review: https://bugs.freedesktop.org/review?bug=37168&attachment=47812
> > proposed patch
> >
> > I'm having the same memory leak issue (though I kill the game when swapping
> > starts so I did not experience kernel lock).
> >
> > The attached patch seems to fix the problem; could you please test it with your
> > setup ?
>
> The patch also fixes the segfaults I experienced. Same bug, different behaviour
> I guess.
Hmm. I never got it to segfault, IOMMU or not :) The closest I could get to a
segfault is the kernel sending it SIGKILL, which results in the console saying
"Killed" and dmesg warning you that the oomkiller had to kill the worst RAM
offender.
Anyway, we should really mark this bug as fixed, even though the original bug
title is a *horrible* misnomer for the actual symptom and fix here...
--
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-10 22:28 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
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 [this message]
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=20110610222849.CD13D13004F@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).