From: robin.murphy@arm.com (Robin Murphy)
To: linux-arm-kernel@lists.infradead.org
Subject: HDLCD crashes with 6d910bfa809e
Date: Tue, 7 Jun 2016 17:42:18 +0100 [thread overview]
Message-ID: <5756F96A.4010208@arm.com> (raw)
In-Reply-To: <20160607144058.GB3363@phenom.ffwll.local>
On 07/06/16 15:40, Daniel Vetter wrote:
> On Tue, Jun 07, 2016 at 01:06:00PM +0100, Robin Murphy wrote:
>> Hi Daniel, Liviu,
>>
>> 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...
>
> Please make sure you have the drm fixes from 4.7-rc2 included, this issue
> is fixed there.
Ah, right you are, thanks - the fact that that the newer branches I
tried crashed or otherwise failed due to unrelated TDA998x problems
threw me off. I see Chris' fix there now.
Robin.
> -Daniel
>
prev parent reply other threads:[~2016-06-07 16:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 12:06 HDLCD crashes with 6d910bfa809e Robin Murphy
2016-06-07 13:35 ` liviu.dudau at arm.com
2016-06-07 14:11 ` Robin Murphy
2016-06-07 14:14 ` liviu.dudau at arm.com
2016-06-07 14:15 ` liviu.dudau at arm.com
2016-06-07 14:34 ` liviu.dudau at arm.com
2016-06-08 6:51 ` [PATCH] of: reserved_mem: restore old behavior when no region is defined Marek Szyprowski
2016-06-08 7:35 ` Sylwester Nawrocki
2016-06-08 10:49 ` Liviu Dudau
2016-06-08 13:05 ` Rob Herring
2016-06-08 15:35 ` Sumit Semwal
2016-06-08 6:58 ` HDLCD crashes with 6d910bfa809e Marek Szyprowski
2016-06-08 9:05 ` liviu.dudau at arm.com
2016-06-08 10:01 ` Marek Szyprowski
2016-06-08 10:42 ` liviu.dudau at arm.com
2016-06-07 14:40 ` Daniel Vetter
2016-06-07 16:42 ` Robin Murphy [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=5756F96A.4010208@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).