From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108625] AMDGPU - Can't even get Xorg to start - Kernel driver hangs with ring buffer timeout on ARM64
Date: Mon, 05 Nov 2018 15:32:20 +0000 [thread overview]
Message-ID: <bug-108625-502-tC3OSpLBM1@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108625-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2105 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108625
--- Comment #12 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Carsten Haitzler from comment #10)
> so wouldn't that make it a necessity then if its even glamor needing it? i
> guess i can turn off glamor accel but realistically gl is a necessity so the
> problem needs to be addressed sooner or later.
>
If you were starting a bare x server, you usually don't hit the glamor paths
too extensively compared to a full desktop environment.
> the ring gfx timeout smells to me of "not a mesa bug" in that an ioctl going
> to the drm driver never returns qhen doing a simple query. it hangs, thus
> something lower down that is having a bad day, if something as simple as
> querying a fence causes a hang... :)
>
> what is this ring gfx thing exactly (seems to be some command queue) and why
> would it be timing out? all the way back at seq 10/11 ... like right at the
> start of its use? it's almost like some interrupt or in memory semaphore
> thing mapped from the card is messing up? i'm looking for something to look
> into more specifically.
Each engine on the GPU (gfx, compute, video decode, encode, dma, etc.) has a
ring buffer used to feed it. The work sent to the engines is managed by a sw
scheduler in the kernel. The kernel driver tests the rings as part of the
driver init sequence. The driver won't come up if the ring tests fail so they
are working at least until you start X. Presumably X submits (via glamor) some
work to the GPU which causes the GPU to hang. The fence never signals because
the GPU never finished processing the job due to the hang.
Another simplier test would be to boot up to a console (no X) and then try
running some of the libdrm amdgpu tests. They are really simple (copying data
and round and verifying it using different engines, allocating freeing memory,
etc.).
https://cgit.freedesktop.org/mesa/drm/tree/tests/amdgpu
See if some of the simple copy or write tests work.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3198 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-11-05 15:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 15:59 [Bug 108625] AMDGPU - Can't even get Xorg to start - Kernel driver hangs with ring buffer timeout on ARM64 bugzilla-daemon
2018-11-01 17:55 ` bugzilla-daemon
2018-11-02 12:14 ` bugzilla-daemon
2018-11-02 12:15 ` bugzilla-daemon
2018-11-02 12:15 ` bugzilla-daemon
2018-11-02 12:16 ` bugzilla-daemon
2018-11-02 18:41 ` bugzilla-daemon
2018-11-02 18:41 ` bugzilla-daemon
2018-11-04 13:17 ` bugzilla-daemon
2018-11-04 16:15 ` bugzilla-daemon
2018-11-05 9:08 ` bugzilla-daemon
2018-11-05 15:20 ` bugzilla-daemon
2018-11-05 15:32 ` bugzilla-daemon [this message]
2018-11-09 20:32 ` bugzilla-daemon
2018-11-09 20:33 ` bugzilla-daemon
2018-11-19 13:00 ` bugzilla-daemon
2018-11-19 13:39 ` bugzilla-daemon
2019-03-21 20:55 ` 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-108625-502-tC3OSpLBM1@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