Bug 14491

Was this an image downloaded from the yocto project build or one you built locally? 

If downloaded, which image was it?
If built locally, what configuration was used to build it?

It is possible the 5.13 linux-libc-headers upgrade may have caused it but we're struggling to understand how to reproduce it and why qemux86/qemux8-64 are passing on the autobuilder.

We could do with more information to understand this, it would be helpful to be able to reproduce the issue.

(In reply to comment #1)
> Was this an image downloaded from the yocto project build or one you built
> locally? 
> 
> If downloaded, which image was it?
> If built locally, what configuration was used to build it?

Hi Richard, this failure was first observed on the genericx86/genericx86-64 images built by our internal autobuilder. However, to identify this issue also occurs on the genericx86-64 image from the yocto project build, I did run the test both manually and automatically on the genericx86-64 image downloaded from the yocto project build and the stap test case is still failing. Outputs are same as the info logged in the error log attached in this bug.

Image src:
https://autobuilder.yocto.io/pub/releases/yocto-3.4_M2.rc1/machines/genericx86-64/core-image-sato-sdk-genericx86-64.wic

> It is possible the 5.13 linux-libc-headers upgrade may have caused it but
> we're struggling to understand how to reproduce it and why qemux86/qemux8-64
> are passing on the autobuilder.

I will try to reproduce it on qemux86-64.

> We could do with more information to understand this, it would be helpful to
> be able to reproduce the issue.

Below is the hardware and configurations I used to reproduce this issue for genericx86-64 architecture: 

Target machine : Intel NUC7i7BNH

Steps taken to reproduce this issue : 
-Execute the stap test case manually and automatically.

Link for this test case :
https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/runtime/cases/stap.py


My local.conf's configurations :
**********************************************************
MACHINE = "genericx86-64"
DISTRO = "poky"
SDKMACHINE = "i686"
PACKAGE_CLASSES = "package_rpm package_deb package_ipk"
CORE_IMAGE_EXTRA_INSTALL += "mesa-demos"
HOSTTOOLS_NONFATAL += "git-lfs"
IMAGE_FSTYPES_append = " wic wic.bmap tar.gz"
INHERIT += "testimage"
TEST_SUITES_remove = "ptest ltp ltp_compliance"
TEST_TARGET = "simpleremote"
TEST_SERVER_IP = ""
TEST_TARGET_IP = ""
**********************************************************

Seems like there might be some changes in the field definitions due to the kernel updates, but I still need some more time to investigate it.

(In reply to comment #2)
> (In reply to comment #1)
> > Was this an image downloaded from the yocto project build or one you built
> > locally? 
> > 
> > If downloaded, which image was it?
> > If built locally, what configuration was used to build it?
> 
> Hi Richard, this failure was first observed on the genericx86/genericx86-64
> images built by our internal autobuilder. However, to identify this issue
> also occurs on the genericx86-64 image from the yocto project build, I did
> run the test both manually and automatically on the genericx86-64 image
> downloaded from the yocto project build and the stap test case is still
> failing. Outputs are same as the info logged in the error log attached in
> this bug.
> 
> Image src:
> https://autobuilder.yocto.io/pub/releases/yocto-3.4_M2.rc1/machines/
> genericx86-64/core-image-sato-sdk-genericx86-64.wic
> 
> > It is possible the 5.13 linux-libc-headers upgrade may have caused it but
> > we're struggling to understand how to reproduce it and why qemux86/qemux8-64
> > are passing on the autobuilder.
> 
> I will try to reproduce it on qemux86-64.
> 

This failure was not able to be reproduce on qemux86-64 image.

> > We could do with more information to understand this, it would be helpful to
> > be able to reproduce the issue.
> 
> Below is the hardware and configurations I used to reproduce this issue for
> genericx86-64 architecture: 
> 
> Target machine : Intel NUC7i7BNH
> 
> Steps taken to reproduce this issue : 
> -Execute the stap test case manually and automatically.
> 
> Link for this test case :
> https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/runtime/
> cases/stap.py
> 
> 
> My local.conf's configurations :
> **********************************************************
> MACHINE = "genericx86-64"
> DISTRO = "poky"
> SDKMACHINE = "i686"
> PACKAGE_CLASSES = "package_rpm package_deb package_ipk"
> CORE_IMAGE_EXTRA_INSTALL += "mesa-demos"
> HOSTTOOLS_NONFATAL += "git-lfs"
> IMAGE_FSTYPES_append = " wic wic.bmap tar.gz"
> INHERIT += "testimage"
> TEST_SUITES_remove = "ptest ltp ltp_compliance"
> TEST_TARGET = "simpleremote"
> TEST_SERVER_IP = ""
> TEST_TARGET_IP = ""
> **********************************************************

likely due to linux libc headers for 5.13 according to Richard.

Put in NEEDINFO accidentally.

I was able to reproduce this on genericx86-64 under runqemu.

https://sourceware.org/git/?p=systemtap.git;a=commitdiff;h=ef5a8b9eda402e4e96c4e3ce01e7ff95d3e10470

appears to fix it.

Noted & Thanks for the info!

http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=6c6dc194679ec907b77e4d792176ac0b84eaa38d

This issue still present in yocto-3.3.3.rc2

(In reply to comment #10)
> This issue still present in yocto-3.3.3.rc2

Thanks Jay. I have included Richard's patch for the next PR.

http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=hardknott&id=0cc1b4141dc840f36530f71b8b1d2a39e9f227ea