From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 99584] New: XVMC on nv43 class card broken with recent mesa + kernel.
Date: Sun, 29 Jan 2017 07:27:59 +0000 [thread overview]
Message-ID: <bug-99584-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1679 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99584
Bug ID: 99584
Summary: XVMC on nv43 class card broken with recent mesa +
kernel.
Product: Mesa
Version: git
Hardware: x86 (IA32)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: randrik-JGs/UdohzUI@public.gmane.org
QA Contact: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Hello again.
Not sure if anyone will look into this, but I run into bug where xvmc state
tracker/nouveau failed for me in multiple ways, depending on exact kernel/mesa
combination.
With kernel 4.2.0 new mesa (Mesa 17.1.0-devel git-12dcad1) compiled agains
recent libdrm (d4b8344363b4e0f0e831e5722b6df5cc0bb08df8
Author: Chad Versace <chadversary-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Date: Fri Jan 27 12:18:00 2017 -0800
Bump version for 2.4.75 release)
produces pink window.
With more mdoern kernel (4.10-rc5). whole device creation failed.
Test commandline:
/home/guest/src/mesa/src/gallium/state_trackers/xvmc/tests/xvmc_bench
result:
Acceleration level: IDCT
Creation failed: No such device (-19)
xvmc_bench: tests/xvmc_bench.c:238: main: Assertion `XvMCCreateContext(display,
port_num, surface_type_id, config.input_width, config.input_height, 0x00000001,
&context) == 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: 3019 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2017-01-29 7:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-29 7:27 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-99584-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-01-29 7:29 ` [Bug 99584] XVMC on nv43 class card broken with recent mesa + kernel bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-29 7:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-29 21:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-19 2:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-26 3:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-26 5:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-26 6:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-25 12:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:44 ` 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-99584-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 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.