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 02:21:20 +0000	[thread overview]
Message-ID: <bug-111213-8800-a8f1lKLG4I@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111213-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #8 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
(In reply to KJ Liew from comment #6)
> I don't know how you had verified VDPAU to make sure it is working. Running
> vdpauinfo is not enough.

mplayer -vo vdpau the-video

See https://nouveau.freedesktop.org/wiki/VideoAcceleration/ -- "Using VDPAU".
(You also have to tell it to use the "vdpau" codecs.)

> $ 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.

Ah yeah, that's something else.

This appears like it would happen as a result of

   ret = nouveau_bo_map(bsp_bo, NOUVEAU_BO_WR, dec->client);

failing. No clue how that could happen... OTOH, I see messages about threads,
and certainly video decoding + GL in different threads is highly likely to be
broken with nouveau.

Please try to build a debug version, see if that yields more info. Also look
for errors in dmesg.

-- 
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: 3118 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  2:21 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
2019-07-27  2:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-27  2:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
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-a8f1lKLG4I@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.