From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Pantelis Antoniou <panto@antoniou-consulting.com>
Cc: Tony Lindgren <tony@atomide.com>,
Grant Likely <grant.likely@linaro.org>,
linux-omap <linux-omap@vger.kernel.org>,
"Kristo, Tero" <t-kristo@ti.com>
Subject: Re: pandaboard boot crash with linux-next
Date: Wed, 19 Mar 2014 16:33:47 +0200 [thread overview]
Message-ID: <5329AACB.7080208@ti.com> (raw)
In-Reply-To: <AA9ED470-ADDB-4855-A016-5E36F983CF7D@antoniou-consulting.com>
[-- Attachment #1: Type: text/plain, Size: 1701 bytes --]
On 19/03/14 16:29, Pantelis Antoniou wrote:
> Hi Tomi,
>
> On Mar 19, 2014, at 4:25 PM, Tomi Valkeinen wrote:
>
>> On 17/03/14 16:09, Tomi Valkeinen wrote:
>>> Hi,
>>>
>>> I noticed that my omap4 panda does not boot with today's linux-next
>>> (8808b950581f71e3ee4cf8e6cae479f4c7106405). I didn't have much time to study
>>> it, but I didn't find any posts about the issue with a quick look. Below is
>>> the crash.
>>
>> I bisected this to the commit:
>>
>> commit ad2c12e9bc250b3387bcb4ab9ab114f43ff6122f
>> Author: Pantelis Antoniou <panto@antoniou-consulting.com>
>> Date: Fri Dec 13 20:08:59 2013 +0200
>>
>> of: device_node kobject lifecycle fixes
>>
>> After the move to having device nodes be proper kobjects the lifecycle
>> of the node needs to be controlled better.
>>
>> At first convert of_add_node() in the unflattened functions to
>> of_init_node() which initializes the kobject so that of_node_get/put
>> work correctly even before of_init is called.
>>
>> Afterwards introduce of_node_is_initialized & of_node_is_attached that
>> query the underlying kobject about the state (attached means kobj
>> is visible in sysfs)
>>
>> Using that make sure the lifecycle of the tree is correct at all
>> times.
>>
>> Signed-off-by: Pantelis Antoniou <panto@antoniou-consulting.com>
>> [grant.likely: moved of_node_init() calls, fixed up locking, and
>> dropped __of_populate() hunks]
>> Signed-off-by: Grant Likely <grant.likely@linaro.org>
>>
>
> Can you try this? It should fix it (plus it should be in -next soon)
Thanks, that fixes the issue (tested on omap4 panda).
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2014-03-19 14:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 14:09 pandaboard boot crash with linux-next Tomi Valkeinen
2014-03-18 8:32 ` Peter Ujfalusi
2014-03-18 9:47 ` Tero Kristo
2014-03-19 14:25 ` Tomi Valkeinen
2014-03-19 14:29 ` Pantelis Antoniou
2014-03-19 14:33 ` Tomi Valkeinen [this message]
2014-03-19 14:35 ` Pantelis Antoniou
2014-03-19 15:06 ` Grant Likely
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=5329AACB.7080208@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=grant.likely@linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=panto@antoniou-consulting.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).