dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: DRI mailing list <dri-devel@lists.freedesktop.org>,
	"Wladimir J. van der Laan" <laanwj@gmail.com>,
	The etnaviv authors <etnaviv@lists.freedesktop.org>,
	Sascha Hauer <kernel@pengutronix.de>
Subject: Re: Etnaviv crashes on glmark2
Date: Wed, 23 Aug 2017 14:06:25 +0200	[thread overview]
Message-ID: <1503489985.2303.41.camel@pengutronix.de> (raw)
In-Reply-To: <20170823084644.GA10094@amethyst.visucore.com>

Hi Fabio,

Am Mittwoch, den 23.08.2017, 10:46 +0200 schrieb Wladimir J. van der
Laan:
> > Etnaviv isn't CMA based, so this is certainly not a valid fix. It
> > probably doesn't crash anymore, as it isn't properly freeing the pages
> > backing the GEM object.
> > 
> > I've seen this crash in the early days of etnaviv a few times, but it
> > hasn't happened to me in a long time.
> 
> I don't recognize this either, I haven't seen a kernel memory managment error while
> running glmark2 (or anything w/ etnaviv) for a long time. Strange.

This might also be related to the used xf86-video-armada version. Are
you sure you are using the latest git version?

Regards,
Lucas

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

  reply	other threads:[~2017-08-23 12:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 12:47 Etnaviv crashes on glmark2 Fabio Estevam
2017-08-22 15:59 ` Fabio Estevam
2017-08-23  8:19   ` Lucas Stach
2017-08-23  8:46     ` Wladimir J. van der Laan
2017-08-23 12:06       ` Lucas Stach [this message]
2017-08-23 13:13         ` Fabio Estevam
2017-08-25 13:00           ` Fabio Estevam

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=1503489985.2303.41.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=etnaviv@lists.freedesktop.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=laanwj@gmail.com \
    /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