From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104825] [amdgpu] [drm:gfx_v8_0_hw_fini] *ERROR* KCQ disabled failed (scratch(0xC040)=0x00000000) when unbinding
Date: Mon, 02 Apr 2018 20:49:31 +0000 [thread overview]
Message-ID: <bug-104825-502-bBTKCAPkNi@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104825-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1122 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104825
Harry Wentland <harry.wentland@amd.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #18 from Harry Wentland <harry.wentland@amd.com> ---
Thanks for your bug report, and constant testing and feedback. Since the
original issue is fixed in drm-next-4.17-wip I'll mark this resolved. If I'm
jumping the gun here and you still notice problems feel free to reopen.
The suspend/resume issue you mention seems to be something else and might be
best tracked with a new bug report, possibly on kernel.org as I don't see an
indication that this is graphics driver related.
As for back-porting the changes, AFAIK this bug report uncovered quite a few
issues which were all fixed with separate commits. I don't think all of them
have been pulled into 4.16.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2795 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
prev parent reply other threads:[~2018-04-02 20:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 6:57 [Bug 104825] [amdgpu] [drm:gfx_v8_0_hw_fini] *ERROR* KCQ disabled failed (scratch(0xC040)=0x00000000) when unbinding bugzilla-daemon
2018-01-29 15:47 ` bugzilla-daemon
2018-01-30 8:00 ` bugzilla-daemon
2018-01-31 7:21 ` bugzilla-daemon
2018-02-27 0:09 ` bugzilla-daemon
2018-02-27 10:55 ` bugzilla-daemon
2018-02-27 11:48 ` bugzilla-daemon
2018-02-27 14:51 ` bugzilla-daemon
2018-02-27 15:20 ` bugzilla-daemon
2018-02-27 15:30 ` bugzilla-daemon
2018-02-27 16:17 ` bugzilla-daemon
2018-02-27 18:10 ` bugzilla-daemon
2018-02-27 18:12 ` bugzilla-daemon
2018-02-27 19:01 ` bugzilla-daemon
2018-02-27 19:17 ` bugzilla-daemon
2018-03-27 18:02 ` bugzilla-daemon
2018-03-27 20:20 ` bugzilla-daemon
2018-03-29 16:07 ` bugzilla-daemon
2018-03-29 19:55 ` bugzilla-daemon
2018-04-01 9:51 ` bugzilla-daemon
2018-04-02 20:49 ` bugzilla-daemon [this message]
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-104825-502-bBTKCAPkNi@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