<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>4548</bug_id>
          
          <creation_ts>2013-05-24 05:45:24 +0000</creation_ts>
          <short_desc>beagleboard could not startup with 20130521-1 image</short_desc>
          <delta_ts>2013-05-30 14:50:50 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>11</classification_id>
          <classification>Runtime</classification>
          <product>General Runtime</product>
          <component>General Runtime</component>
          <version>1.5</version>
          <rep_platform>Beagleboard</rep_platform>
          <op_sys>arm</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>DUPLICATE</resolution>
          <dup_id>4549</dup_id>
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Undecided</priority>
          <bug_severity>major</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Ning Zhang">ning.zhang</reporter>
          <assigned_to name="Bruce Ashfield">bruce.ashfield</assigned_to>
          <cc>dvhart</cc>
    
    <cc>ke.zou</cc>
    
    <cc>yi.zhao</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>33257</commentid>
    <comment_count>0</comment_count>
    <who name="Ning Zhang">ning.zhang</who>
    <bug_when>2013-05-24 05:45:24 +0000</bug_when>
    <thetext>Branch: poky/master
Git rev: 176a46b088135f2891983bb8540bc45389341d90

steps:
1. download beagleboard images from http://autobuilder.yoctoproject.org/pub/nightly/20130521-1
2. this image could not bootup the beagleboard xM target.

Set below bootup parameters:

setenv bootcmd &apos;mmc rescan 0; fatload mmc 0:1 0x80300000 uImage; bootm 0x80300000&apos;
setenv bootargs &apos;console=tty0 console=ttyO2,115200n8 root=/dev/mmcblk0p2 rootwait rootfstype=ext3 ro&apos;

the system hangs at &quot;Uncompressing Linux... done, booting the kernel.&quot; 



==================detail serial logs========================
Texas Instruments X-Loader 1.5.0 (May 13 2013 - 09:51:47)
Beagle xM
Reading boot sector
Loading u-boot.bin from mmc


U-Boot 2011.06 (May 13 2013 - 09:51:42)

OMAP36XX/37XX-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
OMAP3 Beagle board + LPDDR/NAND
I2C:   ready
DRAM:  512 MiB
NAND:  0 MiB
MMC:   OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment

In:    serial
Out:   serial
Err:   serial
Beagle unknown 0x02
No EEPROM on expansion board
Die ID #11c400229ff80000016830100e014012
Hit any key to stop autoboot:  0 
OMAP3 beagleboard.org # 
OMAP3 beagleboard.org # 
OMAP3 beagleboard.org # setenv bootcmd &apos;mmc rescan 0; fatload mmc 0:1 0x80300000 uImage; bootm 0x80300000&apos;
OMAP3 beagleboard.org # setenv bootargs &apos;console=tty0 console=ttyO2,115200n8 root=/dev/mmcblk0p2 rootwait rootfstype=ext3 ro&apos; 
OMAP3 beagleboard.org # boot
reading uImage

4302416 bytes read
## Booting kernel from Legacy Image at 80300000 ...
   Image Name:   Linux-3.4.36-yocto-standard
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4302352 Bytes = 4.1 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>33258</commentid>
    <comment_count>1</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2013-05-24 05:51:03 +0000</bug_when>
    <thetext>What&apos;s the important change here ? There have been no kernel 
changes at all ? If this using gcc 4.8, then document it.

We haven&apos;t fixed ARM boot support for gcc 4.8, so these images
should not be using gcc 4.8 as their default compiler, and we
won&apos;t be fixing all of these via defect.

So if this is 4.8, return it to the platform domain and indicate
they should be setting the preferred version of the toolchain to
a version that is known to work for these boards.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>33305</commentid>
    <comment_count>2</comment_count>
    <who name="Ning Zhang">ning.zhang</who>
    <bug_when>2013-05-27 07:59:53 +0000</bug_when>
    <thetext>(In reply to comment #1)
&gt; What&apos;s the important change here ? There have been no kernel 
&gt; changes at all ? If this using gcc 4.8, then document it.
&gt; 
&gt; We haven&apos;t fixed ARM boot support for gcc 4.8, so these images
&gt; should not be using gcc 4.8 as their default compiler, and we
&gt; won&apos;t be fixing all of these via defect.
&gt; 
&gt; So if this is 4.8, return it to the platform domain and indicate
&gt; they should be setting the preferred version of the toolchain to
&gt; a version that is known to work for these boards.

Hi, 

I rebuild a beagleboard image locally (master: 176a46b088135f2891983bb8540bc45389341d90), it could start up well. And i check the gcc version is &quot;gcc-4.7.2-r20&quot;.

But i am not sure the gcc version of the http://autobuilder.yoctoproject.org/pub/nightly/20130521-1 images. I only got the image files, but can not check the gcc version with the image.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>33378</commentid>
    <comment_count>3</comment_count>
    <who name="Yi Zhao">yi.zhao</who>
    <bug_when>2013-05-30 02:15:03 +0000</bug_when>
    <thetext>For the new build from http://autobuilder.yoctoproject.org/pub/nightly/20130528-2/ . The system can boot up without problems.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>33397</commentid>
    <comment_count>4</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2013-05-30 14:50:50 +0000</bug_when>
    <thetext>This was the result of a MUT build pulling in gcc 4.8 into sstate and the AB not rebuilding with 4.7. This is expected behavior as a change in the toolchain is explicitly prevented from triggering a rebuild.

We will track this with the qemuarm kernel boot failure, Bug 4549.

*** This bug has been marked as a duplicate of bug 4549 ***</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>