From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 200645] 4.18-rc regression bisected to e03fd3f30: amdgpu polaris11/rx460 only activates on one output/monitor of two
Date: Wed, 25 Jul 2018 07:16:11 +0000 [thread overview]
Message-ID: <bug-200645-2300-KnnzfxADnv@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200645-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200645
Duncan (1i5t5.duncan@cox.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
Regression|No |Yes
--- Comment #3 from Duncan (1i5t5.duncan@cox.net) ---
Confirmed it's this commit. Reverting it on top of...
$ uname -r
4.18.0-rc6-00093-g9981b4fb8-dirty
... gets me a fully working multi-monitor setup once again.
(The "dirty" is that patch, along with one that sets noatime as a mount default
so I don't have to add it everywhere.)
--
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
next prev parent reply other threads:[~2018-07-25 7:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 6:00 [Bug 200645] New: 4.18-rc regression bisected to e03fd3f30: amdgpu polaris11/rx460 only activates on one output/monitor of two bugzilla-daemon
2018-07-25 6:06 ` [Bug 200645] " bugzilla-daemon
2018-07-25 6:10 ` bugzilla-daemon
2018-07-25 7:16 ` bugzilla-daemon [this message]
2018-07-25 14:02 ` bugzilla-daemon
2018-07-30 9:10 ` bugzilla-daemon
2018-08-07 23:50 ` bugzilla-daemon
2018-08-11 8:58 ` bugzilla-daemon
2018-09-01 5:21 ` bugzilla-daemon
2018-11-04 16:44 ` bugzilla-daemon
2018-11-05 12:18 ` bugzilla-daemon
2018-11-06 10:53 ` bugzilla-daemon
2018-11-06 11:09 ` bugzilla-daemon
2018-11-06 17:40 ` bugzilla-daemon
2018-11-25 6:29 ` 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-200645-2300-KnnzfxADnv@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.