All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 111213] VA-API nouveau SIGSEGV and asserts
Date: Sat, 27 Jul 2019 01:34:54 +0000	[thread overview]
Message-ID: <bug-111213-8800-e7LdgIXkt2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111213-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 7220 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=111213

--- Comment #6 from KJ Liew <liewkj-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> ---
I don't know how you had verified VDPAU to make sure it is working. Running
vdpauinfo is not enough. I used the VA-API translation layer for VDPAU backend
since my goal is to get VA-API. I had also verified that the VA-API translation
layer worked with nvidia-390xx propriety blobs and Chromium-vaapi accelerated
H264 playback.

The change *ONLY* fixed "vainfo & vdpauinfo SIGSEGV due to NULL pointer".

$ LIBVA_DRIVER_NAME=vdpau vainfo
vainfo: VA-API version: 1.5 (libva 2.5.0)
vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API -
0.7.4
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileMPEG4Simple            : VAEntrypointVLD
      VAProfileMPEG4AdvancedSimple    : VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointVLD
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD


$ LIBVA_DRIVER_NAME=vdpau VDPAU_DRIVER=nouveau chromium
[19735:19735:0726/182126.662312:ERROR:vaapi_wrapper.cc(455)]
GetConfigAttributes failed for va_profile 13
[19735:19735:0726/182126.662353:ERROR:vaapi_wrapper.cc(455)]
GetConfigAttributes failed for va_profile 6
[19735:19735:0726/182126.662359:ERROR:vaapi_wrapper.cc(455)]
GetConfigAttributes failed for va_profile 7
[19735:19735:0726/182126.764805:ERROR:sandbox_linux.cc(368)]
InitializeSandbox() called with multiple threads in process gpu-process.
[19735:19735:0726/182126.808082:ERROR:buffer_manager.cc(488)]
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error
from previous GL command
romium/chromium --type=gpu-process
--field-trial-handle=7302155616383548209,8433935369873353489,131072
--disable-breakpad
--gpu-preferences=KAAAAAAAAAAgAACgAQAAAAAAAAAAAGAAAAAAAAAAAAAIAAAAAAAAAAgAAAAAAAAA
--service-request-channel-token=6382519074401266972:
../mesa-19.1.3/src/gallium/drivers/nouveau/nvc0/nvc0_video.c:43:
nvc0_decoder_begin_frame: Assertion `ret == 2' failed.

There was a long pause, I think the GPU process crashed and then restarted with
more lengthy logs spit until Chromium was killed

[20217:20217:0726/182241.032544:ERROR:vaapi_wrapper.cc(455)]
GetConfigAttributes failed for va_profile 13
[20217:20217:0726/182241.032617:ERROR:vaapi_wrapper.cc(455)]
GetConfigAttributes failed for va_profile 6
[20217:20217:0726/182241.032636:ERROR:vaapi_wrapper.cc(455)]
GetConfigAttributes failed for va_profile 7
[20217:20217:0726/182241.120438:ERROR:sandbox_linux.cc(368)]
InitializeSandbox() called with multiple threads in process gpu-process.
[20217:20217:0726/182241.149352:ERROR:buffer_manager.cc(488)]
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error
from previous GL command
[20217:20217:0726/182241.204625:ERROR:gles2_cmd_decoder.cc(18461)]
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION :
glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[20217:20217:0726/182241.208930:ERROR:gles2_cmd_decoder.cc(10734)]
[.DisplayCompositor]RENDER WARNING: texture bound to texture unit 0 is not
renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20217:20217:0726/182255.379961:ERROR:gles2_cmd_decoder.cc(10734)]
[.DisplayCompositor]RENDER WARNING: texture bound to texture unit 0 is not
renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20217:20217:0726/182255.400308:ERROR:gles2_cmd_decoder.cc(10734)]
[.DisplayCompositor]RENDER WARNING: texture bound to texture unit 0 is not
renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20217:20217:0726/182256.316376:ERROR:gles2_cmd_decoder.cc(10734)]
[.DisplayCompositor]RENDER WARNING: texture bound to texture unit 0 is not
renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20217:20217:0726/182256.344654:ERROR:gles2_cmd_decoder.cc(10734)]
[.DisplayCompositor]RENDER WARNING: texture bound to texture unit 0 is not
renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20217:20217:0726/182256.350918:ERROR:gles2_cmd_decoder.cc(10734)]
[.DisplayCompositor]RENDER WARNING: texture bound to texture unit 0 is not
renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20217:20217:0726/182256.363405:ERROR:gles2_cmd_decoder.cc(10734)]
[.DisplayCompositor]RENDER WARNING: texture bound to texture unit 0 is not
renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20217:20217:0726/182256.394713:ERROR:gles2_cmd_decoder.cc(10734)]
[.DisplayCompositor]RENDER WARNING: texture bound to texture unit 0 is not
renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20217:20217:0726/182256.396760:ERROR:gles2_cmd_decoder.cc(10734)]
[.DisplayCompositor]RENDER WARNING: texture bound to texture unit 0 is not
renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20217:20217:0726/182256.411122:ERROR:gles2_cmd_decoder.cc(10734)]
[.DisplayCompositor]RENDER WARNING: texture bound to texture unit 0 is not
renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20217:20217:0726/182256.442865:ERROR:gles2_cmd_decoder.cc(10734)]
[.DisplayCompositor]RENDER WARNING: texture bound to texture unit 0 is not
renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20217:20217:0726/182256.445224:ERROR:gles2_cmd_decoder.cc(10734)]
[.DisplayCompositor]RENDER WARNING: texture bound to texture unit 0 is not
renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20217:20217:0726/182256.503684:ERROR:gles2_cmd_decoder.cc(10734)]
[.DisplayCompositor]RENDER WARNING: texture bound to texture unit 0 is not
renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20217:20217:0726/182256.530002:ERROR:gles2_cmd_decoder.cc(10734)]
[.DisplayCompositor]RENDER WARNING: texture bound to texture unit 0 is not
renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20217:20217:0726/182256.547899:ERROR:gles2_cmd_decoder.cc(10734)]
[.DisplayCompositor]RENDER WARNING: texture bound to texture unit 0 is not
renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20217:20217:0726/182256.583440:ERROR:gles2_cmd_decoder.cc(10734)]
[.DisplayCompositor]RENDER WARNING: texture bound to texture unit 0 is not
renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[20217:20217:0726/182256.589853:ERROR:gles2_cmd_decoder.cc(10734)]
[.DisplayCompositor]RENDER WARNING: texture bound to texture unit 0 is not
renderable. It maybe non-power-of-2 and have incompatible texture filtering.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 7974 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2019-07-27  1:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-25  7:16 [Bug 111213] New: VA-API nouveau SIGSEGV and asserts bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-111213-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2019-07-25 12:33   ` [Bug 111213] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-25 14:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-25 17:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-26  3:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-26  3:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-27  1:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2019-07-27  2:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-27  2:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-28  3:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-29 13:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-29 22:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-29 23:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-10 17:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-10 18:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-11  0:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-11  0:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-13 22:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-21  4:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-24  2:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-24  2:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-111213-8800-e7LdgIXkt2@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.