control: severity -1 wishlist
control: forwarded -1 https://freedesktop.org/patch/34445
control: retitle -1 mesa: use llvm's getCPUTargetFeatures() instead of
getHostCPUName()
It turns out that mesa uses llvm's getHostCPUName(), and qemu i386 by
default (correctly) reports itself as pentium2, whic
On Fri, 13 Mar 2015 at 13:01:13 +, Simon McVittie wrote:
> Control: unmerge 775235
...
> On 09/03/15 20:57, Julien Cristau wrote:
> > On Thu, Feb 26, 2015 at 08:54:10 +, Simon McVittie wrote:
> >> Context for Mesa maintainers: #775235 is that gnome-shell crashes in
> >> an i386 VM with its
Control: unmerge 775235
Control: retitle 775235 gnome-shell: fails to start on i386 when Mesa was built
with llvm-3.5
Control: reassign 775235 libgl1-mesa-dri
Control: retitle 770130 gnome-shell: crashes with "Failed to create texture 2d"
after "[drm:i8xx_irq_handler] *ERROR* pipe A underrun"
On
On 10/03/15 11:48, Kill Your TV wrote:
> I'd wholeheartedly +1 this is the failure was only on emulated systems
> with "impossibly-doomed-to-failure" configurations, but from the
> earlier posts in this bug this problem initially affected real hardware.
Right, that's a real application problem, in
On Tue, 10 Mar 2015 08:16:03 + (UTC)
Simon McVittie wrote:
> On 09/03/15 22:30, Kill Your TV wrote:
> > On Mon, 9 Mar 2015 21:04:55 + (UTC)
> > Simon McVittie wrote:
> >> If your host CPU is missing any of those features, then emulating a
> >> SandyBridge CPU in your VM is probably an i
On Mon, 9 Mar 2015 21:04:55 + (UTC)
Simon McVittie wrote:
> If your host CPU is missing any of those features, then emulating a
> SandyBridge CPU in your VM is probably an invalid configuration.
This is absolutely true of course (I personally use -cpu host), but
IMHO there should be more g
On 09/03/15 22:30, Kill Your TV wrote:
> On Mon, 9 Mar 2015 21:04:55 + (UTC)
> Simon McVittie wrote:
>> If your host CPU is missing any of those features, then emulating a
>> SandyBridge CPU in your VM is probably an invalid configuration.
>
> This is absolutely true of course (I personally
On 09/03/15 20:57, Julien Cristau wrote:
> On Thu, Feb 26, 2015 at 08:54:10 +, Simon McVittie wrote:
>> Context for Mesa maintainers: #775235 is that gnome-shell crashes in
>> an i386 VM with its default choice of emulated CPU, with
>> "LLVM ERROR: Do not know how to split the result of this op
On 09/03/15 19:09, kytv wrote:
> The host system has an AMD FX-6100 CPU.
...
> These did not work without the patch and they're still not working.
>
> * SandyBridge
> * Broadwell
> * Haswell
> * Westmere
> * Nehalem
> * Penryn
Those are all rather modern Intel CPUs. It would not surprise me at al
On Thu, Feb 26, 2015 at 08:54:10 +, Simon McVittie wrote:
> Adding mesa@packages to Cc since I suspect #775235 needs reassigning
> to Mesa, perhaps along with its merged bugs #770130, #776911.
>
> Context for Mesa maintainers: #775235 is that gnome-shell crashes in
> an i386 VM with its defau
On Sun, 8 Mar 2015 20:02:00 + (UTC)
intrigeri wrote:
> I've rebuilt the mesa package with the patch from
> https://freedesktop.org/patch/34445/, and it fixes things for me, at
> least with `-cpu qemu32'. I've asked the other Tails developer (Cc'd),
> who is also experiencing this bug, to try
Hi,
Simon McVittie wrote (26 Feb 2015 08:54:10 GMT) :
> Context for Mesa maintainers: #775235 is that gnome-shell crashes in
> an i386 VM with its default choice of emulated CPU, with
> "LLVM ERROR: Do not know how to split the result of this operator!".
> See https://bugs.debian.org/cgi-bin/bugre
Adding mesa@packages to Cc since I suspect #775235 needs reassigning
to Mesa, perhaps along with its merged bugs #770130, #776911.
Context for Mesa maintainers: #775235 is that gnome-shell crashes in
an i386 VM with its default choice of emulated CPU, with
"LLVM ERROR: Do not know how to split the
13 matches
Mail list logo