From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104437] RX480 + SME = amdgpu init failed + null dereference
Date: Mon, 01 Jan 2018 16:20:53 +0000 [thread overview]
Message-ID: <bug-104437-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1290 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104437
Bug ID: 104437
Summary: RX480 + SME = amdgpu init failed + null dereference
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: ace@sannes.org
Created attachment 136470
--> https://bugs.freedesktop.org/attachment.cgi?id=136470&action=edit
dmesg when not working
When upgrading from linux 4.13.x -> 4.14.x the amdgpu failed to come up, often
hanging my desktop computer.
Ending the amdgpg bring up with:
[drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 0 test failed
(scratch(0xC040)=0xCAFEDEAD)
[drm:amdgpu_device_init [amdgpu]] *ERROR* hw_init of IP block <gfx_v8_0> failed
-22
amdgpu 0000:0a:00.0: amdgpu_init failed
After getting some help in #radeon we figured out that the culprit was that I
had enabled SME (which the CPU Ryzen X1800 support).
Got the same error on 4.15-rc6, but with additional null dereference in DC
code.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2734 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 reply other threads:[~2018-01-01 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 16:20 bugzilla-daemon [this message]
2019-06-15 16:21 ` [Bug 104437] RX480 + SME = amdgpu init failed + null dereference bugzilla-daemon
2019-06-17 9:09 ` bugzilla-daemon
2019-06-17 22:22 ` bugzilla-daemon
2019-11-19 8:28 ` 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-104437-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.