From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 30374] New: ums 3D lock since drm: kill kernel_context_switch callbacks 1da3f87ebb7edb3e0b829ec4bbe5fb3d9d93986f
Date: Sat, 25 Sep 2010 08:24:00 -0700 (PDT) [thread overview]
Message-ID: <bug-30374-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=30374
Summary: ums 3D lock since drm: kill kernel_context_switch
callbacks 1da3f87ebb7edb3e0b829ec4bbe5fb3d9d93986f
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: lists@andyfurniss.entadsl.com
git d-r-t, mesa, ddx and xserver. rv790 PCIE card.
UMS radeon/r600c with current d-r-t soft locks when a mesa demo is run.
Log shows many
[drm:drm_lock_take] *ERROR* 1 holds heavyweight lock
bisect came up with
1da3f87ebb7edb3e0b829ec4bbe5fb3d9d93986f is first bad commit
commit 1da3f87ebb7edb3e0b829ec4bbe5fb3d9d93986f
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date: Mon Aug 23 22:53:24 2010 +0200
drm: kill kernel_context_switch callbacks
Not used by any in-kernel driver. So drop it.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-09-25 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 15:24 bugzilla-daemon [this message]
2010-09-25 18:33 ` [Bug 30374] ums 3D lock since drm: kill kernel_context_switch callbacks 1da3f87ebb7edb3e0b829ec4bbe5fb3d9d93986f bugzilla-daemon
2010-09-25 18:45 ` bugzilla-daemon
2010-09-25 21:15 ` bugzilla-daemon
2010-09-25 21:28 ` bugzilla-daemon
2010-09-25 22:06 ` bugzilla-daemon
2010-09-26 8:52 ` 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-30374-502@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 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.