From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/5] omapdrm: fences and zpos
Date: Thu, 13 Apr 2017 17:37:51 +0300 [thread overview]
Message-ID: <1678407.pgk3JzOetd@avalon> (raw)
In-Reply-To: <24a5d93c-478d-5fd2-c061-9a33952fcc68@ti.com>
Hi Tomi,
On Wednesday 05 Apr 2017 09:52:36 Tomi Valkeinen wrote:
> On 03/01/17 14:06, Tomi Valkeinen wrote:
> > I got this with your series. AM5 EVM, dual display, I run "kmstest --flip"
> > and then exit by pressing enter, which is when I see the warning. It
> > happens only sometimes, but having lots of cpu load (I used "stress -c
> > 4") makes the driver spam the warning.
> >
> > [ 67.207223] ------------[ cut here ]------------
> > [ 67.211937] WARNING: CPU: 1 PID: 324 at
> > drivers/gpu/drm/omapdrm/omap_gem.c:1085 omap_gem_free_object+0x270/0x2d4
> > [omapdrm] [ 67.223138] Modules linked in: omapdrm drm_kms_helper drm
> > panel_dsi_cm panel_dpi connector_analog_tv connector_dvi connector_hdmi
> > encoder_tp d12s015 encoder_tfp410 omapdss cfbfillrect cfbimgblt
> > cfbcopyarea [last unloaded: omapdss] [ 67.243953] CPU: 1 PID: 324 Comm:
> > kmstest Not tainted 4.9.0-rc8-00163-g55f4a6c2d775 #135
>
> After rebasing to latest drm-next, I no longer see this, but the kms++
> test script hangs when exiting it. And then I get BUGs from the kernel.
> Do you know if all the dependencies are in drm-next?
I've just rebased the patches on top of drm-next and I can't reproduce any of
these two issues. I've ran kmstest --flip for 250 frames in a loop for half an
hour, with and without CPU load (with 'stress -c 4') and everything works
fine. I'll repost the rebased patches now.
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-04-13 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 23:29 [PATCH 0/5] omapdrm: fences and zpos Laurent Pinchart
2017-01-02 23:29 ` [PATCH 1/5] drm: omapdrm: Handle events when enabling/disabling CRTCs Laurent Pinchart
2017-01-03 10:07 ` Tomi Valkeinen
2017-01-03 11:06 ` Laurent Pinchart
2017-01-02 23:29 ` [PATCH 2/5] drm: omapdrm: Use DRM core's atomic commit helper Laurent Pinchart
2017-01-02 23:29 ` [PATCH 3/5] drm: omapdrm: Remove legacy buffer synchronization support Laurent Pinchart
2017-01-02 23:29 ` [PATCH 4/5] drm: omapdrm: Store the Z order in the plane state zpos field Laurent Pinchart
2017-01-02 23:29 ` [PATCH 5/5] drm: omapdrm: Add zpos property Laurent Pinchart
2017-01-03 12:06 ` [PATCH 0/5] omapdrm: fences and zpos Tomi Valkeinen
2017-04-05 6:52 ` Tomi Valkeinen
2017-04-13 14:37 ` Laurent Pinchart [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=1678407.pgk3JzOetd@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=tomi.valkeinen@ti.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