From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 203339] New: AMDGPU: virtual_display disables physical outputs
Date: Tue, 16 Apr 2019 22:51:52 +0000 [thread overview]
Message-ID: <bug-203339-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=203339
Bug ID: 203339
Summary: AMDGPU: virtual_display disables physical outputs
Product: Drivers
Version: 2.5
Kernel Version: 5.0.7
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: parker.l.reed@gmail.com
Regression: No
Created attachment 282351
--> https://bugzilla.kernel.org/attachment.cgi?id=282351&action=edit
Kernel log
Unable to tell if this is intended or if caused by a crash.
I have a monitor connected via HDMI. When I use the virtual_display kernel
parameter, only the virtual displays show up.
amdgpu.virtual_display=0000:07:00.0,2
Original patchset doesn't mention this usecase.
https://lists.freedesktop.org/archives/amd-gfx/2016-August/001058.html
Kernel log attached shows some crashes related to dce_virtual_crtc
--
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 reply other threads:[~2019-04-16 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 22:51 bugzilla-daemon [this message]
2019-04-17 4:05 ` [Bug 203339] AMDGPU: virtual_display disables physical outputs bugzilla-daemon
2020-09-02 15:18 ` bugzilla-daemon
2020-09-02 16:00 ` bugzilla-daemon
2020-10-21 8:57 ` bugzilla-daemon
2020-10-21 12:47 ` 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-203339-2300@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox