From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89746] Mesa and LLVM 3.6+ break opengl for genymotion
Date: Tue, 24 Mar 2015 10:44:17 +0000 [thread overview]
Message-ID: <bug-89746-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2022 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=89746
Bug ID: 89746
Summary: Mesa and LLVM 3.6+ break opengl for genymotion
Product: Mesa
Version: 10.5
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: spupazza@hotmail.com
QA Contact: dri-devel@lists.freedesktop.org
I found out LLVM 3.6 + Mesa 10.5 (and newer) might have some sort of regression
breaking opengl with radeonsi drivers at least.
I use genymotion (android emulator) which relies on virtualbox and make use of
opengl acceleration.
On 2 different machines with 2 different distros (ubuntu 14.10/15.04 and
manjaro 0.9 pre4) I had the same problem: as soon as LLVM 3.6 or 3.7git (the
latter with utopic when I added paulo dias ppa) gets installed
genymotion stop working (the screen of the vm disappear 1-2 seconds after the
machine gets started, and while the screen disappear the machine keeps running
in the background).
On the terminal I get this error:
Port 22468 will be used for OpenGL data connections
Unknown TCPCLI command 1003
LLVM ERROR: 'main' label emitted multiple times to assembly file
With LLVM 3.5 genymotion (with the same distros and machines) was working just
fine.
Another proof that the issue is with LLVM is that as to temporarily sort this
problem out, I installed the proprietary drivers (fgrlx) and the issue vanished
(since proprietary drivers do not make use of LLVM).
To reproduce the bug, you need a radeon vga (possibly one using the radeonsi
drivers so with GCN architecture) , install vitualbox and genymotion, Setup a
virtual device and having installed LLVM 3.6 or newer. Then start the device
you created.
I reported this bug to the llvm bug-tracker system and they told me to report
it to you.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3320 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-03-24 10:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 10:44 bugzilla-daemon [this message]
2015-03-24 12:34 ` [Bug 89746] Mesa and LLVM 3.6+ break opengl for genymotion bugzilla-daemon
2015-03-24 13:42 ` bugzilla-daemon
2015-03-24 14:35 ` bugzilla-daemon
2015-03-24 14:37 ` bugzilla-daemon
2015-03-24 14:55 ` bugzilla-daemon
2015-03-25 21:05 ` bugzilla-daemon
2015-03-26 2:22 ` bugzilla-daemon
2015-03-26 8:20 ` bugzilla-daemon
2015-03-26 8:33 ` bugzilla-daemon
2015-03-26 13:25 ` bugzilla-daemon
2015-03-26 13:31 ` bugzilla-daemon
2015-03-26 16:14 ` bugzilla-daemon
2015-03-26 18:33 ` bugzilla-daemon
2015-03-27 12:19 ` bugzilla-daemon
2015-03-30 12:43 ` bugzilla-daemon
2015-03-30 16:51 ` bugzilla-daemon
2015-03-31 1:32 ` bugzilla-daemon
2015-04-04 22:19 ` bugzilla-daemon
2016-09-01 14:14 ` bugzilla-daemon
2016-09-01 14:59 ` 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-89746-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.