Hi Anuj, I attached the complete chromium log here.
Thank you, Huy On Wed, Jun 7, 2023 at 8:58 AM HuyK via lists.yoctoproject.org <[email protected]> wrote: > Hi Anuj, > > Thank you for the quick response with positive information. It makes me > feel warm about our community. > > 1- "This doesn't look like complete error log. A complete log would have > helped." > Do you mean a complete run log from chromium? I will submit a full running > log when I run chromium soon. > > 2- Regarding the suggestion in > https://github.com/intel/media-driver/issues/1498 > I reviewed that suggestion during my self-research for a solution. It > suggests using chromium r107 and adding > --disable-features=UseChromeOSDirectVideoDecoder > However, I do not know which chromium recipe version for that r107. For > the flag UseChromOSDirectVideoDecoder, I already have that. > > Thank you, > Huy > > > On Wed, Jun 7, 2023 at 8:49 AM Mittal, Anuj <[email protected]> wrote: > >> On Wed, 2023-06-07 at 08:24 +0700, HuyK wrote: >> > Hi all, >> > >> > I am working on Intel J4125 platform with these meta layers: >> > - poky: master branch >> > - meta-intel: master branch >> > - meta-browser: master branch >> > >> > 1/ I build chromium by chromium-ozone-wayland_111.0.5563.147.bb >> > recipe with adding "use-vaapi" and "proprietary-codecs" to >> > PACKAGECONFI in chromium-gn.inc >> > That chromium did not call intel VAAPI functions, but I see it >> > loads iHD_drv_video.so at runtime. >> > >> > 2/ Then I research to find this link about applying patches to >> > support VAAPI in >> > chromium https://aur.archlinux.org/packages/chromium-wayland-vaapi >> > + 0001-ozone-wayland-add-VA-API-support.patch >> > + vaapi-add-av1-support.patch >> > + use-oauth2-client-switches-as-default.patch >> > This chromium loads iHD_drv_video.so and calls Intel VAAPI APIs; >> > however, chromium reports these errors when I open to play an H264 >> > video so that HW Acceleration is not working >> > >> > [13436:13436:0606/150528.263552:ERROR:vaapi_wrapper.cc(2399)] >> > vaCreateSurfaces (import mode) failed, VA error: resource allocation >> > failed >> > [13436:13436:0606/150528.263789:ERROR:vaapi_picture_native_pixmap_ozo >> > ne.cc(73)] Failed creating VASurface for NativePixmap >> > [13436:13436:0606/150528.264843:ERROR:vaapi_wrapper.cc(2399)] >> > vaCreateSurfaces (import mode) failed, VA error: resource allocation >> > failed >> > [13436:13436:0606/150528.265073:ERROR:vaapi_picture_native_pixmap_ozo >> > ne.cc(73)] Failed creating VASurface for NativePixmap >> > [13436:13436:0606/150528.265294:VERBOSE1:vaapi_video_decode_accelerat >> > or.cc(142)] NotifyError(): Notifying of error 4 >> >> This doesn't look like complete error log. A complete log would have >> helped. >> >> > >> > So far, I could not find a solution to fix chromium errors and I am >> > new to chromium, intel vaapi, libva debugging. >> > >> > Please support how to debug the errors there or guidance on how to >> > officially build chromium with intel VAAPI support in Yocto? >> >> This doesn't seem to be Yocto related. This looks very similar so >> please try the suggestions here: >> >> https://github.com/intel/media-driver/issues/1498 >> >> Thanks, >> >> Anuj >> > > > >
sh-5.2$ source ./start_chromium.sh [3980:3980:0607/122727.876476:WARNING:chrome_main_delegate.cc(618)] This is Chrome version 111.0.5563.147 (not a warning) [3980:3980:0607/122727.965150:WARNING:wayland_object.cc(152)] Binding to zwp_linux_dmabuf_v1 version 3 but version 4 is available. [3980:3980:0607/122728.036300:WARNING:wayland_surface.cc(149)] Server doesn't support zcr_alpha_compositing_v1. [3980:3980:0607/122728.036337:WARNING:wayland_surface.cc(164)] Server doesn't support overlay_prioritizer. [3980:3980:0607/122728.036345:WARNING:wayland_surface.cc(178)] Server doesn't support surface_augmenter. [3980:3980:0607/122728.036352:WARNING:wayland_surface.cc(193)] Server doesn't support wp_content_type_v1 [3980:3980:0607/122728.036358:WARNING:wayland_surface.cc(212)] Server doesn't support zcr_color_management_surface. [3980:3980:0607/122728.037024:WARNING:cursor_loader.cc(123)] Failed to load a platform cursor of type kNull libva info: Open new log file /tmp/libva.122728.thd-0x00000fbe for the thread 0x00000fbe libva info: LIBVA_TRACE is on, save log into /tmp/libva.122728.thd-0x00000fbe libva info: VA-API version 1.17.0 libva info: Trying to open /usr/lib/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_17 libva info: va_openDriver() returns 0 [4030:4030:0607/122728.083000:ERROR:gpu_init.cc(525)] Passthrough is not supported, GL is egl, ANGLE is [4030:4030:0607/122728.089781:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called with multiple threads in process gpu-process. [3980:3980:0607/122728.094363:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable. [3980:3980:0607/122756.467072:INFO:CONSOLE(22)] "The Content Security Policy 'child-src 'unsafe-inline' cm.g.doubleclick.net googleads.g.doubleclick.net www.google. com accounts.google.com pagead2.googlesyndication.com/pagead/s/cookie_push.html gmsg: https://tpc.googlesyndication.com/sadbundle/$csp%3Der3$/12934228281280879862/i ndex.html;frame-src 'unsafe-inline' cm.g.doubleclick.net googleads.g.doubleclick.net www.google.com accounts.google.com pagead2.googlesyndication.com/pagead/s/cooki e_push.html gmsg: https://tpc.googlesyndication.com/sadbundle/$csp%3Der3$/12934228281280879862/index.html' was delivered via a <meta> element outside the document's <head>, which is disallowed. The policy has been ignored.", source: https://googleads.g.doubleclick.net/pagead/html/r20230601/r20110914/zrt_lookup.html?fsb=1 (22) [3980:3980:0607/122758.821762:WARNING:cursor_loader.cc(123)] Failed to load a platform cursor of type kHand [4030:4030:0607/122759.781037:VERBOSE2:vaapi_video_decode_accelerator.cc(200)] Initialize(): Initializing VAVDA, profile: h264 high libva info: Open new log file /tmp/libva.122759.thd-0x00000fbe for the thread 0x00000fbe libva info: LIBVA_TRACE is on, save log into /tmp/libva.122759.thd-0x00000fbe libva info: VA-API version 1.17.0 libva info: Trying to open /usr/lib/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_17 libva info: va_openDriver() returns 0 [4030:4573:0607/122759.786123:VERBOSE2:vaapi_video_decode_accelerator.cc(487)] DecodeTask(): Decoder requesting a new set of surfaces [4030:4030:0607/122759.786393:VERBOSE2:vaapi_video_decode_accelerator.cc(582)] InitiateSurfaceSetChange(): |requested_num_pics_| = 13; |requested_num_reference_fra mes_| = 0 [4030:4030:0607/122759.786547:VERBOSE2:vaapi_video_decode_accelerator.cc(648)] TryFinishSurfaceSetChange(): Requesting 13 pictures of size: 1920x1088 and visible re ctangle = 0,0 1920x1080 [4030:4030:0607/122759.794571:ERROR:vaapi_wrapper.cc(2399)] vaCreateSurfaces (import mode) failed, VA error: resource allocation failed [4030:4030:0607/122759.794773:ERROR:vaapi_picture_native_pixmap_ozone.cc(73)] Failed creating VASurface for NativePixmap [4030:4030:0607/122759.800235:ERROR:vaapi_wrapper.cc(2399)] vaCreateSurfaces (import mode) failed, VA error: resource allocation failed [4030:4030:0607/122759.800357:ERROR:vaapi_picture_native_pixmap_ozone.cc(73)] Failed creating VASurface for NativePixmap [4030:4030:0607/122759.800507:VERBOSE1:vaapi_video_decode_accelerator.cc(142)] NotifyError(): Notifying of error 4 [4030:4030:0607/122759.804536:VERBOSE2:vaapi_video_decode_accelerator.cc(1045)] Cleanup(): Destroying VAVDA
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60209): https://lists.yoctoproject.org/g/yocto/message/60209 Mute This Topic: https://lists.yoctoproject.org/mt/99376559/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
