From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110701] GPU faults in in Unigine Valley 1.0
Date: Fri, 24 May 2019 00:08:15 +0000 [thread overview]
Message-ID: <bug-110701-502-JAQ17cMdQ6@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110701-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 848 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110701
--- Comment #26 from Yury Zhuravlev <stalkerg@gmail.com> ---
(In reply to Christoph Haag from comment #25)
> (In reply to Yury Zhuravlev from comment #24)
> > (In reply to Marek Olšák from comment #23)
> > > Fixed by d6053bf2a170a0fec6d232fda097d2f35f0e9eae. Closing.
> >
> > The original issue was about Vega and on Vega we saw a different problem. I
> > suppose before close issue somebody should check patch on Vega.
> > I will do it soon.
>
> Since nobody responded: On a Vega 64 I got GPU faults like the ones posted
> here followed by a GPU hang immediately when restoring a firefox (nightly)
> session. With mesa master this does not happen anymore.
I agree, everything fine now. Vega56
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1862 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-05-24 0:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 11:58 [Bug 110701] GPU faults in in Unigine Valley 1.0 bugzilla-daemon
2019-05-18 0:22 ` bugzilla-daemon
2019-05-18 0:37 ` bugzilla-daemon
2019-05-18 1:48 ` bugzilla-daemon
2019-05-18 3:33 ` bugzilla-daemon
2019-05-18 3:53 ` bugzilla-daemon
2019-05-18 11:43 ` bugzilla-daemon
2019-05-19 4:15 ` bugzilla-daemon
2019-05-19 9:50 ` bugzilla-daemon
2019-05-19 10:19 ` bugzilla-daemon
2019-05-19 15:52 ` bugzilla-daemon
2019-05-19 17:48 ` bugzilla-daemon
2019-05-19 23:19 ` bugzilla-daemon
2019-05-19 23:30 ` bugzilla-daemon
2019-05-20 0:24 ` bugzilla-daemon
2019-05-20 0:27 ` bugzilla-daemon
2019-05-20 3:20 ` bugzilla-daemon
2019-05-20 3:38 ` bugzilla-daemon
2019-05-20 3:46 ` bugzilla-daemon
2019-05-20 13:48 ` bugzilla-daemon
2019-05-21 7:08 ` bugzilla-daemon
2019-05-21 9:44 ` bugzilla-daemon
2019-05-21 18:36 ` bugzilla-daemon
2019-05-21 21:38 ` bugzilla-daemon
2019-05-21 23:19 ` bugzilla-daemon
2019-05-22 0:19 ` bugzilla-daemon
2019-05-23 20:01 ` bugzilla-daemon
2019-05-24 0:08 ` bugzilla-daemon [this message]
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-110701-502-JAQ17cMdQ6@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