Comment 16 for bug 589611

* Stefan Fritsch <email address hidden>:

> But the bug disappears if I do
>
> mv /lib/i686 /lib/disabled_i686

I will try to reproduce this here

> There was a bug recently in Debian related to some gcc versions creating
> wrong code for SSE4. Maybe that is the problem here, too.
>
> What CPUs do you people have? Mine is a Core i7.

# cat /proc/cpuinfo
processor: 0
vendor_id: GenuineIntel
cpu family: 6
model: 15
model name: Intel(R) Xeon(R) CPU E5310 @ 1.60GHz
stepping: 11
cpu MHz: 1600.056
cache size: 4096 KB
fdiv_bug: no
hlt_bug: no
f00f_bug: no
coma_bug: no
fpu: yes
fpu_exception: yes
cpuid level: 10
wp: yes
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 nx lm constant_tsc
arch_perfmon pebs bts tsc_reliable aperfmperf pni ssse3 cx16
hypervisor lahf_lm
bogomips: 3200.11
clflush size: 64
cache_alignment: 64
address sizes: 40 bits physical, 48 bits virtual
power management:

> Does moving /lib/i686 away (or deinstalling libc6-i686) help for you too?
> Does the "flags" line in /proc/cpuinfo on your machines contain sse4_1 or sse4_2?
>
> For reference, the Debian bug was http://bugs.debian.org/cgi-
> bin/bugreport.cgi?bug=583858

I can tell you that the error does NOT occur with a 64bit Ubuntu!
(we reinstalled a 64bit lucid from scratch and transferred the config: the error was gone!)

The problematic 32bit machine is a vmware virtual machine.

--
Ralf Hildebrandt
  Geschäftsbereich IT | Abteilung Netzwerk
  Charité - Universitätsmedizin Berlin
  Campus Benjamin Franklin
  Hindenburgdamm 30 | D-12203 Berlin
  Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
  <email address hidden> | http://www.charite.de