All of lore.kernel.org
 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 16:48:15 +0200	[thread overview]
Message-ID: <87h9yuu9jk.fsf@natisbad.org> (raw)
In-Reply-To: <5448EB5E.3010405@free-electrons.com> (Gregory CLEMENT's message of "Thu, 23 Oct 2014 13:49:50 +0200")

Hi,

Gregory CLEMENT <gregory.clement@free-electrons.com> writes:

> On 23/10/2014 13:00, Arnaud Ebalard wrote:
>> Hi,
>> 
>> Trying to boot a 3.17.1 (same thing w/ current tip of Linus tree or
>> 3.17.1) on two Marvell Armada 370 based platforms (NETGEAR ReadyNAS
>> 102 and Synology DS213j) ends up w/ the following:
>> 
>>    Starting kernel ...
>>    
>>    Uncompressing Linux... done, booting the kernel.
>>    
>>    Error: unrecognized/unsupported machine ID (r1 = 0x00000bde).
>>    
>>    Available machine support:
>>    
>>    ID (hex)        NAME
>>    ffffffff        Generic DT based system
>>    ffffffff        Marvell Armada 380/385 (Device Tree)
>>    ffffffff        Marvell Armada 375 (Device Tree)
>>    ffffffff        Marvell Armada 370/XP (Device Tree)
>>    
>>    Please check your kernel config and/or bootloader.
>> 
>> 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.

Cheers,

a+

WARNING: multiple messages have this Message-ID (diff)
From: arno-LkuqDEemtHBg9hUCZPvPmw@public.gmane.org (Arnaud Ebalard)
To: Gregory CLEMENT
	<gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Cc: Gaurav Minocha
	<gaurav.minocha.os-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Grant Likely
	<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>,
	Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>,
	Sebastian Hesselbarth
	<sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [BISECTED] arm: mvebu: Kernel hang after ae9304c9d311 if OF_SELFTEST=y
Date: Thu, 23 Oct 2014 16:48:15 +0200	[thread overview]
Message-ID: <87h9yuu9jk.fsf@natisbad.org> (raw)
In-Reply-To: <5448EB5E.3010405-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org> (Gregory CLEMENT's message of "Thu, 23 Oct 2014 13:49:50 +0200")

Hi,

Gregory CLEMENT <gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org> writes:

> On 23/10/2014 13:00, Arnaud Ebalard wrote:
>> Hi,
>> 
>> Trying to boot a 3.17.1 (same thing w/ current tip of Linus tree or
>> 3.17.1) on two Marvell Armada 370 based platforms (NETGEAR ReadyNAS
>> 102 and Synology DS213j) ends up w/ the following:
>> 
>>    Starting kernel ...
>>    
>>    Uncompressing Linux... done, booting the kernel.
>>    
>>    Error: unrecognized/unsupported machine ID (r1 = 0x00000bde).
>>    
>>    Available machine support:
>>    
>>    ID (hex)        NAME
>>    ffffffff        Generic DT based system
>>    ffffffff        Marvell Armada 380/385 (Device Tree)
>>    ffffffff        Marvell Armada 375 (Device Tree)
>>    ffffffff        Marvell Armada 370/XP (Device Tree)
>>    
>>    Please check your kernel config and/or bootloader.
>> 
>> 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.

Cheers,

a+
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-10-23 14:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23 11:00 [BISECTED] arm: mvebu: Kernel hang after ae9304c9d311 if OF_SELFTEST=y Arnaud Ebalard
2014-10-23 11:49 ` Gregory CLEMENT
2014-10-23 11:49   ` Gregory CLEMENT
2014-10-23 14:48   ` Arnaud Ebalard [this message]
2014-10-23 14:48     ` Arnaud Ebalard
2014-10-23 20:11     ` Arnaud Ebalard
2014-10-23 20:11       ` Arnaud Ebalard
2014-10-23 21:52       ` Arnaud Ebalard
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=87h9yuu9jk.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 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.