From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from vms173017pub.verizon.net (vms173017pub.verizon.net [206.46.173.17]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 85EEEE00B83 for ; Mon, 14 Apr 2014 22:07:49 -0700 (PDT) Received: from gandalf.denix.org ([unknown] [71.191.205.189]) by vms173017.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0N4200KYL3KGAJ80@vms173017.mailsrvcs.net> for yocto@yoctoproject.org; Tue, 15 Apr 2014 00:07:34 -0500 (CDT) Received: by gandalf.denix.org (Postfix, from userid 1000) id 5E2B0200AC; Tue, 15 Apr 2014 01:07:28 -0400 (EDT) Date: Tue, 15 Apr 2014 01:07:28 -0400 From: Denys Dmytriyenko To: Richard Purdie Message-id: <20140415050728.GA11339@denix.org> References: <20140414154653.GZ3370@denix.org> <534C0415.20701@mlbassoc.com> <20140414160038.GB3370@denix.org> <534C0719.5050908@mlbassoc.com> <20140414160838.GC3370@denix.org> <534C40D9.40509@mlbassoc.com> <20140414224409.GF3370@denix.org> <1397521203.15843.62.camel@ted> <20140415013846.GG3370@denix.org> <1397537044.15843.66.camel@ted> MIME-version: 1.0 In-reply-to: <1397537044.15843.66.camel@ted> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: yocto@yoctoproject.org, Gary Thomas Subject: Re: BBB doesn't boot X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Apr 2014 05:07:51 -0000 Content-type: text/plain; charset=us-ascii Content-disposition: inline On Tue, Apr 15, 2014 at 05:44:04AM +0100, Richard Purdie wrote: > On Mon, 2014-04-14 at 21:38 -0400, Denys Dmytriyenko wrote: > > On Tue, Apr 15, 2014 at 01:20:03AM +0100, Richard Purdie wrote: > > > On Mon, 2014-04-14 at 18:44 -0400, Denys Dmytriyenko wrote: > > > > On Mon, Apr 14, 2014 at 02:11:05PM -0600, Gary Thomas wrote: > > > > > Very interesting results! These are the results from the build hosts I have: > > > > > Fedora 13 (i686) - fails > > > > > Fedora 17 (i686) - fails > > > > > Ubuntu 12.04 (x86_64) - boots > > > > > > > > Interesting indeed. I have no idea what's so special about Fedora host - this > > > > is the first time I hear about issues with it. I may try experimenting with > > > > different VMs once I have more time... > > > > > > I've been having a look at this. The biggest differences I can find > > > between working and non working builds is the path length to the build > > > directory for the kernel. This is from comparing vmlinux files from > > > working and non working builds. > > > > > > Works: > > > /home/paul/poky/build/tmp/work/beaglebone-poky-linux-gnueabi > > > > > > Doesn't Work: > > > /media/data1/build1/poky/build/tmp/work/beaglebone-poky-linux-gnueabi > > > > > > I also have been wondering if the version strings may be making a > > > difference. > > > > > > http://dan.rpsys.net/uImage-rp2 is a uImage from a broken build where I > > > truncated the path length to a "working" build path length and patched > > > in the same version strings: > > > > > > const char linux_banner[] = > > > "Linux version 3.14.0-yocto-standard (paul@ubuntu-build01) (gcc > > > version 4.8.2 (GCC) ) #1 PREEMPT Mon Apr 14 16:00:52 BST 2014\n"; > > > > > > const char linux_proc_banner[] = "%s version %s (paul@ubuntu-build01) > > > (gcc version 4.8.2 (GCC) ) %s\n"; > > > > > > to init/version.c. > > > > > > I don't have hardware and would be interested to know if the kernel > > > linked to above works or not. If it doesn't, it rules out these path and > > > string lengths, if it does work, it points to a problem there. > > > > Richard, > > > > Good catch! It boots: > > Thanks Denys, this helps narrow down the issue. I've shared > http://dan.rpsys.net/uImage-rp3 which is the same as the last one but > with my changes to version.c reverted. The one should tell us if its the > paths or the strings. This one also boots for me: Linux version 3.14.0-yocto-standard (richard@ted) (gcc version 4.8.2 (GCC) ) #2 PREEMPT Tue Apr 15 05:40:19 IST 2014 > I'm guessing the path problem is more likely but anything is possible. > This is starting to look like some kind of compiler or linker issue. If > it is that, it would help to have more data points about what works and > what doesn't. With that in mind could people who have good or bad builds > please share the paths they built the kernels in so we can see if we can > spot some kind of pattern. > > Cheers, > > Richard >