All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 176301] New: Fiji DisplayPort drm_crtc_helper_set_config *ERROR* failed to set mode on
Date: Tue, 04 Oct 2016 19:38:48 +0000	[thread overview]
Message-ID: <bug-176301-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 176301
           Summary: Fiji DisplayPort drm_crtc_helper_set_config *ERROR*
                    failed to set mode on
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.7.5-200.fc24.x86_64
          Hardware: All
                OS: Linux
              Tree: Fedora
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: vedran@miletic.net
        Regression: No

I have a Fiji card

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Fiji
[Radeon R9 FURY / NANO Series] (rev ca)

with two LG DisplayPort 27" 4K monitors. If one of the displays is powered off,
but connected, dmesg shows error messages

[drm:drm_crtc_helper_set_config [drm_kms_helper]] *ERROR* failed to set mode on
[CRTC:34:crtc-1]

and GDM/X will refuse to run.

-- 
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:[~2016-10-04 19:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-04 19:38 bugzilla-daemon [this message]
2016-10-04 20:07 ` [Bug 176301] Fiji DisplayPort drm_crtc_helper_set_config *ERROR* failed to set mode on bugzilla-daemon
2016-11-02 16:58 ` bugzilla-daemon
2016-11-02 16:58 ` bugzilla-daemon
2025-05-29 12:57 ` 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-176301-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 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.