From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 95282] New: system hang on video playback via vdpau
Date: Thu, 05 May 2016 09:21:24 +0000 [thread overview]
Message-ID: <bug-95282-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1590 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=95282
Bug ID: 95282
Summary: system hang on video playback via vdpau
Product: xorg
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: estellnb-7Km2I/eHSAQdnm+yROfE0A@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Yesterday I have installed the proprietary firmware for nouveau as described
under wiki/VideoAcceleration/#firmware and now my machine hangs reliably on
start of video playback. If vdpau is not used (i.e. by specifying xine -V XShm
xy.mkv) then it does not hang. It first starts to hang, then there is a short
moment where it reacts on pressing num lock and where playback continues and
then it hangs forever.
When switching to vt02 before playback starts you can see several messages;
it also reacts on Alt-PrnScr-l/m/p printing out that it would now print the
memory/registers/backtraces but then does not actually print them unless you
presss Alt-PrnScr-C. There appears to be nothing in the log (switched to vt02
is the last message in the xorg.0.log).
Current Operating System: Linux AmiloXi3650 4.6.0-rc6-ARCH-00006-g7d92f59 #8
SMP PREEMPT Tue May 3 14:17:04 CEST 2016 x86_64
Xorg Build Date: 05 April 2016 05:24:02PM
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2796 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:[~2016-05-05 9:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 9:21 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-95282-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-05-05 9:23 ` [Bug 95282] system hang on video playback via vdpau 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
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@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox