From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101261] Radeon - Kernel warning when driver is unbound to secondary GPU
Date: Thu, 09 Jul 2015 08:19:03 +0000 [thread overview]
Message-ID: <bug-101261-2300-0K2llz2hdK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-101261-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=101261
--- Comment #2 from Beau V.C. Bellamy <bellamy.beau@gmail.com> ---
When unbinding the radeon driver from a second GPU in order to bind to the
vfio-pci driver (so it can be used on a virtual machine), the linux kernel will
display several warnings. It looks like some resources may be double-freed.
The GPU will otherwise work flawlessly in the VM with full acceleration on the
stock AMD windows drivers.
This actually shows up on all kernels that I've tried: 4.1.0, 3.19, 3.18, etc.
I'm not sure it's related, but the first GPU when running X on the host will
have some difficulties getting OpenGL working (I have a routine that involves a
dance with glxgears and firefox) and will work for some time and then take the
entire system down hard. If I avoid anything OpenGL/DRM, the system will run
indefinitely.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-07-09 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 8:05 [Bug 101261] New: Radeon - Kernel warning when driver is unbound to secondary GPU bugzilla-daemon
2015-07-09 8:06 ` [Bug 101261] " bugzilla-daemon
2015-07-09 8:19 ` bugzilla-daemon [this message]
2015-07-09 8:19 ` [Bug 101261] Radeon - Kernel warning when driver is unbound from " 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-101261-2300-0K2llz2hdK@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