From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109628] WARNING at dcn10_hw_sequencer.c:868 dcn10_verify_allow_pstate_change_high()
Date: Thu, 14 Feb 2019 14:29:33 +0000 [thread overview]
Message-ID: <bug-109628-502-1EvPIKSVEP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109628-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 894 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #4 from Nicholas Kazlauskas <nicholas.kazlauskas@amd.com> ---
There were some patches recently for Raven that fixed some programming sequence
issues during changes for dpms / suspend. I wonder if these would help fix what
you're reporting - the pstate warnings usually indicate that something went
wrong in the programming sequence and the hardware has potentially hung but it
won't always happen consistently.
https://patchwork.freedesktop.org/patch/282418/
I think there was another related to this as well that might be in
amd-staging-drm-next
https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next
If you can still reproduce the issue consistently I'd give this tree a try and
see if you still have the issue.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1890 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-02-14 14:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 9:56 [Bug 109628] WARNING at dcn10_hw_sequencer.c:868 dcn10_verify_allow_pstate_change_high() bugzilla-daemon
2019-02-14 9:58 ` bugzilla-daemon
2019-02-14 9:59 ` bugzilla-daemon
2019-02-14 10:08 ` bugzilla-daemon
2019-02-14 14:29 ` bugzilla-daemon [this message]
2019-03-05 9:49 ` bugzilla-daemon
2019-08-29 21:54 ` bugzilla-daemon
2019-08-30 10:34 ` bugzilla-daemon
2019-08-30 11:46 ` bugzilla-daemon
2019-08-30 15:01 ` bugzilla-daemon
2019-08-30 15:13 ` bugzilla-daemon
2019-08-30 15:43 ` bugzilla-daemon
2019-08-30 17:13 ` bugzilla-daemon
2019-08-30 23:31 ` bugzilla-daemon
2019-09-04 18:07 ` bugzilla-daemon
2019-09-04 18:10 ` bugzilla-daemon
2019-09-10 15:34 ` bugzilla-daemon
2019-09-11 17:25 ` bugzilla-daemon
2019-09-16 14:17 ` bugzilla-daemon
2019-09-16 15:06 ` bugzilla-daemon
2019-09-19 17:49 ` bugzilla-daemon
2019-09-20 15:57 ` bugzilla-daemon
2019-09-22 9:02 ` bugzilla-daemon
2019-09-22 9:05 ` bugzilla-daemon
2019-09-22 20:13 ` bugzilla-daemon
2019-09-26 8:37 ` bugzilla-daemon
2019-10-06 19:38 ` bugzilla-daemon
2019-10-06 20:13 ` bugzilla-daemon
2019-10-07 5:59 ` bugzilla-daemon
2019-10-07 8:16 ` bugzilla-daemon
2019-10-16 17:31 ` bugzilla-daemon
2019-11-04 10:31 ` bugzilla-daemon
2019-11-05 17:42 ` bugzilla-daemon
2019-11-10 5:34 ` bugzilla-daemon
2019-11-10 6:20 ` bugzilla-daemon
2019-11-14 16:27 ` bugzilla-daemon
2019-11-19 9:13 ` 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-109628-502-1EvPIKSVEP@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.