CPU extensions are not detected

Bug #684198 reported by Carlos Eduardo Moreira dos Santos
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
x264 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: x264

Expected output (intel E3300):
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64
Current output:
x264 [info]: using cpu capabilities: none!

Is it possible to remove "--disabe-asm" from configure flags?

Revision history for this message
Reinhard Tartler (siretart) wrote :

seems that the kernel doesn't detect the processors SSE2 capabilities.

please provide the output of the following commands:

# to check what version of the libx264.so library is picked up
$ ldd /usr/bin/x264

# check cpu capabilities
$ cat /proc/cpuinfo

Changed in x264 (Ubuntu):
status: New → Invalid
status: Invalid → Incomplete
Revision history for this message
Carlos Eduardo Moreira dos Santos (cemsbr) wrote :

Recompiling x264 from git worked for me. Requested information:

$ ldd /usr/bin/x264
 linux-gate.so.1 => (0x00e68000)
 libm.so.6 => /lib/libm.so.6 (0x00b21000)
 libpthread.so.0 => /lib/libpthread.so.0 (0x00175000)
 libavformat.so.52 => /usr/lib/i686/cmov/libavformat.so.52 (0x00435000)
 libswscale.so.0 => /usr/lib/i686/cmov/libswscale.so.0 (0x0061d000)
 libavcodec.so.52 => /usr/lib/i686/cmov/libavcodec.so.52 (0x00e69000)
 libc.so.6 => /lib/libc.so.6 (0x0018f000)
 /lib/ld-linux.so.2 (0x00cbf000)
 libavutil.so.50 => /usr/lib/i686/cmov/libavutil.so.50 (0x00860000)
 libz.so.1 => /lib/libz.so.1 (0x00983000)
 libbz2.so.1.0 => /lib/libbz2.so.1.0 (0x00110000)
 libva.so.1 => /usr/lib/libva.so.1 (0x002f1000)
 libgsm.so.1 => /usr/lib/libgsm.so.1 (0x00122000)
 libschroedinger-1.0.so.0 => /usr/lib/libschroedinger-1.0.so.0 (0x00795000)
 libspeex.so.1 => /usr/lib/sse2/libspeex.so.1 (0x00130000)
 libtheoraenc.so.1 => /usr/lib/libtheoraenc.so.1 (0x002f8000)
 libtheoradec.so.1 => /usr/lib/libtheoradec.so.1 (0x00e44000)
 libvorbisenc.so.2 => /usr/lib/libvorbisenc.so.2 (0x00998000)
 libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x0014d000)
 libvpx.so.0 => /usr/lib/libvpx.so.0 (0x0033c000)
 libdl.so.2 => /lib/libdl.so.2 (0x002ed000)
 liborc-0.4.so.0 => /usr/lib/liborc-0.4.so.0 (0x003d8000)
 libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00bb7000)
 libogg.so.0 => /usr/lib/libogg.so.0 (0x00505000)

$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Celeron(R) CPU E3300 @ 2.50GHz
stepping : 10
cpu MHz : 1203.000
cache size : 1024 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm xsave lahf_lm dts tpr_shadow vnmi flexpriority
bogomips : 5029.50
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
(...)

Revision history for this message
Reinhard Tartler (siretart) wrote : Re: [Bug 684198] Re: CPU extensions are not detected

On Fri, Dec 03, 2010 at 04:06:06 (CET), Carlos Eduardo Moreira dos Santos wrote:

> Recompiling x264 from git worked for me.

yes, but makes the requested output worthless. The package ships two
copies of libx264.so, one compiled with sse2 support and one without. we
now need to find out why it's picking up the wrong copy on your system.

you've now overwritten the x264 binary with a copy that statically links
the correct copy.

--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4

Revision history for this message
Carlos Eduardo Moreira dos Santos (cemsbr) wrote :

No, the output is from /usr/bin/x264 and the working x264 compiled by myself is in another path.

Revision history for this message
Carlos Eduardo Moreira dos Santos (cemsbr) wrote :

Another thing to check: was yasm installed before compiling repository binaries?

Revision history for this message
Loïc Martin (loic-martin3) wrote :

Using 2:0.98.1653+git88b90d9-3 in Maverick (32 bits) I don't have this problem on a C2Q 9550. I didn't see Carlos version anywhere on the thread, so sorry if it's there but I missed it.

Revision history for this message
Reinhard Tartler (siretart) wrote :

Carlos, can you please state the exact package version that is causing problems to you please?

Revision history for this message
Carlos Eduardo Moreira dos Santos (cemsbr) wrote :

$ /usr/bin/x264 --version
x264 0.98.1653 Ubuntu_2:0.98.1653+git88b90d9-3
built on Oct 5 2010, gcc: 4.4.5

(32 bits)

Revision history for this message
Carlos Eduardo Moreira dos Santos (cemsbr) wrote :

This error can be reproduced in 3 machines, all with intel processors. The workaround (compiling x264) works in all of them. Let me know if you need more data.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for x264 (Ubuntu) because there has been no activity for 60 days.]

Changed in x264 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.