From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 111213] New: VA-API nouveau SIGSEGV and asserts
Date: Thu, 25 Jul 2019 07:16:35 +0000 [thread overview]
Message-ID: <bug-111213-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111213
Bug ID: 111213
Summary: VA-API nouveau SIGSEGV and asserts
Product: Mesa
Version: 19.0
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: liewkj-/E1597aS9LQAvxtiuMwx3w@public.gmane.org
QA Contact: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Tested hardware: Geforce 9300 mGPU (NVAC), GT730-GK208B (NV106)
VA-API apps: gstreamer-vaapi, Chromium-vaapi-bin(AUR)
OS: ArchLinux x86_64 kernel 5.2.2-arch1-1-ARCH
GUI: GNOME/Wayland using nouveau
- vainfo & vdpauinfo SIGSEV due to NULL pointer
ArchLinux discussion thread
https://bbs.archlinux.org/viewtopic.php?id=247466
- h264 video decode failed with assertion and tendency to crash GNOME/GUI
Test h264 clip:
$ youtube-dl -f mp4 https://www.youtube.com/watch?v=azvR__GRQic
Gstreamer command line
$ gst-launch-1.0 playbin uri=file:///path/to/MP4
or
$ gst-launch-1.0 filesrc location=/path/to/MP4 ! qtdemux ! vaapidecodebin !
vaapisink
Use enhanced-h264ify plugin on Chromium to playback the same h264 video clip
from YouTube.com
Geforce 9300 mGPU - video played as garbage, browser may crash
GT730 - fallback to FFmpegVideoDecoder after asserts
ve4_set_surface_info:969 - unsupported surface format, try
is_format_supported() !
romium/chromium --type=gpu-process
--field-trial-handle=7734813049068668419,17986421265460211344,131072
--disable-breakpad
--gpu-preferences=KAAAAAAAAAAgAACgAQAAAAAAAAAAAGAAAAAAAAAAAAAIAAAAAAAAAAgAAAAAAAAA
--service-request-channel-token=7551475798706255496:
../mesa-19.1.3/src/gallium/drivers/nouveau/nvc0/nve4_compute.c:396:
nve4_compute_validate_constbufs: Assertion `i > 0' failed.
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3498 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2019-07-25 7:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 7:16 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-111213-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2019-07-25 12:33 ` [Bug 111213] VA-API nouveau SIGSEGV and asserts 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
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@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox