Hi Trevor,

I am afraid the error message did not make it into your previous e-mail.

:rjs

Hello Yocto Project,

I am working with a IMX8 based board from TechNexion.

I am having troubles getting the board to boot using netboot from within uboot.  

I have the tftp server setup as well as the NFS server setup on the host machine.  

Initially seems things to mount ok and the kernel starts to work with the remote filesystem.  then I get the following message in the kernel boot:

Trevor

-- 
-----
Rudolf J Streif
CEO/CTO ibeeto
+1.855.442.3386 x700

I'm using a boot2qt version of a warrior Yocto build for a raspberry pi4.

I'm trying to apply a patch to a driver in the linux kernel. I'm following the procedures laid out in the
book "Embedded Linux Systems with the Yocto Project".

I already have a kernel .bbappend file that I'm using to modify the kernel config and that is working correctly.

I started with a patch file that I found on the internet that addressed the problem that I have and I added
support for it to my .bbappend file. I know that it has been found correctly because I initially specified the
file path incorrectly and received an error.

After building my image I go to look at the STAGING_KERNEL_DIR and I do not see my changes applied to the
file. I even added an error to the patch to see if it was compiling and it didn't trigger the error.


At this point I went back fully to "Embedded Linux Systems with the Yocto Project" and created my own
patch. I still don't see it being applied.

Can somebody please tell me where I should see the patch applied?

Here is how I modified my .bbappend:


# additions to Kernel configuration

SRC_URi += "file://0001-drm-vc4-Keep-the-binner-BO-through-suspend-GWL.patch"

do_configure_append() {
.
.
.
}


And here is the patch:


From d95e6ead8d25165014f8746082656da6345889b0 Mon Sep 17 00:00:00 2001
From: Greg Wilson-Lindberg <gwilson@...>
Date: Tue, 10 Mar 2020 16:29:08 -0700
Subject: [PATCH 1/1] drm-vc4-Keep-the-binner-BO-through-suspend-GWL

---
 drivers/gpu/drm/vc4/vc4_v3d.c | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/drivers/gpu/drm/vc4/vc4_v3d.c b/drivers/gpu/drm/vc4/vc4_v3d.c
index e47e29426078..ff7812066668 100644
--- a/drivers/gpu/drm/vc4/vc4_v3d.c
+++ b/drivers/gpu/drm/vc4/vc4_v3d.c
@@ -303,9 +303,6 @@ static int vc4_v3d_runtime_suspend(struct device *dev)
 
     vc4_irq_uninstall(vc4->dev);
 
-    drm_gem_object_put_unlocked(&vc4->bin_bo->base.base);
-    vc4->bin_bo = NULL;
-
     clk_disable_unprepare(v3d->clk);
 
     return 0;
@@ -317,10 +314,6 @@ static int vc4_v3d_runtime_resume(struct device *dev)
     struct vc4_dev *vc4 = v3d->vc4;
     int ret;
 
-    ret = vc4_allocate_bin_bo(vc4->dev);
-    if (ret)
-        return ret;
-
     ret = clk_prepare_enable(v3d->clk);
     if (ret != 0)
         return ret;
--
2.17.1


Thanks in advance,
Greg Wilson-Lindberg

On Tue, 2020-03-10 at 11:33 +0000, Mikko.Rapeli@... wrote:

On Fri, Feb 28, 2020 at 11:25:59PM +0000, Richard Purdie wrote:

On Fri, 2020-02-28 at 22:51 +0000, Sean McKay wrote:

This is probably a fairly short question (I hope):
I’m working on a branch based on zeus. I found a bug in the way that
one of our recipes was handling something during do_configure (which
caused an error to pop up in a do_compile task). When I modified the
do_configure task (do_configure_append, actually) to behave properly
(which involved changing the actual commands run in that function)
and reran bitbake -c compile <recipe>, the do_configure task wasn’t
rerun despite the change to the function’s code.

Is it safe to assume this means we’ve done something to mess up the
way our system is processing things? Or is that expected behavior

Its not expected behaviour and yes, it sounds like something is messed
up...

This is what I've come to expect with yocto 2.0 jethro, 2.5 sumo and
3.0 zeus.

That's why I always write:

$ bitbake -c clean recipe && bitbake -c cleansstate && bitbake -c compile recipe

when debugging changes in recipes to_compile and other dependent tasks.
I'm also cleaning up sstate to be sure it's not corrupt or filled with
somehow bad data.

This is bad and shouldn't be happening. Can anyone provide some
examples I can look at?

You shouldn't ever need to run cleansstate in particular. If you have
to, there is another underlying bug that should get fixed.

Cheers,

Richard

On Fri, Feb 28, 2020 at 11:25:59PM +0000, Richard Purdie wrote:

On Fri, 2020-02-28 at 22:51 +0000, Sean McKay wrote:

This is probably a fairly short question (I hope):
I’m working on a branch based on zeus. I found a bug in the way that
one of our recipes was handling something during do_configure (which
caused an error to pop up in a do_compile task). When I modified the
do_configure task (do_configure_append, actually) to behave properly
(which involved changing the actual commands run in that function)
and reran bitbake -c compile <recipe>, the do_configure task wasn’t
rerun despite the change to the function’s code.

Is it safe to assume this means we’ve done something to mess up the
way our system is processing things? Or is that expected behavior

Its not expected behaviour and yes, it sounds like something is messed
up...

This is what I've come to expect with yocto 2.0 jethro, 2.5 sumo and
3.0 zeus.

That's why I always write:

$ bitbake -c clean recipe && bitbake -c cleansstate && bitbake -c compile recipe

when debugging changes in recipes to_compile and other dependent tasks.
I'm also cleaning up sstate to be sure it's not corrupt or filled with
somehow bad data.

-Mikko

Hi JH,

On Tue, Mar 10, 2020 at 08:23:37PM +1100, JH wrote:

Hi,

I could not find u-boot-fw-utils recipe from OE git repository, when I
added it to build package, it did build u-boot-fw-utils/1_2019.07-r0
from git://git.denx.de/u-boot.git, but I could not make a bbapend to
it as I don't know what is the bb name.

It was recently changed to libubootenv IIRC. Are you sure it was taken
from u-boot git repo?

In zeus you have both available if you have meta-swupdate layer but
u-boot-fw-utils is still present in openembedded-core.

In master, only libubootenv exists in openembedded-core.

Are you using master for poky/openembedded?

FWIW, what a recipe provides either at runtime or at buildtime is
(R)PROVIDES, c.f.:
http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-bsp/u-boot/libubootenv_0.2.bb?h=master

Quentin

Hi,

I could not find u-boot-fw-utils recipe from OE git repository, when I
added it to build package, it did build u-boot-fw-utils/1_2019.07-r0
from git://git.denx.de/u-boot.git, but I could not make a bbapend to
it as I don't know what is the bb name.

Appreciate your help and advice.

Thank you.

Kind regards,

- jh

On Wed, Feb 19, 2020 at 11:01 PM Khem Raj <raj.khem@...> wrote:

On 2/17/20 11:55 PM, Marek Belisko wrote:

Hi,

I'm debugging strange issue that do_rootfs task took ~50 minutes. I
enabled buildstats and from that I learned it's quite long. Any ideas
how to debug this issue? My idea was to add timestamp to do_rootfs
tasks but I'm not sure if it's even possible. Thanks.

how big is the image its creating, might affect the time. Secondly
use some system perf monitor to see which tool is taking so long.

Image is ~1GB so I would say quite
I can see that python3 took ~75-100% cpu when doing do_rootfs. We
tested on 16.04 + 18.04 Ubuntu server it's same.
Which perf monitor you had in mind? Thanks.

BR,

marek

BR,

marek

--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com

Hi,

You'd be better off asking these questions on the meta-virtualization
mailing list. That's where you'll find the Xen folks.

Thanks, I'll direct any follow-up questions regarding Xen there.

But as for the kernel options, it depends on what kernel you are
using, release, etc. Last I checked, the raspberrypi wouldn't
directly use the fragments from meta-virt, so yes, you'd need to
ensure they are set in your own layer/defconfig.

Ahh, thank you, you managed to switch on the light bulb! :)
Checking the kernel recipes I see now that meta-virt has a
linux-yocto_4.19.bbappend file, whereas meta-raspberrypi uses
linux-raspberrypi_4.19.bb; so as you said, the meta-virt configuration
is never applied due to different versions. Being new to yocto I did
not make that connection immediately, I guess I did miss the obvious.
;)

If I understand you correctly, I need to add a
linux-raspberrypi_4.19.bbappend file in my own layer that applies the
Xen configuration fragments.
That makes sense, thanks again!

Best regards,
Aljoscha

Add missing runtime dependencies otherwise /usr/bin/oscapd can not
startup.

Signed-off-by: Yi Zhao <yi.zhao@...>
---
.../openscap-daemon/openscap-daemon_0.1.10.bb | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/meta-security-compliance/recipes-openscap/openscap-daemon/openscap-daemon_0.1.10.bb b/meta-security-compliance/recipes-openscap/openscap-daemon/openscap-daemon_0.1.10.bb
index ca6e030..a775021 100644
--- a/meta-security-compliance/recipes-openscap/openscap-daemon/openscap-daemon_0.1.10.bb
+++ b/meta-security-compliance/recipes-openscap/openscap-daemon/openscap-daemon_0.1.10.bb
@@ -17,4 +17,7 @@ inherit setuptools3

S = "${WORKDIR}/git"

-RDEPENDS_${PN} = "python"
+RDEPENDS_${PN} = "openscap scap-security-guide \
+ python3-core python3-dbus \
+ python3-pygobject \
+ "
--
2.17.1

ping

Hello,

Thud has moved to "Community supported" today.

The older releases have moved to EOL as no one has stepped up to take on
the maintenance of those older branches.


regards,
Armin

dropped patch now included in update

Signed-off-by: Armin Kuster <akuster808@...>
---
...SNR_xxx-instead-of-__NR_xxx-for-sysc.patch | 45 -------------------
...ibseccomp_2.4.2.bb => libseccomp_2.4.3.bb} | 3 +-
2 files changed, 1 insertion(+), 47 deletions(-)
delete mode 100644 recipes-security/libseccomp/files/0001-tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch
rename recipes-security/libseccomp/{libseccomp_2.4.2.bb => libseccomp_2.4.3.bb} (90%)

diff --git a/recipes-security/libseccomp/files/0001-tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch b/recipes-security/libseccomp/files/0001-tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch
deleted file mode 100644
index a53433f..0000000
--- a/recipes-security/libseccomp/files/0001-tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch
+++ /dev/null
@@ -1,45 +0,0 @@
-From 1ecdddb2a5b61cf527d1f238f88a9d129239f87a Mon Sep 17 00:00:00 2001
-From: Paul Moore <paul@...>
-Date: Tue, 5 Nov 2019 15:11:11 -0500
-Subject: [PATCH] tests: rely on __SNR_xxx instead of __NR_xxx for syscalls
-
-We recently changed how libseccomp handles syscall numbers that are
-not defined natively, but we missed test #15.
-
-Acked-by: Tom Hromatka <tom.hromatka@...>
-Signed-off-by: Paul Moore <paul@...>
-
-Upstream-Status: Backport
-[https://github.com/seccomp/libseccomp/commit/1ecdddb2a5b61cf527d1f238f88a9d129239f87a]
-
-Signed-off-by: Yi Zhao <yi.zhao@...>
----
- tests/15-basic-resolver.c | 6 +++---
- 1 file changed, 3 insertions(+), 3 deletions(-)
-
-diff --git a/tests/15-basic-resolver.c b/tests/15-basic-resolver.c
-index 6badef1..0c1eefe 100644
---- a/tests/15-basic-resolver.c
-+++ b/tests/15-basic-resolver.c
-@@ -55,15 +55,15 @@ int main(int argc, char *argv[])
- unsigned int arch;
- char *name = NULL;
-
-- if (seccomp_syscall_resolve_name("open") != __NR_open)
-+ if (seccomp_syscall_resolve_name("open") != __SNR_open)
- goto fail;
-- if (seccomp_syscall_resolve_name("read") != __NR_read)
-+ if (seccomp_syscall_resolve_name("read") != __SNR_read)
- goto fail;
- if (seccomp_syscall_resolve_name("INVALID") != __NR_SCMP_ERROR)
- goto fail;
-
- rc = seccomp_syscall_resolve_name_rewrite(SCMP_ARCH_NATIVE, "openat");
-- if (rc != __NR_openat)
-+ if (rc != __SNR_openat)
- goto fail;
-
- while ((arch = arch_list[iter++]) != -1) {
---
-2.17.1
-
diff --git a/recipes-security/libseccomp/libseccomp_2.4.2.bb b/recipes-security/libseccomp/libseccomp_2.4.3.bb
similarity index 90%
rename from recipes-security/libseccomp/libseccomp_2.4.2.bb
rename to recipes-security/libseccomp/libseccomp_2.4.3.bb
index 07db82a..9ca41e6 100644
--- a/recipes-security/libseccomp/libseccomp_2.4.2.bb
+++ b/recipes-security/libseccomp/libseccomp_2.4.3.bb
@@ -4,10 +4,9 @@ SECTION = "security"
LICENSE = "LGPL-2.1"
LIC_FILES_CHKSUM = "file://LICENSE;beginline=0;endline=1;md5=8eac08d22113880357ceb8e7c37f989f"

-SRCREV = "1b6cfd1fc0b7499a28c24299a93a80bd18619563"
+SRCREV = "1dde9d94e0848e12da20602ca38032b91d521427"

SRC_URI = "git://github.com/seccomp/libseccomp.git;branch=release-2.4 \
- file://0001-tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch \
file://run-ptest \
"

--
2.17.1

On Sat, Mar 07, 2020 at 08:38:49PM +0000, akuster wrote:

dropped patch now included in update

Do you want to remove the patch?

yeah.. I should.

v2 shortly

thanks,
Armin

Signed-off-by: Armin Kuster <akuster808@...>
---
 .../libseccomp/{libseccomp_2.4.2.bb => libseccomp_2.4.3.bb}    | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
 rename recipes-security/libseccomp/{libseccomp_2.4.2.bb => libseccomp_2.4.3.bb} (90%)

diff --git a/recipes-security/libseccomp/libseccomp_2.4.2.bb b/recipes-security/libseccomp/libseccomp_2.4.3.bb
similarity index 90%
rename from recipes-security/libseccomp/libseccomp_2.4.2.bb
rename to recipes-security/libseccomp/libseccomp_2.4.3.bb
index 07db82a..9ca41e6 100644
--- a/recipes-security/libseccomp/libseccomp_2.4.2.bb
+++ b/recipes-security/libseccomp/libseccomp_2.4.3.bb
@@ -4,10 +4,9 @@ SECTION = "security"
 LICENSE = "LGPL-2.1"
 LIC_FILES_CHKSUM = "file://LICENSE;beginline=0;endline=1;md5=8eac08d22113880357ceb8e7c37f989f"
 
-SRCREV = "1b6cfd1fc0b7499a28c24299a93a80bd18619563"
+SRCREV = "1dde9d94e0848e12da20602ca38032b91d521427"
 
 SRC_URI = "git://github.com/seccomp/libseccomp.git;branch=release-2.4 \
-           file://0001-tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch \
            file://run-ptest \
 "
 
-- 
2.17.1

On Sat, Mar 07, 2020 at 08:38:49PM +0000, akuster wrote:

dropped patch now included in update

Do you want to remove the patch?

Signed-off-by: Armin Kuster <akuster808@...>
---
.../libseccomp/{libseccomp_2.4.2.bb => libseccomp_2.4.3.bb} | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
rename recipes-security/libseccomp/{libseccomp_2.4.2.bb => libseccomp_2.4.3.bb} (90%)

diff --git a/recipes-security/libseccomp/libseccomp_2.4.2.bb b/recipes-security/libseccomp/libseccomp_2.4.3.bb
similarity index 90%
rename from recipes-security/libseccomp/libseccomp_2.4.2.bb
rename to recipes-security/libseccomp/libseccomp_2.4.3.bb
index 07db82a..9ca41e6 100644
--- a/recipes-security/libseccomp/libseccomp_2.4.2.bb
+++ b/recipes-security/libseccomp/libseccomp_2.4.3.bb
@@ -4,10 +4,9 @@ SECTION = "security"
LICENSE = "LGPL-2.1"
LIC_FILES_CHKSUM = "file://LICENSE;beginline=0;endline=1;md5=8eac08d22113880357ceb8e7c37f989f"

-SRCREV = "1b6cfd1fc0b7499a28c24299a93a80bd18619563"
+SRCREV = "1dde9d94e0848e12da20602ca38032b91d521427"

SRC_URI = "git://github.com/seccomp/libseccomp.git;branch=release-2.4 \
- file://0001-tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch \
file://run-ptest \
"

--
2.17.1

Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-security/sssd/sssd_1.16.4.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-security/sssd/sssd_1.16.4.bb b/recipes-security/sssd/sssd_1.16.4.bb
index d42a455..c5ddd5c 100644
--- a/recipes-security/sssd/sssd_1.16.4.bb
+++ b/recipes-security/sssd/sssd_1.16.4.bb
@@ -41,7 +41,6 @@ PACKAGECONFIG[ssh] = "--with-ssh, --with-ssh=no, "
PACKAGECONFIG[samba] = "--with-samba, --with-samba=no, samba"
PACKAGECONFIG[selinux] = "--with-selinux, --with-selinux=no --with-semanage=no, libselinux"
PACKAGECONFIG[manpages] = "--with-manpages, --with-manpages=no"
-PACKAGECONFIG[python2] = "--with-python2-bindings, --without-python2-bindings, python, python"
PACKAGECONFIG[python3] = "--with-python3-bindings, --without-python3-bindings"
PACKAGECONFIG[nss] = "--with-crypto=nss, ,nss,"
PACKAGECONFIG[crypto] = "--with-crypto=libcrypto, , libcrypto"
@@ -57,6 +56,7 @@ EXTRA_OECONF += " \
--without-ipa-getkeytab \
--without-python2-bindings \
--enable-pammoddir=${base_libdir}/security \
+ --without-python2-bindings \
"

do_configure_prepend() {
--
2.17.1