dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109384] Bad DisplayPort enumeration and wrong refresh rate with Hawaii chip
Date: Fri, 18 Jan 2019 18:38:16 +0000	[thread overview]
Message-ID: <bug-109384-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 109384
           Summary: Bad DisplayPort enumeration and wrong refresh rate
                    with Hawaii chip
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: fabio0x@keemail.me

Created attachment 143150
  --> https://bugs.freedesktop.org/attachment.cgi?id=143150&action=edit
Xorg.0 log with DC off

I'm running Solus KDE with kernel 4.20.2 but I've had these issues since kernel
4.19. Here's the list of issues with AMDGPU DC enabled:
- With Solus' default kernel flags I have wrong DisplayPort enumeration,
meaning that I get DisplayPort-1 when I turn on the computer, and then
DisplayPort-2 when I get my monitor to sleep and then I wake it up.
- If I put my computer on sleep (suspension) and then wake it up, I cannot set
a usable refresh rate. This means I actually get 40 Hz when I set 60, and 45 Hz
when I set 74 (yeah, I have a bit of screen "overclocking". That's how I found
DisplayPort enumeration is wrong).
- I get microstuttering, particularly noticeable when I drag windows around.

Now, all these issues are non existant if I set the amdgpu.dc=0 kernel flag.
Also, DisplayPort number is DisplayPort-0 under any circumstances.

❯ inxi -G
Graphics:  Device-1: AMD Hawaii PRO [Radeon R9 290/390] driver: amdgpu v:
kernel 
           Display: x11 server: X.Org 1.20.3 driver: amdgpu,ati unloaded:
fbdev,modesetting,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: 
           renderer: AMD Radeon R9 200 Series (HAWAII DRM 3.27.0
4.20.2-107.current LLVM 7.0.0) 
           v: 4.5 Mesa 18.3.1

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

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

             reply	other threads:[~2019-01-18 18:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 18:38 bugzilla-daemon [this message]
2019-01-18 18:38 ` [Bug 109384] Bad DisplayPort enumeration and wrong refresh rate with Hawaii chip bugzilla-daemon
2019-01-18 18:39 ` bugzilla-daemon
2019-01-18 18:40 ` bugzilla-daemon
2019-01-18 18:41 ` bugzilla-daemon
2019-01-18 18:42 ` bugzilla-daemon
2019-01-18 19:44 ` bugzilla-daemon
2019-01-21 11:44 ` bugzilla-daemon
2019-11-19  9:11 ` 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-109384-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox