From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98645] X Freeze while rendering video with multiple displays and TearFree enabled
Date: Tue, 15 Nov 2016 18:52:50 +0000 [thread overview]
Message-ID: <bug-98645-502-HiXdUWeEgC@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98645-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 745 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98645
--- Comment #8 from Josep Torra <n770galaxy@gmail.com> ---
It's most often reproduced in the Dell T5600 systems with "Intel Corporation
C600/X79 series chipset" and FirePro W9000.
But we also reproduced it few other systems based on chipset "Intel Corporation
C610/X99 series chipset" and FirePro W600.
Not reproducible so far with an Intel Skylake system, Asus Z170 Pro gaming
motherboard, with FirePro W600.
In the Dell T5600 the issue becomes hidden with the drm debug enabled in the
following way.
echo 0xf > /sys/module/drm/parameters/debug
It's still triggered with 0xe instead of 0xf.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1599 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-11-15 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-98645-502@http.bugs.freedesktop.org/>
2016-11-15 9:54 ` [Bug 98645] X Freeze while rendering video with multiple displays and TearFree enabled bugzilla-daemon
2016-11-15 14:23 ` bugzilla-daemon
2016-11-15 18:52 ` bugzilla-daemon [this message]
2019-11-19 9:19 ` bugzilla-daemon
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-98645-502-HiXdUWeEgC@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).