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 99584] XVMC on nv43 class card broken with recent mesa + kernel.
Date: Sun, 26 Mar 2017 03:43:01 +0000	[thread overview]
Message-ID: <bug-99584-8800-9x2XTjx3Nu@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99584-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #5 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
OK, so the NV4A actually runs into a different issue - the MPEG class can only
take linear memory, but the PCI GART is paged. So it can't deal the CMD/DATA
bo's. When moving those to VRAM (in mesa), the NV4A is fine. I plugged a NV42
in with much worse results. On boot I get:

https://hastebin.com/datuzivebu.sql

[   10.110345] nouveau 0000:04:00.0: mpeg: ch -1 [unknown] 03100023 ffffffff
00000001 ffffffff
[   10.191580] nouveau 0000:04:00.0: mpeg: MSRCH 0xffffffff

And just all kinds of fail. This is with some local patches to print the extra
stuff out. Feels like it's not getting powered on (all those 0xffffffff's) in
MC.

-- 
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: 1741 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2017-03-26  3:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-29  7:27 [Bug 99584] New: XVMC on nv43 class card broken with recent mesa + kernel bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-99584-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-01-29  7:29   ` [Bug 99584] " 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 [this message]
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-9x2XTjx3Nu@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.