All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 202533] DVI Monitors blank in 4.20-6 kernel
Date: Sat, 09 Feb 2019 06:02:44 +0000	[thread overview]
Message-ID: <bug-202533-2300-eTjBRac0nV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202533-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=202533

Ilia Mirkin (imirkin@alum.mit.edu) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |imirkin@alum.mit.edu

--- Comment #1 from Ilia Mirkin (imirkin@alum.mit.edu) ---
There weren't a ton of changes to nouveau between 4.19 and 4.20. Can you do a
bisect?

There were some changes to add support for HDMI 2.0, but only on GM20x GPUs
(you have a GK10x GPU, which is earlier). And a handful of fixes to MST-related
object lifetime management. It's likely that you have a MST dock, but those
changes don't seem like they would cause anything that drastic.

Please include dmesg and xorg logs.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-02-09  6:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-09  4:48 [Bug 202533] New: DVI Monitors blank in 4.20-6 kernel bugzilla-daemon
2019-02-09  6:02 ` bugzilla-daemon [this message]
2019-02-09 16:36 ` [Bug 202533] " bugzilla-daemon
2019-02-09 16:37 ` bugzilla-daemon
2019-02-09 16:39 ` bugzilla-daemon
2019-02-09 20:57 ` bugzilla-daemon
2019-02-10  2:41 ` bugzilla-daemon
2019-02-10  2:47 ` bugzilla-daemon
2019-02-18 21:17 ` 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-202533-2300-eTjBRac0nV@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.