From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 198713] AMD DC crashes when computing clocks/detecting freesync
Date: Tue, 12 Jun 2018 20:45:19 +0000 [thread overview]
Message-ID: <bug-198713-2300-UceawVCxBM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198713-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=198713
Andrey Grodzovsky (andrey.grodzovsky@amd.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |andrey.grodzovsky@amd.com
--- Comment #5 from Andrey Grodzovsky (andrey.grodzovsky@amd.com) ---
It's not a crash but a warning over invalid reg fields access - here
https://elixir.bootlin.com/linux/v4.15.1/source/drivers/gpu/drm/amd/display/dc/dm_services.h#L132
I see you are working with 4.15 kernel, can you take the latest stable from
here - https://www.kernel.org/ and see if problem goes away ?
For quicker response time you can try submitting tickets to Free Desktop
Bugzilla -
https://bugs.freedesktop.org/
Andrey
--
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-06-12 20:45 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
2018-06-11 8:28 ` bugzilla-daemon
2018-06-12 20:45 ` bugzilla-daemon [this message]
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-UceawVCxBM@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox