Bug#776911: gnome-shell: fails to start on i386 when [Mesa was] built with llvm-3.5

Simon McVittie smcv at debian.org
Mon Mar 9 21:04:49 UTC 2015


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 all
if they had CPU features that are not supported by your host system: AMD
CPUs usually support the latest version of AMD-originated features and a
somewhat older version of Intel-originated features, and vice versa.

You can check via /proc/cpuinfo on the host and the VM. For instance,
here's the Sandy Bridge CPU on my laptop:

flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology nonstop_tsc
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2
ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer
aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow
vnmi flexpriority ept vpid

If your host CPU is missing any of those features, then emulating a
SandyBridge CPU in your VM is probably an invalid configuration.

    S



More information about the pkg-gnome-maintainers mailing list