From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 116101] New: "Userspace still has active objects" and "trying to unbind memory from uninitialized GART !" when unbinding from radeon
Date: Sat, 09 Apr 2016 20:39:18 +0000 [thread overview]
Message-ID: <bug-116101-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=116101
Bug ID: 116101
Summary: "Userspace still has active objects" and "trying to
unbind memory from uninitialized GART !" when
unbinding from radeon
Product: Drivers
Version: 2.5
Kernel Version: 4.5.0
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: MonopolyMan720@aol.com
Regression: No
Created attachment 212291
--> https://bugzilla.kernel.org/attachment.cgi?id=212291&action=edit
Journalctl output
I am attempting to unbind my R9 290 from radeon and rebind it to vfio. However,
the entire system hangs when "echo "0000:01:00.0" >
/sys/bus/pci/devices/0000:01:00.0/driver/unbind" is ran as root.
Steps to Reproduce:
Run the following script as root
#!/bin/bash
set -x
echo "1002 67b1" > /sys/bus/pci/drivers/vfio-pci/new_id
echo "0000:01:00.0" > /sys/bus/pci/devices/0000:01:00.0/driver/unbind
echo "0000:01:00.0" > /sys/bus/pci/drivers/vfio-pci/bind
echo "1002 67b1" > /sys/bus/pci/drivers/vfio-pci/remove_id
echo "1002 aac8" > /sys/bus/pci/drivers/vfio-pci/new_id
echo "0000:01:00.1" > /sys/bus/pci/devices/0000:01:00.1/driver/unbind
echo "0000:01:00.1" > /sys/bus/pci/drivers/vfio-pci/bind
echo "1002 aac8" > /sys/bus/pci/drivers/vfio-pci/remove_id
set +x
Actual Results:
System hangs on "echo "0000:01:00.0" >
/sys/bus/pci/devices/0000:01:00.0/driver/unbind"
Journalctl shows "Apr 09 16:10:26 joey-arch-pc kernel: radeon 0000:01:00.0:
Userspace still has active objects !" followed by numerous "Apr 09 16:10:26
joey-arch-pc kernel: trying to unbind memory from uninitialized GART !"
Expected Results:
The GPU should be unbinding from radeon and rebinding to vfio-pci without
hanging.
Additional information:
I experienced the same issue on 4.1.20-1.
I know of instances where the same script results in the expected outcome with
a Cayman PRO graphics card.
Attached is the output of journalctl for the entire boot. Go to 16:10:26 to see
relevant call traces.
--
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 reply other threads:[~2016-04-09 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-09 20:39 bugzilla-daemon [this message]
2016-04-10 17:32 ` [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 bugzilla-daemon
2016-04-11 7:36 ` bugzilla-daemon
2016-04-11 14:46 ` bugzilla-daemon
2016-04-11 14:54 ` bugzilla-daemon
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@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox