From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from vms173019pub.verizon.net (vms173019pub.verizon.net [206.46.173.19]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 1CD16E00C1E for ; Thu, 17 Apr 2014 16:17:58 -0700 (PDT) Received: from gandalf.denix.org ([unknown] [71.191.205.189]) by vms173019.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0N4700MX47D7FH30@vms173019.mailsrvcs.net> for yocto@yoctoproject.org; Thu, 17 Apr 2014 18:17:47 -0500 (CDT) Received: by gandalf.denix.org (Postfix, from userid 1000) id A37C7201BF; Thu, 17 Apr 2014 19:17:29 -0400 (EDT) Date: Thu, 17 Apr 2014 19:17:29 -0400 From: Denys Dmytriyenko To: Gary Thomas Message-id: <20140417231729.GL11339@denix.org> References: <534C0415.20701@mlbassoc.com> <3130526.9zUpmp9SKQ@peggleto-mobl5.ger.corp.intel.com> <20140415162639.GC11339@denix.org> <16254891.OyPbf7clBT@peggleto-mobl5.ger.corp.intel.com> <20140415171601.GD11339@denix.org> <20140415174112.GE11339@denix.org> <20140415194307.GG11339@denix.org> <534DBB9E.2030608@mlbassoc.com> <20140417191042.GK11339@denix.org> <53505A3B.2090007@mlbassoc.com> MIME-version: 1.0 In-reply-to: <53505A3B.2090007@mlbassoc.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: yocto@yoctoproject.org 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: Thu, 17 Apr 2014 23:18:02 -0000 Content-type: text/plain; charset=us-ascii Content-disposition: inline On Thu, Apr 17, 2014 at 04:48:27PM -0600, Gary Thomas wrote: > On 2014-04-17 13:10, Denys Dmytriyenko wrote: > > On Tue, Apr 15, 2014 at 05:07:10PM -0600, Gary Thomas wrote: > >> On 2014-04-15 13:43, Denys Dmytriyenko wrote: > >>> On Tue, Apr 15, 2014 at 01:41:12PM -0400, Denys Dmytriyenko wrote: > >>>>>>>> Some other things I tried with a "long" TMPDIR path (note that it's the > >>>>>>>> TMPDIR path that makes the difference - in my tests I've been using > >>>>>>>> /home/paul/poky/build2/much/longer/path/to/tmp). None of this helped: > >>>>>>>> > >>>>>>>> * kernel built with gcc 4.7.2 and binutils 2.23.2 > >>>>>>>> * u-boot built with gcc 4.7.2 and binutils 2.23.2 > >>>>>>>> * u-boot from http://downloads.angstrom-distribution.org/demo/beaglebone/ > >>>>>>>> * earlyprintk and CONFIG_DEBUG_LL - no additional output printed > >>>>>>>> > >>>>>>>> I think we're now at the point where we'd benefit from someone with better > >>>>>>>> knowledge debugging the issue. > >>>>>>> > >>>>>>> Ok, should we expand the search area? Since this is supposed to be vanilla > >>>>>>> 3.14 kernel, can we try other platforms and see if they are similarly > >>>>>>> affected? I'll try pinging our kernel guys for any ideas... > >>>>>> > >>>>>> As far as I know it has only been observed with beaglebone (both white and > >>>>>> black, if it makes a difference). FWIW, qemuarm images from the autobuilder > >>>>>> boot just fine, and apparently the same is true of edgerouter (different > >>>>>> architecture but also uses u-boot). > >>>>> > >>>>> But do those other platforms use uImage or zImage? > >>> > >>> I don't yet know what is going on, but building in the same directory with > >>> sources (B = S) makes it work regarless of the path length: > >>> > >>> /OE/RAM/poky-111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111/22222222222222222222222222222222222222222222222222222222222222222222/3333333333333333333333333333333333333333333333333333/tmp/work/beaglebone-poky-linux-gnueabi/linux-yocto/3.14+gitAUTOINC+928d7b2dda_0143c6ebb4-r0/linux > >>> > >>> So, I just commented out setting kernel-specific B in linux-yocto.inc and any > >>> kernel now boots with long path: > >>> > >>> #B = "${WORKDIR}/linux-${PACKAGE_ARCH}-${LINUX_KERNEL_TYPE}-build" > >>> > >>> I'm copying Richard and Bruce directly to see if they may have a quick insight > >>> and/or accept it as a workaround for the release. I'll keep digging further, > >>> but if anyone cares to verify the above workaround works for them, I would > >>> appreciate. Thanks! > >>> > >> > >> Verified - I rebuilt the kernel in a working tree with a longer > >> path (one in fact that had failed before) and it boots fine. > >> > >> Wonder what ${B} != ${S} is doing wacky...? > > > > Gary, et al, > > > > I've just submitted a patch to oe-core and yocto MLs that fixes this issue - > > could you please test it in your setup and confirm? Thanks! > > > > Yes, verified it works great! Thanks for figuring this one out. And thank you for stumbling upon it in the first place :) and your continued help validating it until completion! Thanks Stefan, Bill and everyone else involed. Now let's hope Richard takes it into the release shortly... :) -- Denys