dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: kernel@pengutronix.de, etnaviv@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org, patchwork-lst@pengutronix.de
Subject: Re: [BUG 4.17] etnaviv-gpu f1840000.gpu: recover hung GPU!
Date: Tue, 26 Jun 2018 17:48:05 +0200	[thread overview]
Message-ID: <1530028085.9910.47.camel@pengutronix.de> (raw)
In-Reply-To: <20180626153653.GA18587@n2100.armlinux.org.uk>

Hi Russell,

Am Dienstag, den 26.06.2018, 16:36 +0100 schrieb Russell King - ARM
Linux:
> On Tue, Jun 26, 2018 at 09:17:26AM +0100, Russell King - ARM Linux
> wrote:
> > On Tue, Jun 19, 2018 at 02:28:46PM +0200, Lucas Stach wrote:
> > > Agreed. I'll look into bringing back the process detection for
> > > 4.17
> > > stable.
> > > 
> > > I'm still curious why the GC600 on the Dove is that slow. With
> > > performance like this moving a big(ish) window on the screen must
> > > be a
> > > horrible user experience.
> > 
> > This doesn't seem to be the cause - it seems that there's something
> > going on with 4.17 that really is causing the Dove GC600 to get
> > stuck.
> > Reverting all the drivers/gpu/drm/etnaviv changes back to the 4.16
> > state while keeping everything else the same results in no hangs,
> > whereas increasing the timeout with 4.17 still results in hangs.
> > 
> > I'll try to find some time to bisect.
> 
> Sorry, it seems that my attempts to change what was running on the
> system were ineffective (due to the etnaviv module loaded from the
> initramfs, not from the fs copy I was updating.)  Extending the
> timeout to 5 seconds does indeed stop the issue.

Thanks for confirming that the issue is caused by the removed progress
check.

> More importantly, it stops some memory corruption I've observed as
> well, caused by etnaviv freeing buffers when it thinks the GPU has
> timed out while the GPU is still writing to them.

Urgh, that is really bad. I'll get a fix out of the door tomorrow.

Regards,
Lucas
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-06-26 15:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19  9:43 [BUG 4.17] etnaviv-gpu f1840000.gpu: recover hung GPU! Russell King - ARM Linux
2018-06-19 10:09 ` Lucas Stach
2018-06-19 11:00   ` Russell King - ARM Linux
2018-06-19 11:11     ` Lucas Stach
2018-06-19 11:42       ` Russell King - ARM Linux
2018-06-19 12:28         ` Lucas Stach
2018-06-19 15:56           ` Russell King - ARM Linux
2018-06-26  8:17           ` Russell King - ARM Linux
2018-06-26 15:36             ` Russell King - ARM Linux
2018-06-26 15:48               ` Lucas Stach [this message]
2018-06-27 14:38                 ` Lucas Stach
2018-07-11 20:13           ` Russell King - ARM Linux

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=1530028085.9910.47.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=etnaviv@lists.freedesktop.org \
    --cc=kernel@pengutronix.de \
    --cc=linux@armlinux.org.uk \
    --cc=patchwork-lst@pengutronix.de \
    /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