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 95282] G96: system hang on video playback via vdpau
Date: Tue, 06 Sep 2016 15:25:00 +0000	[thread overview]
Message-ID: <bug-95282-8800-N4NRZCRCIy@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95282-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #17 from Elmar Stellnberger <estellnb-7Km2I/eHSAQdnm+yROfE0A@public.gmane.org> ---
Created attachment 126248
  --> https://bugs.freedesktop.org/attachment.cgi?id=126248&action=edit
dmesg while trying to play with vdpau by xine

 There is not much in the logs except:
nouveau 0000:01:00.0: bsp: Watchdog interrupt, engine hung.

 tested with kernel 9ca581b50dab6103183396852cc08e440fcda18e and a freshly
downloaded firmware.

  What may I do in order to get more meaningful debug information? Is vdpau
playback an issue that is being worked upon?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1634 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:[~2016-09-06 15:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-05  9:21 [Bug 95282] New: system hang on video playback via vdpau bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-95282-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-05-05  9:23   ` [Bug 95282] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-05  9:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-05  9:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-05  9:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-06 16:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-06 17:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-09 17:33   ` [Bug 95282] G96: " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-09 17:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-09 17:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-09 17:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-13 19:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-18  9:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-24 15:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-04 14:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-13 11:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-30 10:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-29 16:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-06 15:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2017-01-18 21:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-16 17:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-16 17:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-16 17:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-17 10:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:13   ` 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-95282-8800-N4NRZCRCIy@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.