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 18:44:44 +0000 [thread overview]
Message-ID: <bug-203111-2300-NjFrp3WF2N@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203111-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203111
Thomas (v10lator@myway.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
--- Comment #3 from Thomas (v10lator@myway.de) ---
(In reply to Alex Deucher from comment #1)
> I'd suggest trying a new version of mesa
I was too fast with closing this: It crashes with newer mesa, too, just
(subjective) less frequent.
Here's a log from mesa 19.0.1:
> [178793.032358] [drm:amdgpu_job_timedout] *ERROR* ring gfx timeout, signaled
> seq=12332054, emitted seq=12332056
> [178793.032362] [drm:amdgpu_job_timedout] *ERROR* Process information:
> process Dirt4 pid 31348 thread WebViewRenderer pid 31422
> [178793.032365] amdgpu 0000:01:00.0: GPU reset begin!
> [178803.262008] [drm:amdgpu_dm_atomic_check] *ERROR* [CRTC:47:crtc-0] hw_done
> or flip_done timed out
And from git (26e161b1e9):
> [ 7819.095648] [drm:amdgpu_job_timedout] *ERROR* ring gfx timeout, signaled
> seq=2652771, emitted seq=2652773
> [ 7819.095652] [drm:amdgpu_job_timedout] *ERROR* Process information: process
> Dirt4 pid 3075 thread WebViewRenderer pid 3152
> [ 7819.095655] amdgpu 0000:01:00.0: GPU reset begin!
> [ 7829.315220] [drm:amdgpu_dm_atomic_check] *ERROR* [CRTC:47:crtc-0] hw_done
> or flip_done timed out
Not sure if the log is shorter cause of new mesa or new kernel (updated from
5.0.4 to 5.0.5).
Are you sure this could be a mesa bug? Just asking cause for me a hanging
kernel sounds like a kernel bug.
--
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 18:44 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 [this message]
2019-04-05 20:31 ` bugzilla-daemon
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-NjFrp3WF2N@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).