+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52)
+---- Thread: Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server (/showthread.php?tid=231955)
Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
RE: New Era: VAAPI with EGL interoperation - gurabli - 2015-08-10
(2015-08-10, 15:00)fritsch Wrote: https://github.com/FernetMenta/xbmc/commits/master
Many thanks!
RE: New Era: VAAPI with EGL interoperation - Ales - 2015-08-10
I have a strange issue on recent build. Kodi crashes while opening any jpeg picture.
The last line in Kodi log and crashlog is:
Code:
19:38:06 T:140235400988608 DEBUG: Loading: /usr/lib/kodi/system/libexif-x86_64-linux.soCode:
aug 10 19:38:06 htpc kernel: kodi.bin[4863]: segfault at 7fffd21b9f6c ip 00007f8b11f47d5d sp 00007fffd2179de8 error 6 in libc-2.21.so[7f8b11ec4000+199000]I'm on Archlinux, Kodi built from FernetMenta master git branch.
The only error I have in kodi log for a long time is:
Code:
ERROR: CWinSystemX11::XErrorHandler: BadAtom (invalid Atom parameter), type:0, serial:43, error_code:5, request_code:18 minor_code:0RE: New Era: VAAPI with EGL interoperation - fritsch - 2015-08-11
(2015-08-10, 22:18)Ales Wrote: The only error I have in kodi log for a long time is:May I be interested in this error?Code:ERROR: CWinSystemX11::XErrorHandler: BadAtom (invalid Atom parameter), type:0, serial:43, error_code:5, request_code:18 minor_code:0
That one you can ignore. We try to disable the KWIn Compositor, but don't check if it is running at all.
Please also post all the stuff - that you don't think is relevant to you.
Edit: And obviously we need the complete backtrace ... if we don't find anything - blame GCC 5.1 - would not be the first time.
Edit2: The only exif change since a long time was: 3b42ef03375396480bf3a8e942b39353e68ecda9 but a backtrace will clearly show the issue, with enabled debugging - even better.
RE: New Era: VAAPI with EGL interoperation - Ales - 2015-08-11
Thank You fritsch for your kind helping!
mesa: http://paste.ubuntu.com/12054407/
vainfo: http://paste.ubuntu.com/12054409/
kodi.old.log: http://paste.ubuntu.com/12054432/
dmesg: http://paste.ubuntu.com/12054438/
RE: New Era: VAAPI with EGL interoperation - fritsch - 2015-08-11
The crashlog also, please this is the important one with the gdb backtrace.
GCC 5.2.0 - too much time or what? :-)
Here: [ 44.462581] kodi.bin[525]: segfault at 7fff35b8f1ac ip 00007ff61c323d5d sp 00007fff35b4f028 error 6 in libc-2.21.so[7ff61c2a0000+199000] - that looks like an arch fuckup ... man ... we want to test kodi and not the newest and greatest arch stack :-(
Btbn Wrote:The upgrade procedure for gcc 4.x to 5 is also quite fun. Upgrade
gcc, and then rebuild _everything_ 3~5 times, until there are no
errors left
Did you do this:
Btbn Wrote:fritsch, you essentialy have to rebuild until you don't find any
references to the old libgcc abi in any binary on your system.
And as stuff happily depends on each other, it's quite a few
rounds of rebuilds until that is achived.
And then you still have to deal with the potential breakage the
new gcc version might cause
Edit: All of this makes me think, that I just don't support Arch Linux in this thread - too much pain ...
RE: New Era: VAAPI with EGL interoperation - Ales - 2015-08-11
There is a crashlog just out of curiosity: http://paste.ubuntu.com/12054504/
I think the issue is in my distro too, just as you said, so I will try to fight with that myself.
RE: New Era: VAAPI with EGL interoperation - fritsch - 2015-08-11
Quote:/home/player/pictures/FOTKY/Balů a Larry/2008/_DSC0025.JPGCan you rename that folder? :-) from Balů to Balu?
RE: New Era: VAAPI with EGL interoperation - Ales - 2015-08-11
I have tried it just now and it is the same. I appreciate your effort, but it really seems it is in gcc. I will try to downgrade some packages...
RE: New Era: VAAPI with EGL interoperation - fritsch - 2015-08-11
(2015-08-11, 11:49)Ales Wrote: I have tried it just now and it is the same. I appreciate your effort, but it really seems it is in gcc. I will try to downgrade some packages...
Recompile complete packages - this always needs to be done, when libgcc is bumped - I am afraid. Do it 3 to 5 times as mentioned above.
RE: New Era: VAAPI with EGL interoperation - wsnipex - 2015-08-11
(2015-08-11, 11:57)fritsch Wrote:(2015-08-11, 11:49)Ales Wrote: I have tried it just now and it is the same. I appreciate your effort, but it really seems it is in gcc. I will try to downgrade some packages...
Recompile complete packages - this always needs to be done, when libgcc is bumped - I am afraid. Do it 3 to 5 times as mentioned above.
its only necessary cause gcc 5.2 changed the default c++11 abi
RE: New Era: VAAPI with EGL interoperation - pxpert - 2015-08-12
Hi all! I'm using XBMC, now KODI since a long time.
I came here to try the vaapi accelleration for my brand new asrock motherboard with Celeron N3150.
I'm currently using this configuration:
- Gentoo box w/ kernel 4.1.1-gentoo-r1
- Mesa GIT/SVN/CVS Build 18:08:48 26/07/2015
- x11-base/xorg-server 1.17.1-r1
- x11-drivers/xf86-video-intel GIT/SVN/CVS Build 18:38:31 26/07/2015
- x11-libs/libva GIT/SVN/CVS Build 10:07:51 12/08/2015
- x11-libs/libva-intel-driver GIT/SVN/CVS Build 10:05:51 12/08/2015
and now compiled Kodi using Fernetmenta GIT repo (12/08/2015)
All seems to work correctly, but when I enable vaapi menu, the playback window is totally black and i can only hear the video playing.
This is my log: http://pastebin.com/s9zmvNpw
It seems this is the problem from the log: failed to import VA buffer NV12 into EGL image: 12292
Can you please help me?
PS Long life Gentoo.. and kodi!
RE: New Era: VAAPI with EGL interoperation - wsnipex - 2015-08-12
your mesa is most probably missing the NV12 extension. But since you cut the log, I'm just guessing
RE: New Era: VAAPI with EGL interoperation - fritsch - 2015-08-12
Yeah +1 - the mesa extension is missing. Either build mesa git (master) or pick the patches wsnipex ships in his repository.
RE: New Era: VAAPI with EGL interoperation - Ales - 2015-08-12
(2015-08-11, 11:57)fritsch Wrote: Recompile complete packages - this always needs to be done, when libgcc is bumped - I am afraid. Do it 3 to 5 times as mentioned above.
I have spent few hours of compiling yesterday and it works perfectly again.
Thanks very much!
PS: I'm considering migrating to Ubuntu with this hw.
RE: New Era: VAAPI with EGL interoperation - trsqr - 2015-08-13
I mentioned yesterday that there seems to be some strange behaviour when it comes to memory usage of kodi. With the OpenELEC build from post #2 it crashes after watching n videos (where n seems to be something between 50 and 100 in my system). After each video, kodi seems to consume more memory according to system info page. The system became unusable when memory usage was at 72%.
Then I prepared an ubuntu system according to post #1 and #2. The memory usage is approximately 300 megs when I start kodi. After each video it seems to raise a bit. I took screen shots from the situation and stored them at http://trsqr.net/kodi . Strange thing is, the memory consumption reaches 83% (on my 4GB RAM system that corresponds to Kodi using 3120 MB RAM), but never goes further from that. Also, the system stays completely usable. When I quit Kodi everything is fine and all memory is available. When I start it again, this sequence starts from the beginning.
I did run valgrind with parameters --logfile=filename, --leak-check=full and --undef-value-errors=no, but the results do not show anything. The result is in the text file in the above link.
Another strange thing is, that if I disable VA-API from Kodi settings, the memory usage stays at around 300 megs no matter how many times I watch Big Buck Bunny. With VA-API enabled, it seemed to go up 5-30 MB after each video viewing. It seemed to grow fastest when using the video http://distribution.bbb3d.renderfarming.net/video/mp4/bbb_sunflower_2160p_60fps_normal.mp4 .
dmesg: http://paste.ubuntu.com/12066513/
dpkg -l: http://paste.ubuntu.com/12065976/
vainfo: http://paste.ubuntu.com/12066521/
kodi.log with debugging, watched two movies with VA-API and exited (memory usage was 500 megs at that point): http://paste.ubuntu.com/12066571/
Can I somehow further debug this?