From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Christian Gmeiner <christian.gmeiner@gmail.com>
Cc: "Ing. Josua Mayer" <josua.mayer@jm0.eu>,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, Lucas Stach <l.stach@pengutronix.de>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
The etnaviv authors <etnaviv@lists.freedesktop.org>,
DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/etnaviv: fix external abort seen on GC600 rev 0x19
Date: Sun, 23 Aug 2020 20:19:56 +0100 [thread overview]
Message-ID: <20200823191956.GH1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAH9NwWdLnwb0BiR6qAHKFexFm2NJkpHv7Z7YAdQ7fJBVxjGH4w@mail.gmail.com>
On Sun, Aug 23, 2020 at 09:10:25PM +0200, Christian Gmeiner wrote:
> Hi
>
> > I have formally tested the patch with 5.7.10 - and it doesn't resolve
> > the issue - sadly :(
> >
> > From my testing, the reads on
> > VIVS_HI_CHIP_PRODUCT_ID
> > VIVS_HI_CHIP_ECO_ID
> > need to be conditional - while
> > VIVS_HI_CHIP_CUSTOMER_ID
> > seems to be okay.
> >
>
> Uhh.. okay.. just send a V2 - thanks for testing :)
There is also something else going on with the GC600 - 5.4 worked fine,
5.8 doesn't - my 2D Xorg driver gets stuck waiting on a BO after just
a couple of minutes. Looking in debugfs, there's a whole load of BOs
that are listed as "active", yet the GPU is idle:
00020000: A 0 ( 7) 00000000 00000000 8294400
00010000: I 0 ( 1) 00000000 00000000 4096
00010000: I 0 ( 1) 00000000 00000000 4096
00010000: I 0 ( 1) 00000000 00000000 327680
00010000: A 0 ( 7) 00000000 00000000 8388608
00010000: I 0 ( 1) 00000000 00000000 8388608
00010000: I 0 ( 1) 00000000 00000000 8388608
00010000: A 0 ( 7) 00000000 00000000 8388608
00010000: A 0 ( 3) 00000000 00000000 8388608
00010000: A 0 ( 4) 00000000 00000000 8388608
00010000: A 0 ( 3) 00000000 00000000 8388608
00010000: A 0 ( 3) 00000000 00000000 8388608
00010000: A 0 ( 3) 00000000 00000000 8388608
....
00010000: A 0 ( 3) 00000000 00000000 8388608
Total 38 objects, 293842944 bytes
My guess is there's something up with the way a job completes that's
causing the BOs not to be marked inactive. I haven't yet been able
to debug any further.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2020-08-23 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 18:17 Christian Gmeiner
2020-08-23 14:27 ` Ing. Josua Mayer
2020-08-23 19:10 ` Christian Gmeiner
2020-08-23 19:19 ` Russell King - ARM Linux admin [this message]
2020-08-24 11:04 ` Lucas Stach
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=20200823191956.GH1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=airlied@linux.ie \
--cc=christian.gmeiner@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=josua.mayer@jm0.eu \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®