From: robin.murphy@arm.com (Robin Murphy)
To: linux-arm-kernel@lists.infradead.org
Subject: HDLCD crashes with 6d910bfa809e
Date: Tue, 7 Jun 2016 15:11:14 +0100 [thread overview]
Message-ID: <5756D602.4090305@arm.com> (raw)
In-Reply-To: <20160607133535.GA1165@e106497-lin.cambridge.arm.com>
Hi Liviu,
On 07/06/16 14:35, liviu.dudau at arm.com wrote:
> On Tue, Jun 07, 2016 at 01:06:00PM +0100, Robin Murphy wrote:
>> Having just inadvertently merged -next into my working branch, I find
>> dev6d910bfa809e ("drm/hlcd: Use lockless gem BO free callback") adversely
>> affecting my board's ability to boot ;)
>>
>> Since I (intentionally) don't have sufficient CMA to create a framebuffer,
>> drm_gem_cma_create() fails, unconditionally calls the now-NULL
>> drm->driver->gem_free_object() in its cleanup path, and fiery death
>> ensues...
>
> Thanks for reporting this. What other changes other than reducing the CMA
> allocation size do you have that I might need in order to reproduce this?
I've just confirmed a plain checkout of next-20160602, using arm64
defconfig + DRM + HDLCD + TDA998X and CMA_SIZE_MBYTES=1, booted on a
Juno, does the job:
[ 3.032402] hdlcd 7ff60000.hdlcd: bound 0-0070 (ops tda998x_ops)
[ 3.038388] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 3.044970] [drm] No driver support for vblank timestamp query.
[ 3.076973] hdlcd 7ff60000.hdlcd: failed to allocate buffer with size
7680000
[ 3.084081] Bad mode in Synchronous Abort handler detected, code
0x86000004 -- IABT (current EL)
[ 3.092815] CPU: 3 PID: 6 Comm: kworker/u12:0 Not tainted
4.7.0-rc1-next-20160602 #686
[ 3.100682] Hardware name: ARM Juno development board (r1) (DT)
[ 3.106567] Workqueue: deferwq deferred_probe_work_func
[ 3.111761] task: ffff8009768a3e80 ti: ffff8009768e8000 task.ti:
ffff8009768e8000
[ 3.119198] PC is at 0x0
[ 3.121720] LR is at drm_gem_cma_create+0x128/0x130
...and so on.
Today's -next, on the other hand, dodges the bullet entirely:
[ 2.903645] [drm] found ARM HDLCD version r0p0
[ 2.908122] hdlcd 7ff60000.hdlcd: master bind failed: -22
[ 2.913505] tda998x: probe of 0-0070 failed with error -22
[ 2.919141] [drm] found ARM HDLCD version r0p0
[ 2.923609] hdlcd 7ff50000.hdlcd: master bind failed: -22
[ 2.928991] tda998x: probe of 0-0071 failed with error -22
Oh well...
Robin.
WARNING: multiple messages have this Message-ID (diff)
From: Robin Murphy <robin.murphy@arm.com>
To: liviu.dudau@arm.com
Cc: daniel.vetter@ffwll.ch, linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org
Subject: Re: HDLCD crashes with 6d910bfa809e
Date: Tue, 7 Jun 2016 15:11:14 +0100 [thread overview]
Message-ID: <5756D602.4090305@arm.com> (raw)
In-Reply-To: <20160607133535.GA1165@e106497-lin.cambridge.arm.com>
Hi Liviu,
On 07/06/16 14:35, liviu.dudau@arm.com wrote:
> On Tue, Jun 07, 2016 at 01:06:00PM +0100, Robin Murphy wrote:
>> Having just inadvertently merged -next into my working branch, I find
>> dev6d910bfa809e ("drm/hlcd: Use lockless gem BO free callback") adversely
>> affecting my board's ability to boot ;)
>>
>> Since I (intentionally) don't have sufficient CMA to create a framebuffer,
>> drm_gem_cma_create() fails, unconditionally calls the now-NULL
>> drm->driver->gem_free_object() in its cleanup path, and fiery death
>> ensues...
>
> Thanks for reporting this. What other changes other than reducing the CMA
> allocation size do you have that I might need in order to reproduce this?
I've just confirmed a plain checkout of next-20160602, using arm64
defconfig + DRM + HDLCD + TDA998X and CMA_SIZE_MBYTES=1, booted on a
Juno, does the job:
[ 3.032402] hdlcd 7ff60000.hdlcd: bound 0-0070 (ops tda998x_ops)
[ 3.038388] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 3.044970] [drm] No driver support for vblank timestamp query.
[ 3.076973] hdlcd 7ff60000.hdlcd: failed to allocate buffer with size
7680000
[ 3.084081] Bad mode in Synchronous Abort handler detected, code
0x86000004 -- IABT (current EL)
[ 3.092815] CPU: 3 PID: 6 Comm: kworker/u12:0 Not tainted
4.7.0-rc1-next-20160602 #686
[ 3.100682] Hardware name: ARM Juno development board (r1) (DT)
[ 3.106567] Workqueue: deferwq deferred_probe_work_func
[ 3.111761] task: ffff8009768a3e80 ti: ffff8009768e8000 task.ti:
ffff8009768e8000
[ 3.119198] PC is at 0x0
[ 3.121720] LR is at drm_gem_cma_create+0x128/0x130
...and so on.
Today's -next, on the other hand, dodges the bullet entirely:
[ 2.903645] [drm] found ARM HDLCD version r0p0
[ 2.908122] hdlcd 7ff60000.hdlcd: master bind failed: -22
[ 2.913505] tda998x: probe of 0-0070 failed with error -22
[ 2.919141] [drm] found ARM HDLCD version r0p0
[ 2.923609] hdlcd 7ff50000.hdlcd: master bind failed: -22
[ 2.928991] tda998x: probe of 0-0071 failed with error -22
Oh well...
Robin.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-06-07 14:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 12:06 HDLCD crashes with 6d910bfa809e Robin Murphy
2016-06-07 12:06 ` Robin Murphy
2016-06-07 13:35 ` liviu.dudau at arm.com
2016-06-07 13:35 ` liviu.dudau
2016-06-07 14:11 ` Robin Murphy [this message]
2016-06-07 14:11 ` Robin Murphy
2016-06-07 14:14 ` liviu.dudau at arm.com
2016-06-07 14:14 ` liviu.dudau
2016-06-07 14:15 ` liviu.dudau at arm.com
2016-06-07 14:15 ` liviu.dudau
2016-06-07 14:34 ` liviu.dudau at arm.com
2016-06-07 14:34 ` liviu.dudau
2016-06-08 6:51 ` [PATCH] of: reserved_mem: restore old behavior when no region is defined Marek Szyprowski
2016-06-08 6:51 ` Marek Szyprowski
2016-06-08 6:51 ` Marek Szyprowski
2016-06-08 7:35 ` Sylwester Nawrocki
2016-06-08 7:35 ` Sylwester Nawrocki
2016-06-08 10:49 ` Liviu Dudau
2016-06-08 10:49 ` Liviu Dudau
2016-06-08 13:05 ` Rob Herring
2016-06-08 13:05 ` Rob Herring
2016-06-08 13:05 ` Rob Herring
2016-06-08 15:35 ` Sumit Semwal
2016-06-08 15:35 ` Sumit Semwal
2016-06-08 6:58 ` HDLCD crashes with 6d910bfa809e Marek Szyprowski
2016-06-08 6:58 ` Marek Szyprowski
2016-06-08 9:05 ` liviu.dudau at arm.com
2016-06-08 9:05 ` liviu.dudau
2016-06-08 10:01 ` Marek Szyprowski
2016-06-08 10:01 ` Marek Szyprowski
2016-06-08 10:42 ` liviu.dudau at arm.com
2016-06-08 10:42 ` liviu.dudau
2016-06-07 14:40 ` Daniel Vetter
2016-06-07 14:40 ` Daniel Vetter
2016-06-07 16:42 ` Robin Murphy
2016-06-07 16:42 ` Robin Murphy
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=5756D602.4090305@arm.com \
--to=robin.murphy@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.