<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Flightgear crashes during splashboot with R600 driver, LLVM 3.7.0 and mesa 11.0.2"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92214#c28">Comment # 28</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Flightgear crashes during splashboot with R600 driver, LLVM 3.7.0 and mesa 11.0.2"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92214">bug 92214</a>
from <span class="vcard"><a class="email" href="mailto:mister.freeman@laposte.net" title="Barto <mister.freeman@laposte.net>"> <span class="fn">Barto</span></a>
</span></b>
<pre>another discovery :
in qemu I can set a type of CPU ( pentium, pentium2, pentium2, core2duo,
SandyBridge and many more ), you can see the CPUs list with the command
"qemu-i386 -cpu ?",
until now I used the qemu option "-cpu host", which means that it's the CPU of
the host who is emulated ( my pentium dual core E6800 ),
then I decided to set a different CPU name in my qemu script :
-cpu core2duo -enable-kvm -machine type=pc,accel=kvm -smp 2
with this setting the bug disapears, all is ok in my virtual machine, glxgears
and all openGL programs can run without crash, the mesa driver llvmpipe doesn't
crash,
after that I decided to do set again another CPU in qemu :
-cpu Penryn -enable-kvm -machine type=pc,accel=kvm -smp 2 \
with "Penryn" CPU the bug is back in my virtual machine, which means that the
bug seems related to the type of CPU, llvm 3.7.0 lib may have a bug when he
tries to generate binary code, it fails with some CPUs,
this problem doesn't exist with llvm 3.6.2 lib</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>