From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104736] Kernel panic with agd5's drm-next-4.17-wip & GFX8/Polaris10/Ellesmere/Rx-480-8GiB
Date: Wed, 24 Jan 2018 02:52:01 +0000 [thread overview]
Message-ID: <bug-104736-502-TTWY6d1wgD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104736-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 734 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104736
--- Comment #3 from Robin Kauffman <robink@creosotehill.org> ---
(In reply to Alex Deucher from comment #2)
> does manually loading gpu_sched before amdgpu fix the issue?
Can try to do so, but unsure as to how given that pretty much the entire
graphics stack is compiled into the kernel image.
Reverting commit 4983e48c8539282be15f660bdd2c4260467b1190 ('drm/sched: move
fence slab handling to module init/exit') fixes the issue, and thus this bug
may be a duplicate of bug #104756. If so, this bug can be closed as a
duplicate, or I can experiment with trying to force gpu_sched up first.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1869 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-01-24 2:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 18:40 [Bug 104736] Kernel panic with agd5's drm-next-4.17-wip & GFX8/Polaris10/Ellesmere/Rx-480-8GiB bugzilla-daemon
2018-01-22 18:45 ` bugzilla-daemon
2018-01-23 22:19 ` bugzilla-daemon
2018-01-24 2:52 ` bugzilla-daemon [this message]
2018-01-24 8:41 ` bugzilla-daemon
2018-01-24 10:07 ` bugzilla-daemon
2018-01-24 10:47 ` bugzilla-daemon
2018-01-24 10:53 ` bugzilla-daemon
2018-01-24 12:35 ` bugzilla-daemon
2018-01-25 14:50 ` 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-104736-502-TTWY6d1wgD@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