From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105911] DVI-D monitor connected to DVI-I output not detected (regression from kernel 4.14.32 to kernel 4.16.0 using graphic core)
Date: Fri, 06 Apr 2018 14:12:05 +0000 [thread overview]
Message-ID: <bug-105911-502-fBkM22gvfH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105911-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 379 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105911
--- Comment #9 from Harry Wentland <harry.wentland@amd.com> ---
Can you capture the 4.16 dmesg with DC again with the amdgpu.dc_log=1 module
option?
Do you see any activity on dmesg with dc_log=1 when you hotplug the
non-detected display?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1311 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:[~2018-04-06 14:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-105911-502@http.bugs.freedesktop.org/>
2018-04-06 8:09 ` [Bug 105911] DVI-D monitor connected to DVI-I output not detected (regression from kernel 4.14.32 to kernel 4.16.0 using graphic core) bugzilla-daemon
2018-04-06 8:15 ` bugzilla-daemon
2018-04-06 8:34 ` bugzilla-daemon
2018-04-06 8:51 ` bugzilla-daemon
2018-04-06 14:12 ` bugzilla-daemon [this message]
2018-04-07 16:49 ` bugzilla-daemon
2018-04-30 14:22 ` bugzilla-daemon
2018-09-27 21:45 ` bugzilla-daemon
2018-10-04 23:09 ` bugzilla-daemon
2019-11-19 8:35 ` 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-105911-502-fBkM22gvfH@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 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.