From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36563] Unity locks up with latest xorg/mesa/dri/drm
Date: Wed, 25 May 2011 12:27:24 -0700 (PDT) [thread overview]
Message-ID: <20110525192724.997F613004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-36563-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=36563
--- Comment #5 from Rune K. Svendsen <runesvend@gmail.com> 2011-05-25 12:27:24 PDT ---
Created an attachment (id=47157)
--> (https://bugs.freedesktop.org/attachment.cgi?id=47157)
Output of running 'thread apply all bt full' in gdb after attaching to
frozen/hung compiz
(In reply to comment #3)
> Looks like it's hanging when trying to acquire the radeon->bo_handles_mutex .
> Does running
>
> thread apply all bt full
>
> in gdb give backtraces for any other threads?
I'm attaching the output of that command here.
Please let me know if I'm missing any relevant debug symbols. I can see a lot
of the loaded libraries don't have debug symbols, so please let me know which
are relevant, if any.
--
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-05-25 19:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 8:16 [Bug 36563] New: Unity locks up with latest xorg/mesa/dri/drm bugzilla-daemon
2011-04-25 14:16 ` [Bug 36563] " bugzilla-daemon
2011-04-27 4:35 ` bugzilla-daemon
2011-05-22 21:37 ` bugzilla-daemon
2011-05-23 7:31 ` bugzilla-daemon
2011-05-23 8:18 ` bugzilla-daemon
2011-05-25 19:27 ` bugzilla-daemon [this message]
2011-05-25 19:34 ` bugzilla-daemon
2011-05-26 19:35 ` bugzilla-daemon
2015-07-07 23:47 ` 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=20110525192724.997F613004F@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