On 3 September 2012 05:41, Botao Sun botao.sun@linaro.org wrote:
- Zach
Sorry, I mean another Amit, Mr. Amit Pundir, he's working on Samsung related stuff I remembered.
Also, here is more information, I have tried several previous image, the last good one is build 47:
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
Therefore, I'm going to use this one as our weekly test target. However, please dig more on why build 48, 49 & 50 failed - bad thing started at build 48.
Thank you!
Botao,
Just had a second to look at this, I see:
U-Boot 2012.07-00053-gbf30cf4 (Sep 03 2012 - 07:03:03) for ORIGEN
CPU: Exynos4210@1000MHz
Board: ORIGEN DRAM: 1 GiB WARNING: Caches not enabled MMC: SAMSUNG SDHCI: 0 Timeout for status update! mmc fail to send stop cmd Using default environment
In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 reading boot.scr
397 bytes read Running bootscript from mmc0:2 ... ## Executing script at 42000000 reading uImage Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Transfer data timeout Error reading cluster
** Unable to read "uImage" from mmc 0:2 ** ** Can't read partition table on 0:0 ** ** Partition 2 not valid on device 0 **
** Unable to use mmc 0:2 for fatload ** ## Booting kernel from Legacy Image at 40007000 ... Image Name: Linux-3.4.8 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3879160 Bytes = 3.7 MiB Load Address: 40008000 Entry Point: 40008000 Verifying Checksum ... Bad Data CRC ERROR: can't get kernel image! ORIGEN #
on,
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
This would explain why it works in LAVA (since LAVA doesn't update the bootloader) but it doesn't work locally (since we do update the bootloader). Is this what you see?
BR Botao Sun
On Mon, Sep 3, 2012 at 8:25 PM, amit khare amit.khare@linaro.org wrote:
on it....
Regards, Amit
On 3 September 2012 15:21, Botao Sun botao.sun@linaro.org wrote:
Hi Amit,
Would you take a look at this issue?
Origen Jelly Bean boot failed.: https://bugs.launchpad.net/linaro-android/+bug/1045244
The weird thing is LAVA shows that it works well: http://validation.linaro.org/lava-server/dashboard/image-reports/origen-jb-g...
Is there anything I missed during SD card flashing?
Thank you!
BR Botao Sun
Can we try same image with the LAVA bootloader version to confirm that it's a bootloader thing? Also CCed jcriby for bootloader support.
Check with Dave in case we can't find the bootloader installed in LAVA case. On Sep 3, 2012 10:50 PM, "Zach Pfeffer" zach.pfeffer@linaro.org wrote:
On 3 September 2012 05:41, Botao Sun botao.sun@linaro.org wrote:
- Zach
Sorry, I mean another Amit, Mr. Amit Pundir, he's working on Samsung
related
stuff I remembered.
Also, here is more information, I have tried several previous image, the last good one is build 47:
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
Therefore, I'm going to use this one as our weekly test target. However, please dig more on why build 48, 49 & 50 failed - bad thing started at
build
Thank you!
Botao,
Just had a second to look at this, I see:
U-Boot 2012.07-00053-gbf30cf4 (Sep 03 2012 - 07:03:03) for ORIGEN
CPU: Exynos4210@1000MHz
Board: ORIGEN DRAM: 1 GiB WARNING: Caches not enabled MMC: SAMSUNG SDHCI: 0 Timeout for status update! mmc fail to send stop cmd Using default environment
In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 reading boot.scr
397 bytes read Running bootscript from mmc0:2 ... ## Executing script at 42000000 reading uImage Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Transfer data timeout Error reading cluster
** Unable to read "uImage" from mmc 0:2 ** ** Can't read partition table on 0:0 ** ** Partition 2 not valid on device 0 **
** Unable to use mmc 0:2 for fatload ** ## Booting kernel from Legacy Image at 40007000 ... Image Name: Linux-3.4.8 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3879160 Bytes = 3.7 MiB Load Address: 40008000 Entry Point: 40008000 Verifying Checksum ... Bad Data CRC ERROR: can't get kernel image! ORIGEN #
on,
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
This would explain why it works in LAVA (since LAVA doesn't update the bootloader) but it doesn't work locally (since we do update the bootloader). Is this what you see?
BR Botao Sun
On Mon, Sep 3, 2012 at 8:25 PM, amit khare amit.khare@linaro.org
wrote:
on it....
Regards, Amit
On 3 September 2012 15:21, Botao Sun botao.sun@linaro.org wrote:
Hi Amit,
Would you take a look at this issue?
Origen Jelly Bean boot failed.: https://bugs.launchpad.net/linaro-android/+bug/1045244
The weird thing is LAVA shows that it works well:
http://validation.linaro.org/lava-server/dashboard/image-reports/origen-jb-g...
Is there anything I missed during SD card flashing?
Thank you!
BR Botao Sun
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
The landing team is working on it. The issue seems to be due to recent patches to u-boot. On Sep 4, 2012 2:46 AM, "Alexander Sack" alexander.sack@linaro.org wrote:
Can we try same image with the LAVA bootloader version to confirm that it's a bootloader thing? Also CCed jcriby for bootloader support.
The builds are booting well with LAVA bootloader. We have all the results for these daily builds.
Check with Dave in case we can't find the bootloader installed in LAVA case. On Sep 3, 2012 10:50 PM, "Zach Pfeffer" zach.pfeffer@linaro.org wrote:
On 3 September 2012 05:41, Botao Sun botao.sun@linaro.org wrote:
- Zach
Sorry, I mean another Amit, Mr. Amit Pundir, he's working on Samsung
related
stuff I remembered.
Also, here is more information, I have tried several previous image, the last good one is build 47:
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
Therefore, I'm going to use this one as our weekly test target. However, please dig more on why build 48, 49 & 50 failed - bad thing started at
build
Thank you!
Botao,
Just had a second to look at this, I see:
U-Boot 2012.07-00053-gbf30cf4 (Sep 03 2012 - 07:03:03) for ORIGEN
CPU: Exynos4210@1000MHz
Board: ORIGEN DRAM: 1 GiB WARNING: Caches not enabled MMC: SAMSUNG SDHCI: 0 Timeout for status update! mmc fail to send stop cmd Using default environment
In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 reading boot.scr
397 bytes read Running bootscript from mmc0:2 ... ## Executing script at 42000000 reading uImage Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Transfer data timeout Error reading cluster
** Unable to read "uImage" from mmc 0:2 ** ** Can't read partition table on 0:0 ** ** Partition 2 not valid on device 0 **
** Unable to use mmc 0:2 for fatload ** ## Booting kernel from Legacy Image at 40007000 ... Image Name: Linux-3.4.8 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3879160 Bytes = 3.7 MiB Load Address: 40008000 Entry Point: 40008000 Verifying Checksum ... Bad Data CRC ERROR: can't get kernel image! ORIGEN #
on,
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
This would explain why it works in LAVA (since LAVA doesn't update the bootloader) but it doesn't work locally (since we do update the bootloader). Is this what you see?
BR Botao Sun
On Mon, Sep 3, 2012 at 8:25 PM, amit khare amit.khare@linaro.org
wrote:
on it....
Regards, Amit
On 3 September 2012 15:21, Botao Sun botao.sun@linaro.org wrote:
Hi Amit,
Would you take a look at this issue?
Origen Jelly Bean boot failed.: https://bugs.launchpad.net/linaro-android/+bug/1045244
The weird thing is LAVA shows that it works well:
http://validation.linaro.org/lava-server/dashboard/image-reports/origen-jb-g...
Is there anything I missed during SD card flashing?
Thank you!
BR Botao Sun
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
U-boot mmc for origen was broken in 2012.08.2 then fixed by applying a couple of reverts in 2012.08.3. The master branch was updated one week ago however the new tag was not applied until later in the week on Thursday.
--john
On Mon, Sep 3, 2012 at 3:16 PM, Alexander Sack alexander.sack@linaro.org wrote:
Can we try same image with the LAVA bootloader version to confirm that it's a bootloader thing? Also CCed jcriby for bootloader support.
Check with Dave in case we can't find the bootloader installed in LAVA case.
On Sep 3, 2012 10:50 PM, "Zach Pfeffer" zach.pfeffer@linaro.org wrote:
On 3 September 2012 05:41, Botao Sun botao.sun@linaro.org wrote:
- Zach
Sorry, I mean another Amit, Mr. Amit Pundir, he's working on Samsung related stuff I remembered.
Also, here is more information, I have tried several previous image, the last good one is build 47:
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
Therefore, I'm going to use this one as our weekly test target. However, please dig more on why build 48, 49 & 50 failed - bad thing started at build 48.
Thank you!
Botao,
Just had a second to look at this, I see:
U-Boot 2012.07-00053-gbf30cf4 (Sep 03 2012 - 07:03:03) for ORIGEN
CPU: Exynos4210@1000MHz
Board: ORIGEN DRAM: 1 GiB WARNING: Caches not enabled MMC: SAMSUNG SDHCI: 0 Timeout for status update! mmc fail to send stop cmd Using default environment
In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 reading boot.scr
397 bytes read Running bootscript from mmc0:2 ... ## Executing script at 42000000 reading uImage Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Transfer data timeout Error reading cluster
** Unable to read "uImage" from mmc 0:2 ** ** Can't read partition table on 0:0 ** ** Partition 2 not valid on device 0 **
** Unable to use mmc 0:2 for fatload ** ## Booting kernel from Legacy Image at 40007000 ... Image Name: Linux-3.4.8 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3879160 Bytes = 3.7 MiB Load Address: 40008000 Entry Point: 40008000 Verifying Checksum ... Bad Data CRC ERROR: can't get kernel image! ORIGEN #
on,
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
This would explain why it works in LAVA (since LAVA doesn't update the bootloader) but it doesn't work locally (since we do update the bootloader). Is this what you see?
BR Botao Sun
On Mon, Sep 3, 2012 at 8:25 PM, amit khare amit.khare@linaro.org wrote:
on it....
Regards, Amit
On 3 September 2012 15:21, Botao Sun botao.sun@linaro.org wrote:
Hi Amit,
Would you take a look at this issue?
Origen Jelly Bean boot failed.: https://bugs.launchpad.net/linaro-android/+bug/1045244
The weird thing is LAVA shows that it works well:
http://validation.linaro.org/lava-server/dashboard/image-reports/origen-jb-g...
Is there anything I missed during SD card flashing?
Thank you!
BR Botao Sun
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
Fahad,
Would you file a bug on this issue for tracking and verify that the tip build now works from, https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
?
On 4 September 2012 10:13, John Rigby john.rigby@linaro.org wrote:
U-boot mmc for origen was broken in 2012.08.2 then fixed by applying a couple of reverts in 2012.08.3. The master branch was updated one week ago however the new tag was not applied until later in the week on Thursday.
--john
On Mon, Sep 3, 2012 at 3:16 PM, Alexander Sack alexander.sack@linaro.org wrote:
Can we try same image with the LAVA bootloader version to confirm that it's a bootloader thing? Also CCed jcriby for bootloader support.
Check with Dave in case we can't find the bootloader installed in LAVA case.
On Sep 3, 2012 10:50 PM, "Zach Pfeffer" zach.pfeffer@linaro.org wrote:
On 3 September 2012 05:41, Botao Sun botao.sun@linaro.org wrote:
- Zach
Sorry, I mean another Amit, Mr. Amit Pundir, he's working on Samsung related stuff I remembered.
Also, here is more information, I have tried several previous image, the last good one is build 47:
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
Therefore, I'm going to use this one as our weekly test target. However, please dig more on why build 48, 49 & 50 failed - bad thing started at build 48.
Thank you!
Botao,
Just had a second to look at this, I see:
U-Boot 2012.07-00053-gbf30cf4 (Sep 03 2012 - 07:03:03) for ORIGEN
CPU: Exynos4210@1000MHz
Board: ORIGEN DRAM: 1 GiB WARNING: Caches not enabled MMC: SAMSUNG SDHCI: 0 Timeout for status update! mmc fail to send stop cmd Using default environment
In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 reading boot.scr
397 bytes read Running bootscript from mmc0:2 ... ## Executing script at 42000000 reading uImage Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Transfer data timeout Error reading cluster
** Unable to read "uImage" from mmc 0:2 ** ** Can't read partition table on 0:0 ** ** Partition 2 not valid on device 0 **
** Unable to use mmc 0:2 for fatload ** ## Booting kernel from Legacy Image at 40007000 ... Image Name: Linux-3.4.8 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3879160 Bytes = 3.7 MiB Load Address: 40008000 Entry Point: 40008000 Verifying Checksum ... Bad Data CRC ERROR: can't get kernel image! ORIGEN #
on,
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
This would explain why it works in LAVA (since LAVA doesn't update the bootloader) but it doesn't work locally (since we do update the bootloader). Is this what you see?
BR Botao Sun
On Mon, Sep 3, 2012 at 8:25 PM, amit khare amit.khare@linaro.org wrote:
on it....
Regards, Amit
On 3 September 2012 15:21, Botao Sun botao.sun@linaro.org wrote:
Hi Amit,
Would you take a look at this issue?
Origen Jelly Bean boot failed.: https://bugs.launchpad.net/linaro-android/+bug/1045244
The weird thing is LAVA shows that it works well:
http://validation.linaro.org/lava-server/dashboard/image-reports/origen-jb-g...
Is there anything I missed during SD card flashing?
Thank you!
BR Botao Sun
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
The landing team has fixed the issue. The status has been updated in the bug : https://bugs.launchpad.net/linaro-android/+bug/1045244
On 4 September 2012 20:51, Zach Pfeffer zach.pfeffer@linaro.org wrote:
Fahad,
Would you file a bug on this issue for tracking and verify that the tip build now works from,
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
?
On 4 September 2012 10:13, John Rigby john.rigby@linaro.org wrote:
U-boot mmc for origen was broken in 2012.08.2 then fixed by applying a couple of reverts in 2012.08.3. The master branch was updated one week ago however the new tag was not applied until later in the week on Thursday.
--john
On Mon, Sep 3, 2012 at 3:16 PM, Alexander Sack alexander.sack@linaro.org wrote:
Can we try same image with the LAVA bootloader version to confirm that
it's
a bootloader thing? Also CCed jcriby for bootloader support.
Check with Dave in case we can't find the bootloader installed in LAVA
case.
On Sep 3, 2012 10:50 PM, "Zach Pfeffer" zach.pfeffer@linaro.org
wrote:
On 3 September 2012 05:41, Botao Sun botao.sun@linaro.org wrote:
- Zach
Sorry, I mean another Amit, Mr. Amit Pundir, he's working on Samsung related stuff I remembered.
Also, here is more information, I have tried several previous image,
the
last good one is build 47:
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
Therefore, I'm going to use this one as our weekly test target.
However,
please dig more on why build 48, 49 & 50 failed - bad thing started
at
build 48.
Thank you!
Botao,
Just had a second to look at this, I see:
U-Boot 2012.07-00053-gbf30cf4 (Sep 03 2012 - 07:03:03) for ORIGEN
CPU: Exynos4210@1000MHz
Board: ORIGEN DRAM: 1 GiB WARNING: Caches not enabled MMC: SAMSUNG SDHCI: 0 Timeout for status update! mmc fail to send stop cmd Using default environment
In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 reading boot.scr
397 bytes read Running bootscript from mmc0:2 ... ## Executing script at 42000000 reading uImage Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Transfer data timeout Error reading cluster
** Unable to read "uImage" from mmc 0:2 ** ** Can't read partition table on 0:0 ** ** Partition 2 not valid on device 0 **
** Unable to use mmc 0:2 for fatload ** ## Booting kernel from Legacy Image at 40007000 ... Image Name: Linux-3.4.8 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3879160 Bytes = 3.7 MiB Load Address: 40008000 Entry Point: 40008000 Verifying Checksum ... Bad Data CRC ERROR: can't get kernel image! ORIGEN #
on,
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
This would explain why it works in LAVA (since LAVA doesn't update the bootloader) but it doesn't work locally (since we do update the bootloader). Is this what you see?
BR Botao Sun
On Mon, Sep 3, 2012 at 8:25 PM, amit khare amit.khare@linaro.org wrote:
on it....
Regards, Amit
On 3 September 2012 15:21, Botao Sun botao.sun@linaro.org wrote: > > Hi Amit, > > Would you take a look at this issue? > > Origen Jelly Bean boot failed.: > https://bugs.launchpad.net/linaro-android/+bug/1045244 > > The weird thing is LAVA shows that it works well: > >
http://validation.linaro.org/lava-server/dashboard/image-reports/origen-jb-g...
> > Is there anything I missed during SD card flashing? > > Thank you! > > > BR > Botao Sun
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
On 4 September 2012 10:23, Vishal Bhoj vishal.bhoj@linaro.org wrote:
The landing team has fixed the issue. The status has been updated in the bug : https://bugs.launchpad.net/linaro-android/+bug/1045244
Awesome. :) Thanks for the update Vishal.
On 4 September 2012 20:51, Zach Pfeffer zach.pfeffer@linaro.org wrote:
Fahad,
Would you file a bug on this issue for tracking and verify that the tip build now works from,
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
?
On 4 September 2012 10:13, John Rigby john.rigby@linaro.org wrote:
U-boot mmc for origen was broken in 2012.08.2 then fixed by applying a couple of reverts in 2012.08.3. The master branch was updated one week ago however the new tag was not applied until later in the week on Thursday.
--john
On Mon, Sep 3, 2012 at 3:16 PM, Alexander Sack alexander.sack@linaro.org wrote:
Can we try same image with the LAVA bootloader version to confirm that it's a bootloader thing? Also CCed jcriby for bootloader support.
Check with Dave in case we can't find the bootloader installed in LAVA case.
On Sep 3, 2012 10:50 PM, "Zach Pfeffer" zach.pfeffer@linaro.org wrote:
On 3 September 2012 05:41, Botao Sun botao.sun@linaro.org wrote:
- Zach
Sorry, I mean another Amit, Mr. Amit Pundir, he's working on Samsung related stuff I remembered.
Also, here is more information, I have tried several previous image, the last good one is build 47:
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
Therefore, I'm going to use this one as our weekly test target. However, please dig more on why build 48, 49 & 50 failed - bad thing started at build 48.
Thank you!
Botao,
Just had a second to look at this, I see:
U-Boot 2012.07-00053-gbf30cf4 (Sep 03 2012 - 07:03:03) for ORIGEN
CPU: Exynos4210@1000MHz
Board: ORIGEN DRAM: 1 GiB WARNING: Caches not enabled MMC: SAMSUNG SDHCI: 0 Timeout for status update! mmc fail to send stop cmd Using default environment
In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 reading boot.scr
397 bytes read Running bootscript from mmc0:2 ... ## Executing script at 42000000 reading uImage Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Transfer data timeout Error reading cluster
** Unable to read "uImage" from mmc 0:2 ** ** Can't read partition table on 0:0 ** ** Partition 2 not valid on device 0 **
** Unable to use mmc 0:2 for fatload ** ## Booting kernel from Legacy Image at 40007000 ... Image Name: Linux-3.4.8 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3879160 Bytes = 3.7 MiB Load Address: 40008000 Entry Point: 40008000 Verifying Checksum ... Bad Data CRC ERROR: can't get kernel image! ORIGEN #
on,
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
This would explain why it works in LAVA (since LAVA doesn't update the bootloader) but it doesn't work locally (since we do update the bootloader). Is this what you see?
BR Botao Sun
On Mon, Sep 3, 2012 at 8:25 PM, amit khare amit.khare@linaro.org wrote: > > on it.... > > Regards, > Amit > > > On 3 September 2012 15:21, Botao Sun botao.sun@linaro.org wrote: >> >> Hi Amit, >> >> Would you take a look at this issue? >> >> Origen Jelly Bean boot failed.: >> https://bugs.launchpad.net/linaro-android/+bug/1045244 >> >> The weird thing is LAVA shows that it works well: >> >> >> http://validation.linaro.org/lava-server/dashboard/image-reports/origen-jb-g... >> >> Is there anything I missed during SD card flashing? >> >> Thank you! >> >> >> BR >> Botao Sun > >
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
Hi, All
Maybe we can make lava use the boot loader of the test build to boot the test images, so that there will be no such inconsistency that "lava can boot but the image can not" or "lava can not boot but the image can boot"
Here is branch that I have tested on panda stable and aosp build: the https://code.launchpad.net/~liuyq0307/lava-dispatcher/test-bootloader/+merge...
Thanks, Yongqin Liu
On 4 September 2012 23:24, Zach Pfeffer zach.pfeffer@linaro.org wrote:
On 4 September 2012 10:23, Vishal Bhoj vishal.bhoj@linaro.org wrote:
The landing team has fixed the issue. The status has been updated in the bug : https://bugs.launchpad.net/linaro-android/+bug/1045244
Awesome. :) Thanks for the update Vishal.
On 4 September 2012 20:51, Zach Pfeffer zach.pfeffer@linaro.org wrote:
Fahad,
Would you file a bug on this issue for tracking and verify that the tip build now works from,
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
?
On 4 September 2012 10:13, John Rigby john.rigby@linaro.org wrote:
U-boot mmc for origen was broken in 2012.08.2 then fixed by applying a couple of reverts in 2012.08.3. The master branch was updated one week ago however the new tag was not applied until later in the week on Thursday.
--john
On Mon, Sep 3, 2012 at 3:16 PM, Alexander Sack alexander.sack@linaro.org wrote:
Can we try same image with the LAVA bootloader version to confirm that it's a bootloader thing? Also CCed jcriby for bootloader support.
Check with Dave in case we can't find the bootloader installed in LAVA case.
On Sep 3, 2012 10:50 PM, "Zach Pfeffer" zach.pfeffer@linaro.org wrote:
On 3 September 2012 05:41, Botao Sun botao.sun@linaro.org wrote: > + Zach > > Sorry, I mean another Amit, Mr. Amit Pundir, he's working on Samsung > related > stuff I remembered. > > Also, here is more information, I have tried several previous image, > the > last good one is build 47: > > > > https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams... > > Therefore, I'm going to use this one as our weekly test target. > However, > please dig more on why build 48, 49 & 50 failed - bad thing started > at > build > 48. > > Thank you!
Botao,
Just had a second to look at this, I see:
U-Boot 2012.07-00053-gbf30cf4 (Sep 03 2012 - 07:03:03) for ORIGEN
CPU: Exynos4210@1000MHz
Board: ORIGEN DRAM: 1 GiB WARNING: Caches not enabled MMC: SAMSUNG SDHCI: 0 Timeout for status update! mmc fail to send stop cmd Using default environment
In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 reading boot.scr
397 bytes read Running bootscript from mmc0:2 ... ## Executing script at 42000000 reading uImage Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Timeout for status update! mmc fail to send stop cmd Transfer data timeout Error reading cluster
** Unable to read "uImage" from mmc 0:2 ** ** Can't read partition table on 0:0 ** ** Partition 2 not valid on device 0 **
** Unable to use mmc 0:2 for fatload ** ## Booting kernel from Legacy Image at 40007000 ... Image Name: Linux-3.4.8 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3879160 Bytes = 3.7 MiB Load Address: 40008000 Entry Point: 40008000 Verifying Checksum ... Bad Data CRC ERROR: can't get kernel image! ORIGEN #
on,
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
This would explain why it works in LAVA (since LAVA doesn't update the bootloader) but it doesn't work locally (since we do update the bootloader). Is this what you see?
> > > BR > Botao Sun > > On Mon, Sep 3, 2012 at 8:25 PM, amit khare amit.khare@linaro.org > wrote: >> >> on it.... >> >> Regards, >> Amit >> >> >> On 3 September 2012 15:21, Botao Sun botao.sun@linaro.org wrote: >>> >>> Hi Amit, >>> >>> Would you take a look at this issue? >>> >>> Origen Jelly Bean boot failed.: >>> https://bugs.launchpad.net/linaro-android/+bug/1045244 >>> >>> The weird thing is LAVA shows that it works well: >>> >>> >>> http://validation.linaro.org/lava-server/dashboard/image-reports/origen-jb-g... >>> >>> Is there anything I missed during SD card flashing? >>> >>> Thank you! >>> >>> >>> BR >>> Botao Sun >> >> >
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
On 09/07/2012 02:49 AM, YongQin Liu wrote:
Hi, All
Maybe we can make lava use the boot loader of the test build to boot the test images, so that there will be no such inconsistency that "lava can boot but the image can not" or "lava can not boot but the image can boot"
Here is branch that I have tested on panda stable and aosp build: the https://code.launchpad.net/~liuyq0307/lava-dispatcher/test-bootloader/+merge...
This is a very clever hack!
I'm not sure how reliable having one u-boot load/exec another u-boot would be. I guess it can't be worse than what we have now, but I'd like to here what John thinks just to know what we are getting ourselves into here.
Thanks, Yongqin Liu
On 4 September 2012 23:24, Zach Pfeffer zach.pfeffer@linaro.org wrote:
On 4 September 2012 10:23, Vishal Bhoj vishal.bhoj@linaro.org wrote:
The landing team has fixed the issue. The status has been updated in the bug : https://bugs.launchpad.net/linaro-android/+bug/1045244
Awesome. :) Thanks for the update Vishal.
On 4 September 2012 20:51, Zach Pfeffer zach.pfeffer@linaro.org wrote:
Fahad,
Would you file a bug on this issue for tracking and verify that the tip build now works from,
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams...
?
On 4 September 2012 10:13, John Rigby john.rigby@linaro.org wrote:
U-boot mmc for origen was broken in 2012.08.2 then fixed by applying a couple of reverts in 2012.08.3. The master branch was updated one week ago however the new tag was not applied until later in the week on Thursday.
--john
On Mon, Sep 3, 2012 at 3:16 PM, Alexander Sack alexander.sack@linaro.org wrote:
Can we try same image with the LAVA bootloader version to confirm that it's a bootloader thing? Also CCed jcriby for bootloader support.
Check with Dave in case we can't find the bootloader installed in LAVA case.
On Sep 3, 2012 10:50 PM, "Zach Pfeffer" zach.pfeffer@linaro.org wrote: > > On 3 September 2012 05:41, Botao Sun botao.sun@linaro.org wrote: >> + Zach >> >> Sorry, I mean another Amit, Mr. Amit Pundir, he's working on Samsung >> related >> stuff I remembered. >> >> Also, here is more information, I have tried several previous image, >> the >> last good one is build 47: >> >> >> >> https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams... >> >> Therefore, I'm going to use this one as our weekly test target. >> However, >> please dig more on why build 48, 49 & 50 failed - bad thing started >> at >> build >> 48. >> >> Thank you! > > Botao, > > Just had a second to look at this, I see: > > U-Boot 2012.07-00053-gbf30cf4 (Sep 03 2012 - 07:03:03) for ORIGEN > > CPU: Exynos4210@1000MHz > > Board: ORIGEN > DRAM: 1 GiB > WARNING: Caches not enabled > MMC: SAMSUNG SDHCI: 0 > Timeout for status update! > mmc fail to send stop cmd > Using default environment > > In: serial > Out: serial > Err: serial > Hit any key to stop autoboot: 0 > reading boot.scr > > 397 bytes read > Running bootscript from mmc0:2 ... > ## Executing script at 42000000 > reading uImage > Timeout for status update! > mmc fail to send stop cmd > Timeout for status update! > mmc fail to send stop cmd > Timeout for status update! > mmc fail to send stop cmd > Timeout for status update! > mmc fail to send stop cmd > Timeout for status update! > mmc fail to send stop cmd > Timeout for status update! > mmc fail to send stop cmd > Timeout for status update! > mmc fail to send stop cmd > Timeout for status update! > mmc fail to send stop cmd > Timeout for status update! > mmc fail to send stop cmd > Timeout for status update! > mmc fail to send stop cmd > Timeout for status update! > mmc fail to send stop cmd > Transfer data timeout > Error reading cluster > > ** Unable to read "uImage" from mmc 0:2 ** > ** Can't read partition table on 0:0 ** > ** Partition 2 not valid on device 0 ** > > ** Unable to use mmc 0:2 for fatload ** > ## Booting kernel from Legacy Image at 40007000 ... > Image Name: Linux-3.4.8 > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 3879160 Bytes = 3.7 MiB > Load Address: 40008000 > Entry Point: 40008000 > Verifying Checksum ... Bad Data CRC > ERROR: can't get kernel image! > ORIGEN # > > on, > > > > https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-sams... > > This would explain why it works in LAVA (since LAVA doesn't update the > bootloader) but it doesn't work locally (since we do update the > bootloader). Is this what you see? > >> >> >> BR >> Botao Sun >> >> On Mon, Sep 3, 2012 at 8:25 PM, amit khare amit.khare@linaro.org >> wrote: >>> >>> on it.... >>> >>> Regards, >>> Amit >>> >>> >>> On 3 September 2012 15:21, Botao Sun botao.sun@linaro.org wrote: >>>> >>>> Hi Amit, >>>> >>>> Would you take a look at this issue? >>>> >>>> Origen Jelly Bean boot failed.: >>>> https://bugs.launchpad.net/linaro-android/+bug/1045244 >>>> >>>> The weird thing is LAVA shows that it works well: >>>> >>>> >>>> http://validation.linaro.org/lava-server/dashboard/image-reports/origen-jb-g... >>>> >>>> Is there anything I missed during SD card flashing? >>>> >>>> Thank you! >>>> >>>> >>>> BR >>>> Botao Sun >>> >>> >> > > > > -- > Zach Pfeffer > Android Platform Team Lead, Linaro Platform Teams > Linaro.org | Open source software for ARM SoCs > Follow Linaro: http://www.facebook.com/pages/Linaro > http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
On 7 September 2012 03:49, YongQin Liu yongqin.liu@linaro.org wrote:
Hi, All
Maybe we can make lava use the boot loader of the test build to boot the test images, so that there will be no such inconsistency that "lava can boot but the image can not" or "lava can not boot but the image can boot"
That is a great idea. Perhaps it can be done as a single test so we are sure the image boots.
anmar
linaro-android@lists.linaro.org
-
Alexander Sack -
Andy Doan -
anmar.oueja＠linaro.org -
John Rigby -
Vishal Bhoj -
YongQin Liu -
Zach Pfeffer