From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 196635] amdgpu clinfo hangs with SI
Date: Tue, 22 Aug 2017 11:33:29 +0000 [thread overview]
Message-ID: <bug-196635-2300-5aq8OcjODx@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196635-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=196635
Janpieter Sollie (janpieter.sollie@dommel.be) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |PATCH_ALREADY_AVAILABLE
--- Comment #11 from Janpieter Sollie (janpieter.sollie@dommel.be) ---
the problem SEEMS to be with CIK support and upgrade to rc6 ...
disabling CIK support in my kernel and upgrading it to rc6 solved the problem.
Probably CIK and SI are not really cooperating properly yet.
--
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:[~2017-08-22 11:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 15:13 [Bug 196635] New: amdgpu clinfo hangs with SI bugzilla-daemon
2017-08-10 15:14 ` [Bug 196635] " bugzilla-daemon
2017-08-10 16:33 ` bugzilla-daemon
2017-08-11 3:31 ` bugzilla-daemon
2017-08-11 3:33 ` bugzilla-daemon
2017-08-11 3:35 ` bugzilla-daemon
2017-08-11 3:37 ` bugzilla-daemon
2017-08-14 10:07 ` bugzilla-daemon
2017-08-15 6:14 ` bugzilla-daemon
2017-08-15 6:25 ` bugzilla-daemon
2017-08-16 5:34 ` bugzilla-daemon
2017-08-16 6:17 ` bugzilla-daemon
2017-08-22 11:33 ` bugzilla-daemon [this message]
2017-08-23 1:20 ` bugzilla-daemon
2017-08-25 3:57 ` 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-196635-2300-5aq8OcjODx@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