From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92214] Flightgear crashes during splashboot with R600 driver, LLVM 3.7.0 and mesa 11.0.2
Date: Tue, 13 Oct 2015 07:06:32 +0000 [thread overview]
Message-ID: <bug-92214-502-eYxGEq6fDK@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92214-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 828 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92214
--- Comment #29 from Barto <mister.freeman@laposte.net> ---
like Roland said in comment#13 the bug could be in mesa source code, an
incorrect initialization of llvm 3.7.0,
it worked in 3.6.2, but perhaps in 3.7.0 the same code is not enough, it needs
maybe more precise instructions in order to target exactly the CPU platform, to
produce correct cpu opcodes,
in dmesg I can see these messages when the SIGILL occurs :
[13766.649327] traps: tunnel[4095] trap invalid opcode ip:7f68ce8d7183
sp:7fff6c078700 error:0
[35876.638782] traps: llvmpipe-1[8766] trap invalid opcode ip:f77271bd
sp:f3536db0 error:0
[35876.638785] traps: llvmpipe-0[8765] trap invalid opcode ip:f77271bd
sp:f3d37db0 error:0
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1698 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 prev parent reply other threads:[~2015-10-13 7:06 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 17:17 [Bug 92214] Flightgear crashes during splashboot with R600 driver and mesa 11.0.2 bugzilla-daemon
2015-10-01 17:18 ` bugzilla-daemon
2015-10-01 17:25 ` bugzilla-daemon
2015-10-01 17:34 ` bugzilla-daemon
2015-10-01 17:48 ` bugzilla-daemon
2015-10-01 17:54 ` bugzilla-daemon
2015-10-01 18:40 ` bugzilla-daemon
2015-10-01 19:48 ` bugzilla-daemon
2015-10-01 20:02 ` bugzilla-daemon
2015-10-01 21:36 ` bugzilla-daemon
2015-10-02 1:03 ` bugzilla-daemon
2015-10-02 2:29 ` bugzilla-daemon
2015-10-02 2:55 ` bugzilla-daemon
2015-10-02 3:37 ` bugzilla-daemon
2015-10-07 13:28 ` bugzilla-daemon
2015-10-08 16:08 ` [Bug 92214] Flightgear crashes during splashboot with R600 driver, LLVM 3.7.0 " bugzilla-daemon
2015-10-09 16:44 ` bugzilla-daemon
2015-10-09 16:45 ` bugzilla-daemon
2015-10-09 16:47 ` bugzilla-daemon
2015-10-09 17:16 ` bugzilla-daemon
2015-10-09 18:34 ` bugzilla-daemon
2015-10-09 18:43 ` bugzilla-daemon
2015-10-09 18:53 ` bugzilla-daemon
2015-10-09 19:17 ` bugzilla-daemon
2015-10-11 14:38 ` bugzilla-daemon
2015-10-11 16:15 ` bugzilla-daemon
2015-10-12 11:42 ` bugzilla-daemon
2015-10-12 16:54 ` bugzilla-daemon
2015-10-12 21:14 ` bugzilla-daemon
2015-10-13 2:07 ` bugzilla-daemon
2015-10-13 7:06 ` bugzilla-daemon [this message]
2015-10-14 6:36 ` bugzilla-daemon
2015-10-22 1:49 ` bugzilla-daemon
2015-10-22 3:14 ` bugzilla-daemon
2015-10-22 19:41 ` bugzilla-daemon
2015-10-22 21:54 ` bugzilla-daemon
2015-10-22 21:59 ` bugzilla-daemon
2015-10-22 22:36 ` bugzilla-daemon
2015-10-23 10:37 ` bugzilla-daemon
2015-10-23 10:39 ` bugzilla-daemon
2015-10-23 13:55 ` bugzilla-daemon
2015-10-23 19:26 ` 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-92214-502-eYxGEq6fDK@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox