From mboxrd@z Thu Jan 1 00:00:00 1970 From: arno@natisbad.org (Arnaud Ebalard) Date: Thu, 23 Oct 2014 23:52:22 +0200 Subject: [BISECTED] arm: mvebu: Kernel hang after ae9304c9d311 if OF_SELFTEST=y In-Reply-To: <87wq7q4kcp.fsf@natisbad.org> (Arnaud Ebalard's message of "Thu, 23 Oct 2014 22:11:34 +0200") References: <87mw8nt5io.fsf@natisbad.org> <5448EB5E.3010405@free-electrons.com> <87h9yuu9jk.fsf@natisbad.org> <87wq7q4kcp.fsf@natisbad.org> Message-ID: <87siie4fop.fsf@natisbad.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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. Ok, I just built an u-boot and two 3.17.1 kernels for versatile express, which I then loaded via qemu. The result is the same as for mvebu, i.e. w/o OF_SELFTEST the first kernel just boots as expected and the second kernel compiled w/ OF_SELFTEST hangs. Both kernels are built w/ appended dtb support. Cheers, a+ From mboxrd@z Thu Jan 1 00:00:00 1970 From: arno-LkuqDEemtHBg9hUCZPvPmw@public.gmane.org (Arnaud Ebalard) Subject: Re: [BISECTED] arm: mvebu: Kernel hang after ae9304c9d311 if OF_SELFTEST=y Date: Thu, 23 Oct 2014 23:52:22 +0200 Message-ID: <87siie4fop.fsf@natisbad.org> References: <87mw8nt5io.fsf@natisbad.org> <5448EB5E.3010405@free-electrons.com> <87h9yuu9jk.fsf@natisbad.org> <87wq7q4kcp.fsf@natisbad.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: <87wq7q4kcp.fsf-LkuqDEemtHBg9hUCZPvPmw@public.gmane.org> (Arnaud Ebalard's message of "Thu, 23 Oct 2014 22:11:34 +0200") Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Gregory CLEMENT Cc: Gaurav Minocha , Grant Likely , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, Jason Cooper , Andrew Lunn , Sebastian Hesselbarth List-Id: devicetree@vger.kernel.org Hi, > arno-LkuqDEemtHBg9hUCZPvPmw@public.gmane.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. Ok, I just built an u-boot and two 3.17.1 kernels for versatile express, which I then loaded via qemu. The result is the same as for mvebu, i.e. w/o OF_SELFTEST the first kernel just boots as expected and the second kernel compiled w/ OF_SELFTEST hangs. Both kernels are built w/ appended dtb support. 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