From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107261] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 1us * 10 tries - optc1_lock line:628
Date: Mon, 04 Feb 2019 05:15:12 +0000 [thread overview]
Message-ID: <bug-107261-502-T08wjxQLec@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107261-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 323 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107261
--- Comment #14 from raxondmc@gmail.com ---
hey,
give the following patches a try :
8c9d90eebd23b6d40ddf4ce5df5ca2b932336a06 , it helped me (MST but works for SST)
- Raxondmc
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1173 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:[~2019-02-04 5:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 11:30 [Bug 107261] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 1us * 10 tries - optc1_lock line:628 bugzilla-daemon
2018-07-18 15:51 ` bugzilla-daemon
2018-08-19 20:35 ` bugzilla-daemon
2018-08-21 2:12 ` bugzilla-daemon
2018-09-03 17:58 ` bugzilla-daemon
2018-09-16 5:41 ` bugzilla-daemon
2018-09-16 20:20 ` bugzilla-daemon
2018-09-29 21:02 ` bugzilla-daemon
2018-10-15 17:21 ` bugzilla-daemon
2018-10-28 20:21 ` bugzilla-daemon
2018-11-08 4:10 ` bugzilla-daemon
2018-11-08 4:13 ` bugzilla-daemon
2019-01-01 19:43 ` bugzilla-daemon
2019-01-19 10:40 ` bugzilla-daemon
2019-02-04 5:15 ` bugzilla-daemon [this message]
2019-02-04 5:15 ` bugzilla-daemon
2019-02-08 3:40 ` bugzilla-daemon
2019-11-19 8:43 ` 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-107261-502-T08wjxQLec@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).