Bug#847701: kodi: Movie player unusable with libva error

[Bálint Réczey <balint@balintreczey.hu>]

Hi Leandro,

2017-01-14 11:29 GMT+01:00 Leandro Noferini <lnoferin@cybervalley.org>:
> Bálint Réczey <balint@balintreczey.hu> writes:
>
>
> [...]
>
>> It looks like the system is really slow for the video.
>
> But really it was very good before the upgrade of kodi.

Do you know which kodi upgrade broke it? Can you revert to a kodi
version which does work?

>
>> I have reinstalled a similar system and playing videos was very slow
>> on it, indeed.
>>
>> The system:
>> $ cat /proc/cpuinfo
>> processor    : 0
>> vendor_id    : GenuineIntel
>> cpu family    : 6
>> model        : 28
>> model name    : Intel(R) Atom(TM) CPU N270   @ 1.60GHz
>> stepping    : 2
>> microcode    : 0x208
>> cpu MHz        : 1067.000
>> cache size    : 512 KB
>> physical id    : 0
>> siblings    : 2
>> core id        : 0
>> cpu cores    : 1
>> ...
>
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 28
> model name      : Intel(R) Atom(TM) CPU D525   @ 1.80GHz
> stepping        : 10
> microcode       : 0x107
> cpu MHz         : 1799.931
> cache size      : 512 KB
> physical id     : 0
> siblings        : 4
> core id         : 0
> cpu cores       : 2
> apicid          : 0
> initial apicid  : 0
> 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 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf eagerfpu pni dtes64 monitor ds_cpl tm2 ssse3 cx16 xtpr pdcm movbe lahf_lm dtherm
> bugs            :
> bogomips        : 3599.86
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 36 bits physical, 48 bits virtual
> power management:
>
> [And the same for other three cores]
>
>> # lspci -v -s 00:02.1
>> 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME,
>> 943/940GML Express Integrated Graphics Controller (rev 03)
>>     Subsystem: Fujitsu Technology Solutions Mobile 945GM/GMS/GME,
>> 943/940GML Express Integrated Graphics Controller
>>     Flags: bus master, fast devsel, latency 0
>>     Memory at f8180000 (32-bit, non-prefetchable) [size=512K]
>>     Capabilities: [d0] Power Management version 2
>
> root@pinolino:~# lspci -v -s 00:02.0
> 00:02.0 VGA compatible controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])
>         Subsystem: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
>         Flags: bus master, fast devsel, latency 0, IRQ 29
>         Memory at e0200000 (32-bit, non-prefetchable) [size=512K]
>         I/O ports at 20c0 [size=8]
>         Memory at d0000000 (32-bit, prefetchable) [size=256M]
>         Memory at e0100000 (32-bit, non-prefetchable) [size=1M]
>         [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
>         Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
>         Capabilities: [d0] Power Management version 2
>         Kernel driver in use: i915
>         Kernel modules: i915
>
>> I have collected some profiling data by running:
>>
>> $ perf record -g kodi
>>
>> Which shows that ~70% of the time is spent in intel's mesa driver:
>>
>> $ perf report --sort comm,dso | cat
>
> [...]
>
> I made the same experiment (consider I am not a technician) and I have
> got some datas: do you need these datas?

If you have very different results regarding where most time is spent
they may be interesting.

Cheers,
Balint