From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 198713] AMD DC crashes when computing clocks/detecting freesync
Date: Wed, 07 Feb 2018 17:12:46 +0000 [thread overview]
Message-ID: <bug-198713-2300-PWFjBgmi4Y@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198713-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=198713
--- Comment #3 from Jon (jon@moozaad.co.uk) ---
(In reply to Mike Lothian from comment #2)
> As a workaround try amdgpu.dc=0
Well spotted. Workaround has stopped the traces as you'd expect. It's also
stopped the weird blue flicker I was getting in KDE with OGL3 compositor
(different DC bug).
I hope the above is useful for getting PRE_VEGA out of experimental!
Missing from original report, it's 3x BenQ XL2730Z, all display port.
--
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 prev parent reply other threads:[~2018-02-07 17:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 15:59 [Bug 198713] New: AMD DC crashes when computing clocks/detecting freesync bugzilla-daemon
2018-02-07 16:00 ` [Bug 198713] " bugzilla-daemon
2018-02-07 16:17 ` bugzilla-daemon
2018-02-07 17:12 ` bugzilla-daemon [this message]
2018-06-11 8:28 ` bugzilla-daemon
2018-06-12 20:45 ` bugzilla-daemon
2018-06-13 2:28 ` bugzilla-daemon
2018-06-13 13:42 ` bugzilla-daemon
2018-06-13 13:53 ` bugzilla-daemon
2018-06-13 13:53 ` 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-198713-2300-PWFjBgmi4Y@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.