From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107946] AMDGPU regression, multi-head not working on 4.18, 4.19RC3, but does on 4.16
Date: Sat, 15 Sep 2018 19:19:30 +0000 [thread overview]
Message-ID: <bug-107946-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1017 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107946
Bug ID: 107946
Summary: AMDGPU regression, multi-head not working on 4.18,
4.19RC3, but does on 4.16
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: dave@locochino.com
Created attachment 141576
--> https://bugs.freedesktop.org/attachment.cgi?id=141576&action=edit
dmesg output on a broken system, using kernel 4.19_RC3
Multi-head on AMD Vega is not working on kernel 4.18 or 4.19RC, but works fine
on 4.16
I'm stuck at kernel 4.16 with my hardware, current stable kernels leave me with
just one display working.
Attaching dmesg output from 4.16, 4.18, and 4.19_RC3
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2520 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 reply other threads:[~2018-09-15 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-15 19:19 bugzilla-daemon [this message]
2018-09-15 19:21 ` [Bug 107946] AMDGPU regression, multi-head not working on 4.18, 4.19RC3, but does on 4.16 bugzilla-daemon
2018-09-15 19:22 ` bugzilla-daemon
2018-09-18 13:07 ` bugzilla-daemon
2018-09-24 22:06 ` bugzilla-daemon
2018-09-24 22:07 ` bugzilla-daemon
2018-09-24 22:07 ` bugzilla-daemon
2018-12-04 19:46 ` bugzilla-daemon
2018-12-04 19:49 ` 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-107946-502@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.