From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 116101] "RIP radeon_gem_va_ioctl+0x35/0x650", "Userspace still has active objects", and "trying to unbind memory from uninitialized GART !" when unbinding from radeon
Date: Mon, 11 Apr 2016 14:54:03 +0000 [thread overview]
Message-ID: <bug-116101-2300-tOIAzwuyRU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-116101-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=116101
--- Comment #3 from Joe P. <MonopolyMan720@aol.com> ---
(In reply to Christian König from comment #1)
> Well as the error message already suggests "Userspace still has active
> objects !" you have an application which is still using the hardware.
>
> So unbinding and rebinding it to the isn't possible in this state.
Just to show that it's working
$ glxinfo | grep "OpenGL renderer"
OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Server
$ DRI_PRIME=1 glxinfo | grep "OpenGL renderer"
OpenGL renderer string: Gallium 0.4 on AMD HAWAII (DRM 2.43.0, LLVM 3.7.1)
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-04-11 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-09 20:39 [Bug 116101] New: "Userspace still has active objects" and "trying to unbind memory from uninitialized GART !" when unbinding from radeon bugzilla-daemon
2016-04-10 17:32 ` [Bug 116101] "RIP radeon_gem_va_ioctl+0x35/0x650", "Userspace still has active objects", " bugzilla-daemon
2016-04-11 7:36 ` bugzilla-daemon
2016-04-11 14:46 ` bugzilla-daemon
2016-04-11 14:54 ` bugzilla-daemon [this message]
2016-04-11 18:43 ` bugzilla-daemon
2016-04-12 23:26 ` bugzilla-daemon
2016-04-13 0:25 ` 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-116101-2300-tOIAzwuyRU@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.