From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103949] REG_WAIT timeout - dce110_stream_encoder_dp_blank line:930 - 4.15-rc1
Date: Sat, 22 Sep 2018 16:47:43 +0000 [thread overview]
Message-ID: <bug-103949-502-WGe2ZGb6cx@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103949-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 787 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103949
Barry G <barry@grussling.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |barry@grussling.com
--- Comment #2 from Barry G <barry@grussling.com> ---
Created attachment 141688
--> https://bugs.freedesktop.org/attachment.cgi?id=141688&action=edit
dmesg from 4.19-rc4
I still get a lot of entries like:
[ 824.605349] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us *
3000 tries - dce110_stream_encoder_dp_blank line:922
with 4.19-rc4. Are these concerning? Dmesg attached.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2296 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
next prev parent reply other threads:[~2018-09-22 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 3:54 [Bug 103949] REG_WAIT timeout - dce110_stream_encoder_dp_blank line:930 - 4.15-rc1 bugzilla-daemon
2017-11-28 3:57 ` bugzilla-daemon
2018-09-22 16:47 ` bugzilla-daemon [this message]
2018-12-14 18:24 ` bugzilla-daemon
2018-12-17 16:52 ` bugzilla-daemon
2019-01-28 14:56 ` bugzilla-daemon
2019-11-19 8:26 ` 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-103949-502-WGe2ZGb6cx@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;
as well as URLs for NNTP newsgroup(s).