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: Fri, 26 Jul 2019 03:00:48 +0000	[thread overview]
Message-ID: <bug-111213-8800-ua5k1p6CBg@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111213-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #4 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
Good news -

../src/gallium/drivers/nouveau/nvc0/nve4_compute.c:396:
nve4_compute_validate_constbufs: Assertion `i > 0' failed.

also happens with vdpau. It's because we don't expect ever receiving a non-user
constbuf at position 0. Will add handling for it.

-- 
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: 1271 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-26  3:00 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 [this message]
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
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-ua5k1p6CBg@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.