Date   

[PATCH 1/1] meta-sugarbay: switch to linux-yocto 3.0 kernel

tom.zanussi@...
 

From: Tom Zanussi <tom.zanussi@...>

Switch sugarbay to the 3.0 kernel, lock it down, and update kernel
SRCREVs.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
meta-sugarbay/conf/machine/sugarbay.conf | 1 +
.../recipes-kernel/linux/linux-yocto_3.0.bbappend | 7 +++++++
2 files changed, 8 insertions(+), 0 deletions(-)
create mode 100644 meta-sugarbay/recipes-kernel/linux/linux-yocto_3.0.bbappend

diff --git a/meta-sugarbay/conf/machine/sugarbay.conf b/meta-sugarbay/conf/machine/sugarbay.conf
index ebc6dbc..9450d97 100644
--- a/meta-sugarbay/conf/machine/sugarbay.conf
+++ b/meta-sugarbay/conf/machine/sugarbay.conf
@@ -15,6 +15,7 @@ MACHINE_FEATURES = "kernel26 screen keyboard pci usbhost ext2 ext3 x86 \
KERNEL_IMAGETYPE = "bzImage"

PREFERRED_PROVIDER_virtual/kernel = "linux-yocto"
+PREFERRED_VERSION_linux-yocto = "3.0+git%"
PREFERRED_PROVIDER_linux-libc-headers ?= "linux-libc-headers-yocto"

PREFERRED_PROVIDER_virtual/libx11 ?= "libx11-trim"
diff --git a/meta-sugarbay/recipes-kernel/linux/linux-yocto_3.0.bbappend b/meta-sugarbay/recipes-kernel/linux/linux-yocto_3.0.bbappend
new file mode 100644
index 0000000..57420f2
--- /dev/null
+++ b/meta-sugarbay/recipes-kernel/linux/linux-yocto_3.0.bbappend
@@ -0,0 +1,7 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+COMPATIBLE_MACHINE_sugarbay = "sugarbay"
+KMACHINE_sugarbay = "yocto/standard/common-pc-64/sugarbay"
+
+SRCREV_machine_pn-linux-yocto_sugarbay ?= "3216e7d5c3cada16161481826cdb39c930457587"
+SRCREV_meta_pn-linux-yocto_sugarbay ?= "9010d1cbef2633dac7e559a7705c326b7601dd4c"
--
1.7.0.4


[PATCH 0/1] switch meta-sugarbay to 3.0 kernel

tom.zanussi@...
 

From: Tom Zanussi <tom.zanussi@...>

Built and booted into sato - basic testing shows everything
works as expected.

The following changes since commit 96c247dad88b9fc0159b2a929216876d9fbb06dc:
Tom Zanussi (1):
meta-emenlow: fix glx bug

are available in the git repository at:

git://git.yoctoproject.org/meta-intel.git tzanussi/sugarbay-linux-3.0-switchover
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/log/?h=tzanussi/sugarbay-linux-3.0-switchover

Tom Zanussi (2):
meta-sugarbay: switch to linux-yocto 3.0 kernel

meta-jasperforest/conf/machine/jasperforest.conf | 1 +
.../recipes-kernel/linux/linux-yocto_3.0.bbappend | 8 ++++++++
meta-sugarbay/conf/machine/sugarbay.conf | 1 +
.../recipes-kernel/linux/linux-yocto_3.0.bbappend | 7 +++++++
4 files changed, 17 insertions(+), 0 deletions(-)
create mode 100644 meta-jasperforest/recipes-kernel/linux/linux-yocto_3.0.bbappend
create mode 100644 meta-sugarbay/recipes-kernel/linux/linux-yocto_3.0.bbappend


Minutes: Yocto Technical Team (Tuesday, July 26, 2011 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada))

Liu, Song <song.liu@...>
 

Attendees:
Saul, Tom, Paul, Jessica, Rahul, Koen, Joshua, Mark, Denys, Richard, Bruce, Song
 
Action Item List:
------------------------------------------------------------------------------------------------------------------------------------
* The team to review ALL bugs each owns and do some estimation. Please put the estimation on the white board by next Thursday (8/4/11)
------------------------------------------------------------------------------------------------------------------------------------
* Saul: talk to Jianjun, QA should work with developers to make sure we can cover more distro testing (informal) before major release. Joshua and Darren volunteers for some of these testing.
* Beth/Darren/ScottR: document the central location in the release, and put any doc changes in the location after release.
* Song will follow up with Tracey to make sure marketing planning happens between milestones so that there is no disruption to the development schedule.
  
Agenda:
 
- opens collection - 5 min (Song)
- Review M3 status and open issues - 15 min (team)
------------------------------------------------------
* Feature cut-off time is mid-day 27th, US pacific time. All committed features should be in by then and M3 will branch out.
------------------------------------------------------
* Beth's autobuilder infrastructure will move to M4 due to hardware issues. No impact to Yocto 1.1 release.
* Multi-lib plan: merge multi-lib tree with M3 branch at the point when M3 branches out.
* Mark needs to get some licensing statement for some of the code. Targeting today to get it done.
* HOB for M3 is on track.
* Demos: No resources allocated for demo during M3. Song will follow up with Tracey.
* Overall, M3 is on track to get us to point of the feature complete.
- M4
* The focus of M4 is bug fixing for 1.1. After M3 Sprint A, the team should review ALL the bugs they own and estimate the effort, then put the estimation on the white board. We will use that information to do M4 planning next Thursday (8/4/11)
- Action item review
* Team: please take a look at the post 1.1 items on the wiki page and let Song know if there is any comment or concerns. (Done, CCB approved)
* Saul: talk to Jianjun, QA should work with developers to make sure we can cover more distro testing (informal) before major release. Joshua and Darren volunteers for some of these testing.
* Beth/Darren/ScottR: document the central location in the release, and put any doc changes in the location after release.
* Song to setup go/no-go meeting next Monday to decide on the M2 release. (Done)


Weekly test report for Yocto 1.1 20110723 build

Fan, WenhuaX <wenhuax.fan@...>
 

Hi, All

This is the weekly test report for Yocto1.1 20110723 build. There is one new bug found. The qemuppc and qemumips images can not boot up due to kernel update to 3.0. Standby and I2C issue still exist on Emenlow. All the lsb image build failed on autobuilder. Psplash failed issue exist on Blacksand in current build. Xorg and broken grub still exist on Crownbay. 3D testing still is blocked on sugarbay. Broken ldd issue still exist also. The rpm/zypper install/removal consume disk space issue still exists. Perl still not found in qemu sato image. For bug fixing, ${B} issue for linux-yocto has been fixed. Non-GPLv3 issue for build system also fixed. Ld.so issue fixed on Sugarbay in current build.

The test report is archived @https://wiki.yoctoproject.org/wiki/Yocto_1.1_Weekly_Test_Report

 

 

Test Summary:

---------------------------------------

 

Test Result Summary

Component

Target

Status

Comments

BSP

SugarBay

GOOD

3D testing blocked due to libsdl.so

CrownBay-emgd

GOOD

Xorg eats lots of CPU time after standby; broken grub due to wrong root path

JasperForest

GOOD

I/OAT DMA engine init failed;

Blacksand

GOOD

Psplash failed when boot up Yocto

eMenlow

GOOD

I2C_transfer error; Standby failed;

Beagleboard

GOOD

Everything runs well

Routerstationpro

GOOD

Everything runs well

Mpc8315e-rdb

GOOD

Everything runs well

QEMU

qemux86

GOOD

Perl not exist

qemux86-64

GOOD

Perl not exist

qemuarm

GOOD

Perl not exist

qemuppc

BLOCK

The image can not boot up.

qemumips

BLOCK

The image can not boot up.

ADT

 

BUGGY

Unfs does not work with qemuppc;

 

Critical bugs, more than 50% test cases are blocked

 

Only Normal, Minor or Enhancement bugs, or less than 10% test cases failed

 

Normal, Major and Critical bugs, and more than 10% test cases failed

 

Detailed Test Result for each component

Target

Total TCs

Not Run

Passed

Failed

Not testable (Blocked)

Sugarbay Sato-SDK

59

0

57

0

2 (bug 883)

Jasperforest Sato-SDK

32

0

31

1 (bug 1188)

0

n450 Sato-SDK

56

0

56

0

0

eMenlow Sato-SDK

56

0

54

2(bug 310, 503)

0

Crownbay-Sato-SDK

56

0

56

0

0

Beagleboard

36

0

36

0

0

Routerstationpro

31

0

31

0

0

Mpc8315e-rdb

34

0

34

0

0

Qemux86-64 Sato

28

0

27

1 (bug 1172)

0

Qemux86-64 Sato-SDK

31

0

31

0

0

Qemux86 Sato

28

0

27

1 (bug 1172)

0

Qemux86 Sato-SDK

31

0

31

0

0

Qemumips Sato

28

0

0

0

28 (bug 1290)

Qemumips Sato-SDK

31

0

0

0

31 (bug 1290)

Qemuppc Sato

21

0

0

0

21 (bug 1290)

Qemuppc Sato-SDK

24

0

0

0

24 (bug 1290)

Qemuarm Sato

28

0

27

1 (bug 1172)

0

Qemuarm Sato-SDK

31

0

31

0

0

ADT

6

0

5

1 (bug 414)

0

Total

647

0

534

7

106

 

 

Commit Information

---------------------------------------

 

Tree/Branch: Poky/Master

Poky Commit id: eea4bd731ef286516ee1fb934fe2222a09c06e70

Meta Branch: Master

Meta Commit id: 96c247dad88b9fc0159b2a929216876d9fbb06dc

 

 

Issue Summary

---------------------------------------

 

Component

Bug Number

Target Milestone

System & Core OS

Installation & Boot

Bug 1211 - [Blacksand] Psplash failed when boot up Yocto

1.1 M3

System Usage

Bug 1172: Perl not exist in sato image

1.1

Bug 1174: [zypper/rpm] package install/removal costs lots of disk space

1.1 M3

New! Bug 1290: qemuppc minimal,sato,sato-sdk images boot failed ( nightly build 20110723-2)

---

Other

Bug 1236 - Broken ldd due to wrong path for ld.so

1.1 M3

Bug 1257 - [crownbay] broken grub due to wrong root path

1.1 M3

Bug 1258 -[crownbay] Xorg eats lots of CPU time after standby

1.1 M4

ADT

Bug 414: [PPC] kernel panic when booting poky-image-sdk-qemuppc through UNFS

1.1 M3

 

 

Verified Fixed Bug:

---------------------------------------

 

1.     Bug 1133 - No provider for core-image-minimal/basic for non-GPLv3 build

2.       Bug 1136 - do_menuconfig for linux-yocto needs ${B} exists

3.     Bug 1237 - [sugarbay] Inconsistency detected by ld.so: dl-deps.c: 622: _dl_map_object_deps: Assertion `nlist > 1' failed!

 


[ANNOUNCEMENT] Milestone 2 Released

Flanagan, Elizabeth <elizabeth.flanagan@...>
 

All,

We are pleased to announce the second milestone of the coming
October release of Yocto 1.1. This milestone release is available at:

http://mirrors.kernel.org/yocto/poky/poky-bernard-5.1.0-m2.tar.bz2

Additional tarballs for the meta-intel, meta-qt3 and eclipse plugin are
available at:

http://mirrors.kernel.org/yocto/poky/meta-intel-bernard-5.1.0-m2.tar.bz2
http://mirrors.kernel.org/yocto/poky/meta-qt3-bernard-5.1.0-m2.tar.bz2
http://mirrors.kernel.org/yocto/poky/eclipse-poky-bernard-5.1.0-m2.tar.bz2

Thanks you everyone for all the hard work.

------------------
Elizabeth Flanagan
Yocto Project
Release Engineer

--------------------
Bernard 5.1.0-m2 Errata
--------------------
Release name: poky-bernard-5.1.0-m2
Repo: git://git.yoctoproject.org/poky.git
Branch: 1.1_M2
Tag: 1.1_M2.final
Hash: a62982ffb6b35acc70bb30a429fc854cf9a8873f
Download locations:
http://autobuilder.yoctoproject.org/downloads/poky/poky-bernard-5.1.0-m2.tar.bz2
http://mirrors.kernel.org/yocto/poky/poky-bernard-5.1.0-m2.tar.bz2

--------------------
Features
--------------------
1. Layer tooling
2. Basic functions of the HOB.
3. Share gcc work directory.
4. Cache redesign and reimplementation.
5. Some performance improvement measures such as splitting libc,
removing perl-native from bld dep.
6. Beagle board XM update.
7. Tracing: Add Systemtap support for user space tracing
8. 3G support

--------------------
Known Issues
--------------------
766 [mpc8315e-rdb] USB does not work on mpc8315e-rdb
638 need documentation for sstate
689 BB_ENV_EXTRAWHITE does not respect CCACHE_DIR


--------------------
Bugs Fixed
--------------------
1208 busybox powertop mess up our eclipse plugin
1218 [HOB] package selection logic inconsistent after select/deselect
several times
1219 [HOB] lots of bug traces when launching hob
1237 [sugarbay] Inconsistency detected by ld.so: dl-deps.c: 622:
_dl_map_object_deps: Assertion `nlist > 1' failed!
1215 Can't build minimal image with IMAGE_LINGUAS set
773 [routerstationpro] USB does not work on routerstationpro
1038 Recipe alsa-tools does not build
1209 eglibc 2.13 r5: cannot stat localedef when
ENABLE_BINARY_LOCALE_GENERATION = "0"
1072 machine-specific xorg.confs not being picked up
1037 web browser can't handle https pages
1040 Recipe clutter-box2d does not build
1107 Open or add person in contacts may segfault on blacksand
1025 Release of documentation needs to be rethought.
1195 [mips toolchain] cvs configure fail with no cvs_cv_func_printf_ptr set
868 GUI Progress bar sits at 0% until done when using GUI's with none server
1132 libxml-simple-perl do_configure Failed if being built after libxml-sax-perl
891 clutter is not included in the poky-image-sato-sdk
896 [N450] poky-image-clutter build failure
963 kernel tarballs being served up by autobuilder contain
missing/corrupted branches
1085 fetcher2: try mirror after failing checksum from upstream
1194 support DSF debugger
1213 btrfs-tools parallel make failure
1180 bitbake -c listtasks doesn't print to the console
1091 Adding .bbappend should invalidate cache
1140 Can't build update-rc.d if BB_NO_NETWORK=1
1182 poky-init-build-env user feedback need updated
1148 libxml2.so.2 unknown version errors on bootup
1197 Refresh x-load to include 2efa178acd56d83c86210b5934895cfb9ea62125
1198 refresh u-boot to include a 2011.06 recipe
1009 Building world fails with errors of conflicting providers of ssh
1128 Meaningless error message when python v3 is the only python available
904 LSB 4.1:Printing absent cups, foomatic and gs
1090 LSB4.1: lsb graphic library can't be installed into lsb-image
1118 LSB 4.1: Param_Value error
1196 LSB 4.1: Compilation error from startup-notification_0.12.bb
1136 do_menuconfig for linux-yocto needs ${B} exists
933 Add a build profile which checks the things which may need a proxy
790 Layer dependency support
1142 git fetcher error when wrong protocol is specified is not helpful
1163 gcc-cross-canadian needs set to TRANSLATED_TARGET_ARCH
1173 toolchain build failed with 20110613 build on autobuilder
1156 BSP formfactors not being picked up
1168 qt4-tools-nativesdk does not build
1186 Recent bitbake change results in git fetch during parse
1170 login.defs file shipped with base-passwd causes runtime warnings
1020 LSB4.1: LSB test suite need libQtOpenGL.so for hardware ppc, x86 and x86-64


[PATCH 1/1] meta-jasperforeset: switch to linux-yocto 3.0 kernel

tom.zanussi@...
 

From: Tom Zanussi <tom.zanussi@...>

Switch jasperforest to the 3.0 kernel, lock it down, and update kernel
SRCREVs.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
meta-jasperforest/conf/machine/jasperforest.conf | 1 +
.../recipes-kernel/linux/linux-yocto_3.0.bbappend | 8 ++++++++
2 files changed, 9 insertions(+), 0 deletions(-)
create mode 100644 meta-jasperforest/recipes-kernel/linux/linux-yocto_3.0.bbappend

diff --git a/meta-jasperforest/conf/machine/jasperforest.conf b/meta-jasperforest/conf/machine/jasperforest.conf
index 3f8591a..1d875b5 100644
--- a/meta-jasperforest/conf/machine/jasperforest.conf
+++ b/meta-jasperforest/conf/machine/jasperforest.conf
@@ -15,6 +15,7 @@ MACHINE_FEATURES = "kernel26 screen keyboard pci usbhost ext2 ext3 x86 \
KERNEL_IMAGETYPE = "bzImage"

PREFERRED_PROVIDER_virtual/kernel = "linux-yocto"
+PREFERRED_VERSION_linux-yocto = "3.0+git%"
PREFERRED_PROVIDER_linux-libc-headers ?= "linux-libc-headers-yocto"

PREFERRED_PROVIDER_virtual/libx11 ?= "libx11-trim"
diff --git a/meta-jasperforest/recipes-kernel/linux/linux-yocto_3.0.bbappend b/meta-jasperforest/recipes-kernel/linux/linux-yocto_3.0.bbappend
new file mode 100644
index 0000000..52f0a6e
--- /dev/null
+++ b/meta-jasperforest/recipes-kernel/linux/linux-yocto_3.0.bbappend
@@ -0,0 +1,8 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+COMPATIBLE_MACHINE_jasperforest = "jasperforest"
+
+KMACHINE_jasperforest = "yocto/standard/common-pc-64/jasperforest"
+
+SRCREV_machine_pn-linux-yocto_jasperforest ?= "3216e7d5c3cada16161481826cdb39c930457587"
+SRCREV_meta_pn-linux-yocto_jasperforest ?= "9010d1cbef2633dac7e559a7705c326b7601dd4c"
--
1.7.0.4


[PATCH 0/1] switch meta-jasperforest to 3.0 kernel

tom.zanussi@...
 

From: Tom Zanussi <tom.zanussi@...>

Built and booted into sato - basic testing shows everything
works as expected.

The following changes since commit 96c247dad88b9fc0159b2a929216876d9fbb06dc:
Tom Zanussi (1):
meta-emenlow: fix glx bug

are available in the git repository at:

git://git.yoctoproject.org/meta-intel.git tzanussi/jasperforest-linux-3.0-switchover
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/log/?h=tzanussi/jasperforest-linux-3.0-switchover

Tom Zanussi (1):
meta-jasperforeset: switch to linux-yocto 3.0 kernel

meta-jasperforest/conf/machine/jasperforest.conf | 1 +
.../recipes-kernel/linux/linux-yocto_3.0.bbappend | 8 ++++++++
2 files changed, 9 insertions(+), 0 deletions(-)
create mode 100644 meta-jasperforest/recipes-kernel/linux/linux-yocto_3.0.bbappend


Re: Fullpass test report for Yocto1.1 M2 RC3 20110717

Xu, Jiajun <jiajun.xu@...>
 

Hi all,

The stress test on beagleboard pass today. Fullpass testing is finished for M2 RC3. There is no new issue found.

You could find the test report on https://wiki.yoctoproject.org/wiki/Yocto_1.1_Milestone_Test_Report.

 

Best Regards,

Jiajun

 

From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Xu, Jiajun
Sent: Saturday, July 23, 2011 12:39 AM
To: Fan, WenhuaX; poky@...; yocto@...
Subject: Re: [yocto] Fullpass test report for Yocto1.1 M2 RC3 20110717

 

Hi all,

Currently the only one testing not finished is the LTP stress testing on beagleboard, which is supposed to be finished next Monday.

QA does not find other new issues, compared with RC3 weekly test result – Crownbay has 2 issues on grub and Xorg separately. Gettext-native build issue on opensuse11.4 still exists but Saul already has a patch to fix the issue. For performance testing, sugarbay and crownbay have no regression compared with M1 result. Core build testing shows 109 minutes for a qemux86 core-image-sato build on a Core i7 860 machine.

 

 

Best Regards,

Jiajun

 

From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Fan, WenhuaX
Sent: Friday, July 22, 2011 5:23 PM
To: poky@...; yocto@...
Subject: [yocto] Fullpass test report for Yocto1.1 M2 RC3 20110717

 

Hi all,

       This is the Fullpass test report for Yocto1.1 M2 RC3 build. There is no new bug found in this testing. We add two stress testing for Beagleboard. Xorg eats lots of CPU’s resource after standby on Crownbay, expect for this issue, broken grub issue appear on this machine.

       Helltest and Crashme could pass 24 hours testing on Jasperforest. Idle power consumption of sugarbay and crownbay are 37.50W and 23.96W respectively. LTP and POSIX testing are pass. Crashme on Jasperforest and Beagleboard could pass 24 hours stress testing. And Helltest on Jasperforest could pass also, but Helltest on Beagleboard is on running.

 

 

Test Summary

---------------------------------------

 

Test Result Summary

Component

Target

Status

Comments

BSP

SugarBay

GOOD

3D testing blocked due to libsdl.so

CrownBay-emgd

GOOD

Xorg eats lots of CPU time after standby; broken grub due to wrong root path

JasperForest

GOOD

I/OAT DMA engine init failed;

Blacksand

GOOD

Psplash failed when boot up Yocto

eMenlow

GOOD

i2c_transfer error; Standby failed;

Beagleboard

GOOD

Everything runs well

Routerstationpro

GOOD

Everything runs well

Mpc8315e-rdb

GOOD

Everything runs well

QEMU

qemux86

GOOD

Perl not exist

qemux86-64

GOOD

Perl not exist

qemuarm

GOOD

Perl not exist

qemuppc

BUGGY

Perl not exist; unfs does not work with qemuppc.

qemumips

GOOD

Perl not exist

Core Build System

 

BUGGY

/usr/lib64/libxml2.so: undefined reference to `gzdirect@....2.3';
Skeleton initscript can not start with minimal image.

Power/Performance

 

GOOD

Power consumption of sugarbay and crownbay are 37.50W and 23.96W respectively

Compliance

 

GOOD

LTP result: https://wiki.yoctoproject.org/wiki/LTP_result
POSIX result: https://wiki.pokylinux.org/wiki/Posix_result

Stress

 

GOOD

Except for Helltest on Beagleboard is on running, Helltest and crashme could pass 24 hours testing

ADT

 

BUGGY

Unfs does not work with qemuppc;

 

Critical bugs, more than 50% test cases are blocked

 

Only Normal, Minor or Enhancement bugs, or less than 10% test cases failed

 

Normal, Major and Critical bugs, and more than 10% test cases failed

 

Detailed Test Result for each component

Target

Total TCs

Not Run

Passed

Failed

Not testable (Blocked)

Sugarbay Sato-SDK

59

0

57

0

2 (bug 883)

Jasperforest Sato-SDK

32

0

31

1 (bug 1188)

0

n450 Sato-SDK

56

0

56

0

0

eMenlow Sato-SDK

56

0

54

2(bug 310, 503)

0

Crownbay-Sato-SDK

56

0

56

0

0

Beagleboard

36

0

36

0

0

Routerstationpro

31

0

31

0

0

Mpc8315e-rdb

34

0

34

0

0

Qemux86-64 Sato

28

0

27

1 (bug 1172)

0

Qemux86-64 Sato-SDK

31

0

31

0

0

Qemux86 Sato

28

0

27

1 (bug 1172)

0

Qemux86 Sato-SDK

31

0

31

0

0

Qemumips Sato

28

0

27

1 (bug 1172)

0

Qemumips Sato-SDK

31

0

31

0

0

Qemuppc Sato

21

0

19

2 (bug 414, 1172)

0

Qemuppc Sato-SDK

24

0

23

1 (bug 414)

0

Qemuarm Sato

28

0

27

1 (bug 1172)

0

Qemuarm Sato-SDK

31

0

31

0

0

Core Build System

9

0

7

2 (bug 1242, 1165)

0

Power/Performance

5

0

5

0

0

Compliance

2

0

2

0

0

Stress

2

0

2

0

0

ADT

6

0

5

1 (bug 414)

0

Total

665

0

650

13

2

 

 

Commit Information

---------------------------------------

 

For Emenlow/Blacksand/Crownbay/Sugarbay/Jasperforest:

 

Tree/Branch: Poky/1.1_M2

Poky Commit id: fa4bcfdb73167f8159b88e5a4d711c0d37627a70

Meta Branch: 1.1_M2

Meta Commit id: 738d2bc6d1a0d7ff6589000893c1c8b4f983d76f

 

For Toolchain/Qemux86/Qemux86-64

 

Tree/Branch: Poky/1.1_M2

Poky Commit id: 93a2ca70482f09e93469481936302e7b6847156e

Meta Branch: 1.1_M2

Meta commit id1a6bcb62666b0fc67a66bd38a1c3f2a3399a249f

 

For qemuarm/mips/ppc/beagleboard/mpc8315e-rdb/routerstationpro:


Tree/Branch: Poky/1.1_M2
Poky Commit: 93a2ca70482f09e93469481936302e7b6847156e

 

 

Issue Summary

---------------------------------------

 

Component

Bug Number

Target Milestone

System & Core OS

Installation & Boot

Bug 1211 - [Blacksand] Psplash failed when boot up Yocto

1.1 M2

System Usage

Bug 1172: Perl not exist in sato image

1.1 M2

Bug 1174: [zypper/rpm] package install/removal costs lots of disk space

1.1 M3

Bug 1234: No response when I click the 'Install/Remove Software' icon

1.1 M4

Other

Bug 1236 - Broken ldd due to wrong path for ld.so

1.1 M3

New! Bug 1257 - [crownbay] broken grub due to wrong root path

1.1 M3

New! Bug 1258 -[crownbay] Xorg eats lots of CPU time after standby

1.1 M4

Core Build System

Bug 1165 - Skeleton initscript can not start with minimal image

1.1 M3

Bug 1242 - [opensuse11.4] /usr/lib64/libxml2.so: undefined reference to `gzdirect@....2.3'

1.1 M3

Power/Performance

Power consumption of sugarbay and crownbay are 37.50W and 23.96W respectively

 

Compliance

Compliance testing is finished, but result is still under analysis. LTP test result is on https://wiki.pokylinux.org/wiki/LTP_result
POSIX test result is on https://wiki.pokylinux.org/wiki/Posix_result

 

Stress

Crashme on Jasperforest and Beagleboard could pass 24 hours stress testing. And Helltest on Jasperforest could pass also, but Helltest on Beagleboard is on running.

 

ADT

Bug 414: [PPC] kernel panic when booting poky-image-sdk-qemuppc through UNFS

1.1 M3

 


Weekly Build Status

Saul Wold <sgw@...>
 

Folks,

There is a build available from the autobuilder

http://autobuilder.yoctoproject.org/nightly/20110723-2/

There were a couple of failures in the LSB-QT3 Builds that are being looked into. The failures occur in differnt packages for qemuarm and qemux86 LSB builds. I am trying to determine this is related to some shared state issues I have been seeing.

The meta-toolchain builds are running again due to an autobuilder related issue.

Please begin weekly testing with what is available.

Thanks
--
Sau!

Saul Wold
Yocto Component Wrangler @ Intel
Yocto Project / Poky Build System


Yocto weekly bug trend charts -- WW30

Xu, Jiajun <jiajun.xu@...>
 

Hi all,
RC3 is built out last week and QA is testing it. The new-submit vs. fixed bug is 26 vs. 24 for last week. The open bug number increased to 185 (No enhancement bugs counted). WDD number increased from 933 to 943. Several Critical and Major bugs are fixed in RC3. Meanwhile, a lot of hob bugs are submitted. Bug status of WW30 could be found on https://wiki.pokylinux.org/wiki/Yocto_Bug_Trend.

Best Regards,
Jiajun


Git services services are moving to a new host

Michael Halstead <michaelx.d.halstead@...>
 

On Monday July 25th from 10 to 11am PDT we will move git.yoctoproject.org and git.pokylinux.org to new hardware hosted at the OSU Open Source Lab. Read only access will be available during the entire process. Pushes will be refused until the transition is complete. If your push is accepted then the process has completed for you. Due to the nature of DNS propagation service will not become available to all users simultaneously.

Michael Halstead
Intel OTC Yocto


Re: Fullpass test report for Yocto1.1 M2 RC3 20110717

Xu, Jiajun <jiajun.xu@...>
 

Hi all,

Currently the only one testing not finished is the LTP stress testing on beagleboard, which is supposed to be finished next Monday.

QA does not find other new issues, compared with RC3 weekly test result – Crownbay has 2 issues on grub and Xorg separately. Gettext-native build issue on opensuse11.4 still exists but Saul already has a patch to fix the issue. For performance testing, sugarbay and crownbay have no regression compared with M1 result. Core build testing shows 109 minutes for a qemux86 core-image-sato build on a Core i7 860 machine.

 

 

Best Regards,

Jiajun

 

From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Fan, WenhuaX
Sent: Friday, July 22, 2011 5:23 PM
To: poky@...; yocto@...
Subject: [yocto] Fullpass test report for Yocto1.1 M2 RC3 20110717

 

Hi all,

       This is the Fullpass test report for Yocto1.1 M2 RC3 build. There is no new bug found in this testing. We add two stress testing for Beagleboard. Xorg eats lots of CPU’s resource after standby on Crownbay, expect for this issue, broken grub issue appear on this machine.

       Helltest and Crashme could pass 24 hours testing on Jasperforest. Idle power consumption of sugarbay and crownbay are 37.50W and 23.96W respectively. LTP and POSIX testing are pass. Crashme on Jasperforest and Beagleboard could pass 24 hours stress testing. And Helltest on Jasperforest could pass also, but Helltest on Beagleboard is on running.

 

 

Test Summary

---------------------------------------

 

Test Result Summary

Component

Target

Status

Comments

BSP

SugarBay

GOOD

3D testing blocked due to libsdl.so

CrownBay-emgd

GOOD

Xorg eats lots of CPU time after standby; broken grub due to wrong root path

JasperForest

GOOD

I/OAT DMA engine init failed;

Blacksand

GOOD

Psplash failed when boot up Yocto

eMenlow

GOOD

i2c_transfer error; Standby failed;

Beagleboard

GOOD

Everything runs well

Routerstationpro

GOOD

Everything runs well

Mpc8315e-rdb

GOOD

Everything runs well

QEMU

qemux86

GOOD

Perl not exist

qemux86-64

GOOD

Perl not exist

qemuarm

GOOD

Perl not exist

qemuppc

BUGGY

Perl not exist; unfs does not work with qemuppc.

qemumips

GOOD

Perl not exist

Core Build System

 

BUGGY

/usr/lib64/libxml2.so: undefined reference to `gzdirect@....2.3';
Skeleton initscript can not start with minimal image.

Power/Performance

 

GOOD

Power consumption of sugarbay and crownbay are 37.50W and 23.96W respectively

Compliance

 

GOOD

LTP result: https://wiki.yoctoproject.org/wiki/LTP_result
POSIX result: https://wiki.pokylinux.org/wiki/Posix_result

Stress

 

GOOD

Except for Helltest on Beagleboard is on running, Helltest and crashme could pass 24 hours testing

ADT

 

BUGGY

Unfs does not work with qemuppc;

 

Critical bugs, more than 50% test cases are blocked

 

Only Normal, Minor or Enhancement bugs, or less than 10% test cases failed

 

Normal, Major and Critical bugs, and more than 10% test cases failed

 

Detailed Test Result for each component

Target

Total TCs

Not Run

Passed

Failed

Not testable (Blocked)

Sugarbay Sato-SDK

59

0

57

0

2 (bug 883)

Jasperforest Sato-SDK

32

0

31

1 (bug 1188)

0

n450 Sato-SDK

56

0

56

0

0

eMenlow Sato-SDK

56

0

54

2(bug 310, 503)

0

Crownbay-Sato-SDK

56

0

56

0

0

Beagleboard

36

0

36

0

0

Routerstationpro

31

0

31

0

0

Mpc8315e-rdb

34

0

34

0

0

Qemux86-64 Sato

28

0

27

1 (bug 1172)

0

Qemux86-64 Sato-SDK

31

0

31

0

0

Qemux86 Sato

28

0

27

1 (bug 1172)

0

Qemux86 Sato-SDK

31

0

31

0

0

Qemumips Sato

28

0

27

1 (bug 1172)

0

Qemumips Sato-SDK

31

0

31

0

0

Qemuppc Sato

21

0

19

2 (bug 414, 1172)

0

Qemuppc Sato-SDK

24

0

23

1 (bug 414)

0

Qemuarm Sato

28

0

27

1 (bug 1172)

0

Qemuarm Sato-SDK

31

0

31

0

0

Core Build System

9

0

7

2 (bug 1242, 1165)

0

Power/Performance

5

0

5

0

0

Compliance

2

0

2

0

0

Stress

2

0

2

0

0

ADT

6

0

5

1 (bug 414)

0

Total

665

0

650

13

2

 

 

Commit Information

---------------------------------------

 

For Emenlow/Blacksand/Crownbay/Sugarbay/Jasperforest:

 

Tree/Branch: Poky/1.1_M2

Poky Commit id: fa4bcfdb73167f8159b88e5a4d711c0d37627a70

Meta Branch: 1.1_M2

Meta Commit id: 738d2bc6d1a0d7ff6589000893c1c8b4f983d76f

 

For Toolchain/Qemux86/Qemux86-64

 

Tree/Branch: Poky/1.1_M2

Poky Commit id: 93a2ca70482f09e93469481936302e7b6847156e

Meta Branch: 1.1_M2

Meta commit id1a6bcb62666b0fc67a66bd38a1c3f2a3399a249f

 

For qemuarm/mips/ppc/beagleboard/mpc8315e-rdb/routerstationpro:


Tree/Branch: Poky/1.1_M2
Poky Commit: 93a2ca70482f09e93469481936302e7b6847156e

 

 

Issue Summary

---------------------------------------

 

Component

Bug Number

Target Milestone

System & Core OS

Installation & Boot

Bug 1211 - [Blacksand] Psplash failed when boot up Yocto

1.1 M2

System Usage

Bug 1172: Perl not exist in sato image

1.1 M2

Bug 1174: [zypper/rpm] package install/removal costs lots of disk space

1.1 M3

Bug 1234: No response when I click the 'Install/Remove Software' icon

1.1 M4

Other

Bug 1236 - Broken ldd due to wrong path for ld.so

1.1 M3

New! Bug 1257 - [crownbay] broken grub due to wrong root path

1.1 M3

New! Bug 1258 -[crownbay] Xorg eats lots of CPU time after standby

1.1 M4

Core Build System

Bug 1165 - Skeleton initscript can not start with minimal image

1.1 M3

Bug 1242 - [opensuse11.4] /usr/lib64/libxml2.so: undefined reference to `gzdirect@....2.3'

1.1 M3

Power/Performance

Power consumption of sugarbay and crownbay are 37.50W and 23.96W respectively

 

Compliance

Compliance testing is finished, but result is still under analysis. LTP test result is on https://wiki.pokylinux.org/wiki/LTP_result
POSIX test result is on https://wiki.pokylinux.org/wiki/Posix_result

 

Stress

Crashme on Jasperforest and Beagleboard could pass 24 hours stress testing. And Helltest on Jasperforest could pass also, but Helltest on Beagleboard is on running.

 

ADT

Bug 414: [PPC] kernel panic when booting poky-image-sdk-qemuppc through UNFS

1.1 M3

 


"sat-solver" package fails to fetch

Robert P. J. Day
 

this is something i noticed a couple days back -- trying to "bitbake
-c fetchall world" failed on the sat-solver package:


NOTE: Running task 478 of 1358 (ID: 486,
/home/rpjday/yocto/poky.git/meta/recipes-extended/sat-solver/sat-solver_git.bb,
do_fetch)
NOTE: package
sat-solver-0.0-git1+0a7378d5f482f477a01cf1690d76871ab8bdcc32-r11: task
do_fetch: Started
ERROR: Function 'Fetcher failure for URL:
'git://gitorious.org/opensuse/sat-solver.git;protocol=git'. Unable to
fetch URL git://gitorious.org/opensuse/sat-solver.git;protocol=git
from any source.' failed
ERROR: Logfile of failure stored in:
/home/rpjday/yocto/build/tmp/work/qemux86-poky-linux/sat-solver-0.0-git1+0a7378d5f482f477a01cf1690d76871ab8bdcc32-r11/temp/log.do_fetch.10656
Log data follows:
| fatal: Not a git repository (or any of the parent directories): .git
| fatal: Not a git repository (or any of the parent directories):
.git
| ERROR: Function 'Fetcher failure for URL:
'git://gitorious.org/opensuse/sat-solver.git;protocol=git'. Unable to
fetch URL git://gitorious.org/opensuse/sat-solver.git;protocol=git
from any source.' failed
|
NOTE: package
sat-solver-0.0-git1+0a7378d5f482f477a01cf1690d76871ab8bdcc32-r11: task
do_fetch: Failed


rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================


Re: [PATCH] mpc8315e-rdb: Set TARGET_FPU correct

Gary Thomas
 

On 07/22/2011 10:13 AM, Saul Wold wrote:
On 07/14/2011 09:56 PM, Kumar Gala wrote:
The MPC8315E has a e300c3 core in it with 'classic' or normal PPC
floating point.

'SPE' floating point is what exists on the e500v2 core.

Signed-off-by: Kumar Gala<galak@...>
---
meta-yocto/conf/machine/mpc8315e-rdb.conf | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta-yocto/conf/machine/mpc8315e-rdb.conf b/meta-yocto/conf/machine/mpc8315e-rdb.conf
index 095d113..3f946a0 100644
--- a/meta-yocto/conf/machine/mpc8315e-rdb.conf
+++ b/meta-yocto/conf/machine/mpc8315e-rdb.conf
@@ -2,7 +2,7 @@
#@DESCRIPTION: Machine configuration for running

TARGET_ARCH = "powerpc"
-TARGET_FPU = "spe"
+TARGET_FPU = "hard"
This doesn't match the documentation:
./meta/conf/documentation.conf:TARGET_FPU[doc] = "Floating point option (mostly for FPU-less systems), can be 'soft' or empty
The file
meta/classes/icecc.bbclass
seems to be the only place where TARGET_FPU="hard" means anything.

--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------


Re: [PATCH] mpc8315e-rdb: Set TARGET_FPU correct

Saul Wold <sgw@...>
 

On 07/14/2011 09:56 PM, Kumar Gala wrote:
The MPC8315E has a e300c3 core in it with 'classic' or normal PPC
floating point.

'SPE' floating point is what exists on the e500v2 core.

Signed-off-by: Kumar Gala<galak@...>
---
meta-yocto/conf/machine/mpc8315e-rdb.conf | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta-yocto/conf/machine/mpc8315e-rdb.conf b/meta-yocto/conf/machine/mpc8315e-rdb.conf
index 095d113..3f946a0 100644
--- a/meta-yocto/conf/machine/mpc8315e-rdb.conf
+++ b/meta-yocto/conf/machine/mpc8315e-rdb.conf
@@ -2,7 +2,7 @@
#@DESCRIPTION: Machine configuration for running

TARGET_ARCH = "powerpc"
-TARGET_FPU = "spe"
+TARGET_FPU = "hard"

require conf/machine/include/tune-ppc603e.inc
Pulled into Yocto/Master

Thanks
Sau!


Re: [poky] Yocto bug traige call for action: Please Verify Resolved bugs in bugzilla

Rifenbark, Scott M <scott.m.rifenbark@...>
 

Fixed mine.

 

ScottR

 

From: poky-bounces@... [mailto:poky-bounces@...] On Behalf Of Zhang, Jessica
Sent: Thursday, July 21, 2011 4:00 PM
To: Poky Project; yocto@...
Subject: [poky] Yocto bug traige call for action: Please Verify Resolved bugs in bugzilla

 

Hi All,

 

In today’s bug triage meeting, we noticed there’re total 564 bugs that are in “Resolved” status.  The process is once a bug is in Resolved status, the original reporter of the bug should verify the resolution, either a valid fix or acceptable reason and mark the bug as “Verified”.  So please take a look at Yocto bugzilla (http://bugzilla.pokylinux.org/buglist.cgi?query_format=advanced&bug_status=RESOLVED) and verify those bugs that you’ve reported and now is marked as Resolved.

 

Thanks,

Jessica


Re: [PATCH] mpc8315e-rdb: Set TARGET_FPU correct

Kumar Gala <galak@...>
 

On Jul 14, 2011, at 11:56 PM, Kumar Gala wrote:

The MPC8315E has a e300c3 core in it with 'classic' or normal PPC
floating point.

'SPE' floating point is what exists on the e500v2 core.

Signed-off-by: Kumar Gala <galak@...>
---
meta-yocto/conf/machine/mpc8315e-rdb.conf | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
Richard,

ping. Bruce has ack'd this.

https://lists.yoctoproject.org/pipermail/yocto/2011-July/001915.html

- k


diff --git a/meta-yocto/conf/machine/mpc8315e-rdb.conf b/meta-yocto/conf/machine/mpc8315e-rdb.conf
index 095d113..3f946a0 100644
--- a/meta-yocto/conf/machine/mpc8315e-rdb.conf
+++ b/meta-yocto/conf/machine/mpc8315e-rdb.conf
@@ -2,7 +2,7 @@
#@DESCRIPTION: Machine configuration for running

TARGET_ARCH = "powerpc"
-TARGET_FPU = "spe"
+TARGET_FPU = "hard"

require conf/machine/include/tune-ppc603e.inc

--
1.7.3.4

_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Re: Bitbaking python fails

Andre Haupt <andre@...>
 

My target machine is atom-pc and my build host is Fedora 13 in a
VirtualBox machine.
I've not seen this before. You could run
"file /home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc/usr/lib/libgdbm.so.3.0.0" and check that its of the correct architecture since the invalid instruction is a weird error to see. I'm not 100% sure its that file its complaining about the instruction from though.
this is the output of the file command:
libgdbm.so.3.0.0: ELF 32-bit LSB shared object, Intel 80386, version 1
(SYSV), dynamically linked, not stripped
Sounds correct...

Does it do this every build, erroring in the same way? I know we did see
some emulation corruption type issues with virtualbox in the past
although they've not been reported for a while. It might be worth
starting a new build of "bitbake python" and see if the error is
reproducible too...
It happens reproducible when i do a "bitbake python".
Is this on a fresh clean build directory?
I did a fresh build in a new clean directory now and it fails too. The
error log (attached) is a bit different though.

What i did:

- source poky-init-build-env build python
- edit conf/local.conf to set
BB_NUMBER_THREADS = "2"
PARALLEL_MAKE = "-j 2"
MACHINE ??= "atom-pc"
- source poky-init-build-env build python, again (not sure if this is needed)
- bitbake python

You could also try "bitbake -c cleansstate python gdbm" on your existing
build directory and retry "bitbake python" to see if its reproducible
that way.
hmmh, the cleansstate task does neither exist for python nor for gdbm.

ERROR: Task do_cleansstate does not exist for target python

regards,

Andre


Re: Bitbaking python fails

Richard Purdie
 

On Fri, 2011-07-22 at 11:37 +0200, Andre Haupt wrote:
Hi Richard,

thanks for your answer. See below ...

On Fri, Jul 22, 2011 at 09:59:51AM +0100, Richard Purdie wrote:
On Fri, 2011-07-22 at 10:37 +0200, Andre Haupt wrote:
Hi all,

Building python for poky bernard fails for me with the following error:

...
...
Looking in tk80 for ['/home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc/usr/lib']
Looking in tcl80 for ['/home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc/usr/lib']
*** WARNING: renaming "gdbm" since importing it failed: libgdbm.so.3:
cannot open shared object file: No such file or directory
/bin/sh: line 1: 12830 Illegal instruction (core dumped)
LD_LIBRARY_PATH=/home/ahaupt/yocto-git/build/tmp/work/core2-poky-
linux/python-2.6.6-nk1.2/Python-2.6.6:/home/ahaupt/yocto-git/build
/tmp/sysroots/i686-linux/usr/bin/../lib/pseudo/lib:/home/ahaupt
/yocto-git/build/tmp/sysroots/i686-linux/usr/bin/../lib/pseudo/lib64
CC='ccache i586-poky-linux-gcc -m32 -march=core2 -msse3
-mtune=generic -mfpmath=sse
--sysroot=/home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc'
LDSHARED='ccache i586-poky-linux-gcc -m32 -march=core2 -msse3
-mtune=generic -mfpmath=sse
--sysroot=/home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc
-shared' LDFLAGS='-Wl,-O1 -Wl,--as-needed'
OPT='-fexpensive-optimizations -fomit-frame-pointer
-frename-registers -O2 -ggdb -feliminate-unused-debug-types'
/home/ahaupt/yocto-git/build/tmp/sysroots/i686-linux/usr/bin/python
-E ./setup.py -q build
make: *** [sharedmods] Error 132
FATAL: oe_runmake failed
ERROR: Function 'do_compile' failed (see
/home/ahaupt/yocto-git/build/tmp/work/core2-poky-linux/
python-2.6.6-nk1.2/temp/log.do_compile.12751
for further information)

Does this sound familiar to anyone? libgdbm.so.3 exists in
/home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc/usr/lib and points to
libgdbm.so.3.0.0

My target machine is atom-pc and my build host is Fedora 13 in a
VirtualBox machine.
I've not seen this before. You could run
"file /home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc/usr/lib/libgdbm.so.3.0.0" and check that its of the correct architecture since the invalid instruction is a weird error to see. I'm not 100% sure its that file its complaining about the instruction from though.
this is the output of the file command:
libgdbm.so.3.0.0: ELF 32-bit LSB shared object, Intel 80386, version 1
(SYSV), dynamically linked, not stripped
Sounds correct...

Does it do this every build, erroring in the same way? I know we did see
some emulation corruption type issues with virtualbox in the past
although they've not been reported for a while. It might be worth
starting a new build of "bitbake python" and see if the error is
reproducible too...
It happens reproducible when i do a "bitbake python".
Is this on a fresh clean build directory?

You could also try "bitbake -c cleansstate python gdbm" on your existing
build directory and retry "bitbake python" to see if its reproducible
that way.

Cheers,

Richard


Re: Bitbaking python fails

Andre Haupt <andre@...>
 

Hi Richard,

thanks for your answer. See below ...

On Fri, Jul 22, 2011 at 09:59:51AM +0100, Richard Purdie wrote:
On Fri, 2011-07-22 at 10:37 +0200, Andre Haupt wrote:
Hi all,

Building python for poky bernard fails for me with the following error:

...
...
Looking in tk80 for ['/home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc/usr/lib']
Looking in tcl80 for ['/home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc/usr/lib']
*** WARNING: renaming "gdbm" since importing it failed: libgdbm.so.3:
cannot open shared object file: No such file or directory
/bin/sh: line 1: 12830 Illegal instruction (core dumped)
LD_LIBRARY_PATH=/home/ahaupt/yocto-git/build/tmp/work/core2-poky-
linux/python-2.6.6-nk1.2/Python-2.6.6:/home/ahaupt/yocto-git/build
/tmp/sysroots/i686-linux/usr/bin/../lib/pseudo/lib:/home/ahaupt
/yocto-git/build/tmp/sysroots/i686-linux/usr/bin/../lib/pseudo/lib64
CC='ccache i586-poky-linux-gcc -m32 -march=core2 -msse3
-mtune=generic -mfpmath=sse
--sysroot=/home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc'
LDSHARED='ccache i586-poky-linux-gcc -m32 -march=core2 -msse3
-mtune=generic -mfpmath=sse
--sysroot=/home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc
-shared' LDFLAGS='-Wl,-O1 -Wl,--as-needed'
OPT='-fexpensive-optimizations -fomit-frame-pointer
-frename-registers -O2 -ggdb -feliminate-unused-debug-types'
/home/ahaupt/yocto-git/build/tmp/sysroots/i686-linux/usr/bin/python
-E ./setup.py -q build
make: *** [sharedmods] Error 132
FATAL: oe_runmake failed
ERROR: Function 'do_compile' failed (see
/home/ahaupt/yocto-git/build/tmp/work/core2-poky-linux/
python-2.6.6-nk1.2/temp/log.do_compile.12751
for further information)

Does this sound familiar to anyone? libgdbm.so.3 exists in
/home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc/usr/lib and points to
libgdbm.so.3.0.0

My target machine is atom-pc and my build host is Fedora 13 in a
VirtualBox machine.
I've not seen this before. You could run
"file /home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc/usr/lib/libgdbm.so.3.0.0" and check that its of the correct architecture since the invalid instruction is a weird error to see. I'm not 100% sure its that file its complaining about the instruction from though.
this is the output of the file command:
libgdbm.so.3.0.0: ELF 32-bit LSB shared object, Intel 80386, version 1
(SYSV), dynamically linked, not stripped

Does it do this every build, erroring in the same way? I know we did see
some emulation corruption type issues with virtualbox in the past
although they've not been reported for a while. It might be worth
starting a new build of "bitbake python" and see if the error is
reproducible too...
It happens reproducible when i do a "bitbake python".

regards,

Andre