linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arno@natisbad.org (Arnaud Ebalard)
To: linux-arm-kernel@lists.infradead.org
Subject: [BISECTED] arm: mvebu: Kernel hang after ae9304c9d311 if OF_SELFTEST=y
Date: Thu, 23 Oct 2014 22:11:34 +0200	[thread overview]
Message-ID: <87wq7q4kcp.fsf@natisbad.org> (raw)
In-Reply-To: <87h9yuu9jk.fsf@natisbad.org> (Arnaud Ebalard's message of "Thu, 23 Oct 2014 16:48:15 +0200")

Hi,

arno at natisbad.org (Arnaud Ebalard) writes:

>>> I bisected it up to ae9304c9d31117 ("Adding selftest testdata
>>> dynamically into live tree"). For a while, my kernels are compiled w/
>>> OF_SELFTEST and it works w/o issue. After that commit, boot hangs as
>>
>> It would be interesting to have a feedback of a kernel with an appended dtb
>> and OF_SELFTEST enabled to a different platform (ie non mvebu). Then we
>> will know if it something related to mvebu or to the device tree support.
>>
>> I will try to see if I can do this.
>
> I can test that on a kirkwood (6282) this evening.

FWIW, the problem does not only show up on Armada 370 but also on
kirwood. I just tested it on a ReadyNAS Duo v2. I do not have any
other non-mvebu platform at hand ATM. I'll try and see if I can
find some ARM board to boot a recent kernel tomorrow.

Cheers,

a+

  reply	other threads:[~2014-10-23 20:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87mw8nt5io.fsf@natisbad.org>
2014-10-23 11:49 ` [BISECTED] arm: mvebu: Kernel hang after ae9304c9d311 if OF_SELFTEST=y Gregory CLEMENT
2014-10-23 14:48   ` Arnaud Ebalard
2014-10-23 20:11     ` Arnaud Ebalard [this message]
2014-10-23 21:52       ` Arnaud Ebalard

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=87wq7q4kcp.fsf@natisbad.org \
    --to=arno@natisbad.org \
    --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).