From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org Subject: [Bug 99584] XVMC on nv43 class card broken with recent mesa + kernel. Date: Sun, 19 Mar 2017 02:24:35 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0962409494==" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: nouveau-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Sender: "Nouveau" To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org List-Id: nouveau.vger.kernel.org --===============0962409494== Content-Type: multipart/alternative; boundary="14898902751.73D3CdFD.3400"; charset="UTF-8" --14898902751.73D3CdFD.3400 Date: Sun, 19 Mar 2017 02:24:35 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D99584 --- Comment #4 from Ilia Mirkin --- FWIW with mesa 17.0.1 and kernel 4.10.4, I'm unable to fully reproduce the issue. I have a NV4A, which uses the nv44 mpeg object, which in turn is rat= her different than the "plain" nv40 one which you have. I get a ton of warnings in dmesg: [15871.309494] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]] 01000000 00000010 000001b0 00006051 [15871.309516] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]] 01000000 00000020 00000380 0058b000 [15871.309531] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]] 01000000 00000020 0000038c 0068b000 [15871.326326] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]] 01000000 00000020 00000380 0058b000 [15871.326356] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]] 01000000 00000020 00000384 0000b350 [15871.326371] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]] 01000000 00000020 0000038c 0068b000 [15871.326385] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]] 01000000 00000020 00000390 000467e8 [15871.372669] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]] 01000000 00000020 00000380 0058b000 [15871.372690] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]] 01000000 00000020 00000384 000069c0 [15871.372708] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]] 01000000 00000020 0000038c 0068b000 [15871.372723] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]] 01000000 00000020 00000390 00010604 and so on. The first one is harmless (simple bug that causes it to be print= ed instead of hidden), but the rest are harmful. The end-result is random junk= on the screen, but that makes perfect sense given the above errors. I have fix= es for some things, but not others. Will update when I have fixed my setup. --=20 You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.= --14898902751.73D3CdFD.3400 Date: Sun, 19 Mar 2017 02:24:35 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comment= # 4 on bug 99584<= /a> from Ilia Mirkin 
FWIW with mesa 17.0.1 and kernel 4.10.4, I'm unable to fully r=
eproduce the
issue. I have a NV4A, which uses the nv44 mpeg object, which in turn is rat=
her
different than the "plain" nv40 one which you have.

I get a ton of warnings in dmesg:

[15871.309494] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]]
01000000 00000010 000001b0 00006051
[15871.309516] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]]
01000000 00000020 00000380 0058b000
[15871.309531] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]]
01000000 00000020 0000038c 0068b000
[15871.326326] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]]
01000000 00000020 00000380 0058b000
[15871.326356] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]]
01000000 00000020 00000384 0000b350
[15871.326371] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]]
01000000 00000020 0000038c 0068b000
[15871.326385] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]]
01000000 00000020 00000390 000467e8
[15871.372669] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]]
01000000 00000020 00000380 0058b000
[15871.372690] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]]
01000000 00000020 00000384 000069c0
[15871.372708] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]]
01000000 00000020 0000038c 0068b000
[15871.372723] nouveau 0000:09:00.0: mpeg: ch 4 [00060530 mplayer[26300]]
01000000 00000020 00000390 00010604

and so on. The first one is harmless (simple bug that causes it to be print=
ed
instead of hidden), but the rest are harmful. The end-result is random junk=
 on
the screen, but that makes perfect sense given the above errors. I have fix=
es
for some things, but not others. Will update when I have fixed my setup.

You are receiving this mail because:
  • You are the QA Contact for the bug.
  • You are the assignee for the bug.
= --14898902751.73D3CdFD.3400-- --===============0962409494== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTm91dmVhdSBt YWlsaW5nIGxpc3QKTm91dmVhdUBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5m cmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9ub3V2ZWF1Cg== --===============0962409494==--