From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@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 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0614422344==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 2E1F689050 for ; Tue, 13 Oct 2015 00:06:32 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0614422344== Content-Type: multipart/alternative; boundary="1444719992.B02d0.17062"; charset="UTF-8" --1444719992.B02d0.17062 Date: Tue, 13 Oct 2015 07:06:31 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=92214 --- Comment #29 from Barto --- 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. --1444719992.B02d0.17062 Date: Tue, 13 Oct 2015 07:06:32 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 29 on bug 92214 from 
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.
--1444719992.B02d0.17062-- --===============0614422344== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============0614422344==--