From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104275] Stoney Ridge laptop display goes blank after HDMI gets plugged/unplugged in extended mode.
Date: Fri, 15 Dec 2017 03:51:43 +0000 [thread overview]
Message-ID: <bug-104275-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1322 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104275
Bug ID: 104275
Summary: Stoney Ridge laptop display goes blank after HDMI gets
plugged/unplugged in extended mode.
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: kai.heng.feng@canonical.com
Hi,
We are enabling a new Stoney Ridge laptop.
The issue can be reproduced on branch drm-next-4.16-wip and
amd-staging-drm-next.
Reproduce steps:
1. Plug HDMI monitor.
2. Change to extended mode.
3. Unplug the HDMI monitor
4. Plug the HDMI monitor
Internal display may go blank in step 3.
The internal display may also go blank in step 4. The external one shows
desktop correctly though.
I can see lots of message flooding once I plugged HDMI:
[ 120.933668] amdgpu 0000:00:01.0: 0000000030e07f1f pin failed
[ 120.933859] [drm:amdgpu_crtc_page_flip_target [amdgpu]] *ERROR* failed to
pin new abo buffer before flip
These messages stop as soon as the HDMI is unplugged.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2639 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:[~2017-12-15 3:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 3:51 bugzilla-daemon [this message]
2017-12-15 3:52 ` [Bug 104275] Stoney Ridge laptop display goes blank after HDMI gets plugged/unplugged in extended mode bugzilla-daemon
2017-12-15 3:52 ` bugzilla-daemon
2017-12-15 9:25 ` bugzilla-daemon
2017-12-15 9:57 ` bugzilla-daemon
2017-12-15 9:59 ` bugzilla-daemon
2017-12-15 10:30 ` bugzilla-daemon
2017-12-20 5:56 ` bugzilla-daemon
2017-12-20 9:58 ` bugzilla-daemon
2017-12-20 14:31 ` bugzilla-daemon
2017-12-25 6:38 ` bugzilla-daemon
2017-12-25 8:35 ` bugzilla-daemon
2018-01-02 9:53 ` bugzilla-daemon
2018-01-02 16:07 ` bugzilla-daemon
2018-12-20 7:18 ` 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-104275-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.