From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91202] Output to DVI-I (or DVI-D) is blank on Tonga (R9 285 and 380X) with multiple monitors
Date: Mon, 26 Sep 2016 11:08:01 +0000 [thread overview]
Message-ID: <bug-91202-502-Z958NK2iH2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91202-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1329 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91202
--- Comment #23 from Thomas R. <freedesktop-bugs@digital-trauma.de> ---
Guido, does that mean that now it works for you, or simply that you can't say
one way or the other because you didn't test with DAL actually running?
I'm asking because I finally got around to compile amd-staging-4.7 (which only
works with a certain set of kernel options, BTW), and with DAL enabled and both
the last commit and f67b5d74 you mentioned, I still see this bug. So now I'm
confused - am I doing something wrong, or was the fix a victim of the numerous
DAL cleanups along the way, or maybe the freesync changes? I got "[drm] DAL is
enabled" in my kernel log at any rate, and freesync.c dumps stack traces in
warn_slowpath_null, which I guess is just a development help and nothing
serious.
If I'd find a branch with both a working and non-working revision in it I'd be
willing to bisect, but going back in staging-4.7 removes DAL completely, and
staging-4.6 doesn't even compile for me, which was when I gave up yesterday.
It's a shame because apart from this, 4.7 works really, really well. So if
there is anything I can do to properly triangulate this problem, I'd be very
eager to help.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2205 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-09-26 11:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 1:22 [Bug 91202] output to DVI-I is blank bugzilla-daemon
2015-07-03 1:23 ` bugzilla-daemon
2015-07-04 17:51 ` bugzilla-daemon
2015-07-25 18:47 ` bugzilla-daemon
2015-07-25 18:49 ` bugzilla-daemon
2015-07-25 18:50 ` bugzilla-daemon
2015-08-18 15:44 ` bugzilla-daemon
2015-11-07 18:01 ` bugzilla-daemon
2016-01-05 21:26 ` [Bug 91202] Output to DVI-I (or DVI-D) is blank on Tonga (R9 285 and 380X) with multiple monitors bugzilla-daemon
2016-01-06 11:26 ` bugzilla-daemon
2016-01-07 10:49 ` bugzilla-daemon
2016-01-07 12:12 ` bugzilla-daemon
2016-04-22 10:09 ` bugzilla-daemon
2016-04-22 10:18 ` bugzilla-daemon
2016-04-22 10:19 ` bugzilla-daemon
2016-05-09 17:36 ` bugzilla-daemon
2016-05-23 21:45 ` bugzilla-daemon
2016-06-03 14:42 ` bugzilla-daemon
2016-08-28 15:22 ` bugzilla-daemon
2016-08-28 18:14 ` bugzilla-daemon
2016-08-28 20:56 ` bugzilla-daemon
2016-08-28 21:52 ` bugzilla-daemon
2016-09-17 18:44 ` bugzilla-daemon
2016-09-26 11:08 ` bugzilla-daemon [this message]
2016-09-27 17:31 ` bugzilla-daemon
2016-11-14 23:03 ` bugzilla-daemon
2017-02-20 3:28 ` bugzilla-daemon
2017-02-21 11:25 ` bugzilla-daemon
2019-11-09 7:37 ` bugzilla-daemon
2019-11-19 8:06 ` 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-91202-502-Z958NK2iH2@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).