All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105177] amdgpu wrong colors with rx460 connected via hdmi
Date: Sat, 24 Feb 2018 10:57:46 +0000	[thread overview]
Message-ID: <bug-105177-502-jnm5REh254@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105177-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 871 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=105177

--- Comment #14 from Reimar Imhof <tuxuser@quantentunnel.de> ---
I've build a 4.15.5 kernel incl. your patch and booted with display connected
to hdmi.
First boot hang.
In journalctl I found
Feb 24 11:29:28 linux kernel: [drm:drm_atomic_helper_wait_for_flip_done
[drm_kms_helper]] *ERROR* [CRTC:42:crtc-0] flip_done timed out
(I'll attach journalctl-boot-4-15-5-with-patch-hdmi-hang.txt)

Second try booted into gui (kde login). The colors where still wrong. But now
it was possible to turn of the screen and on again. The screen resolution
stayed the same but the colors still were wrong.
(I'll attach dmesg-4-15-5-with-patch-hdmi.txt and
Xorg.0.log-4.15.5-with-patch-hdmi.txt)

I'll stay with the dvi connected monitor.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1660 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

  parent reply	other threads:[~2018-02-24 10:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-20 21:04 [Bug 105177] amdgpu wrong colors with rx460 connected via hdmi bugzilla-daemon
2018-02-20 21:04 ` bugzilla-daemon
2018-02-20 21:05 ` bugzilla-daemon
2018-02-20 21:05 ` bugzilla-daemon
2018-02-20 22:02 ` bugzilla-daemon
2018-02-20 22:02 ` bugzilla-daemon
2018-02-21 21:37 ` bugzilla-daemon
2018-02-21 21:38 ` bugzilla-daemon
2018-02-21 21:39 ` bugzilla-daemon
2018-02-21 21:39 ` bugzilla-daemon
2018-02-21 21:40 ` bugzilla-daemon
2018-02-21 21:42 ` bugzilla-daemon
2018-02-21 22:04 ` bugzilla-daemon
2018-02-22 20:19 ` bugzilla-daemon
2018-02-24 10:57 ` bugzilla-daemon [this message]
2018-02-24 10:58 ` bugzilla-daemon
2018-02-24 10:59 ` bugzilla-daemon
2018-02-24 11:00 ` bugzilla-daemon
2018-03-27 15:36 ` bugzilla-daemon
2018-03-27 16:48 ` bugzilla-daemon
2018-03-29 13:25 ` bugzilla-daemon
2018-03-29 13:34 ` bugzilla-daemon
2018-04-17 18:13 ` bugzilla-daemon
2019-11-19  8: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-105177-502-jnm5REh254@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.