From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 203111] Unrecoverable GPU crash with DiRT 4
Date: Fri, 05 Apr 2019 20:31:41 +0000 [thread overview]
Message-ID: <bug-203111-2300-ADgDqRfaFW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203111-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203111
--- Comment #4 from Alex Deucher (alexdeucher@gmail.com) ---
(In reply to Thomas from comment #3)
>
> Are you sure this could be a mesa bug? Just asking cause for me a hanging
> kernel sounds like a kernel bug.
Likely a mesa bug. Mesa submits gfx/video/compute jobs to the kernel driver.
If there are subtle bugs in those jobs, the GPU can hang. The kernel driver
can reset the GPU, but the display server needs to catch the reset and properly
re-initialize it's context and buffers. At the moment, none of the display
servers do this so you need to restart them after a GPU reset.
The:
[drm:amdgpu_cs_ioctl] *ERROR* Failed to initialize parser -125!
error is because userspace tried to submit more work to the kernel after a
reset without re-initializing it's context, so the kernel rejects it.
--
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:[~2019-04-05 20:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 9:29 [Bug 203111] New: Unrecoverable GPU crash with DiRT 4 bugzilla-daemon
2019-04-01 16:02 ` [Bug 203111] " bugzilla-daemon
2019-04-02 7:38 ` bugzilla-daemon
2019-04-05 18:44 ` bugzilla-daemon
2019-04-05 20:31 ` bugzilla-daemon [this message]
2019-04-05 21:15 ` bugzilla-daemon
2019-04-05 21:15 ` bugzilla-daemon
2019-04-09 1:39 ` 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-203111-2300-ADgDqRfaFW@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;
as well as URLs for NNTP newsgroup(s).