From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 76173] New: xbmc green screen with vdpau enabled
Date: Fri, 14 Mar 2014 13:54:15 +0000 [thread overview]
Message-ID: <bug-76173-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1286 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=76173
Priority: medium
Bug ID: 76173
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: xbmc green screen with vdpau enabled
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: serafean-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: 10.1
Component: Drivers/DRI/nouveau
Product: Mesa
When using xbmc with vdpau acceleration enabled, I get a green screen (audio
works), and this appears in the kernel log :
nouveau E[ PFIFO][0000:03:00.0] DMA_PUSHER - ch 6 [xbmc.bin[22420]] get
0x00200f06c8 put 0x00200f0770 ib_get 0x000000db ib_put 0x000000dc state
0x80000000 (err: INVALID_CMD) push 0x00400040
Sometimes it makes xbmc crash completely.
This is on an nv50 (Chipset: MCP79/MCP7A (NVAC) ) : VGA compatible controller:
NVIDIA Corporation ION VGA (rev b1)
Mesa 10.1
libdrm 2.4.52
It works all right using mplayer.
Just a wild guess : something to do with GL_NV_vdpau_interop?
If you need any more information, I'd be happy to provide it.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2520 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2014-03-14 13:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 13:54 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-76173-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-03-14 13:55 ` [Bug 76173] xbmc green screen with vdpau enabled bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-14 13:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-14 14:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-14 15:39 ` [Bug 76173] [NVAC] xbmc failure " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-14 17:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-10 9:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:39 ` 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-76173-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.