[linux-yocto] v4.18.x - stable updates comprising v4.18.30

[Paul Gortmaker]

Bruce, Yocto kernel folks:

Here is the next 4.18.x stable update "extension" primarily created
for the Yocto project, continuing from the previous v4.18.29 release.

There are about 245 commits here, based on commits chosen from what
were used in the existing 4.19.22 --> 4.19.26 stable releases.

The largest group of related commits in this series are 32 bit ARM
spectre related changes.  With some low level assembly changes involved,
I used the the 4.19-stable versions instead of directly backporting from
mainline like I normally do for everything else -- to capitalize on the
runtime testing and non-straightforward backports done by others with
more ARM32 experience.

I've put this 4.18.x queue through the usual testing; build testing
on x86-64/32, ARM-64/32, PPC and MIPS, plus some static analysis
and finally some sanity runtime tests on x86-64.

I did the signed tag just as per the previously released versions.
Please find a signed v4.18.30 tag using this key:

http://pgp.mit.edu/pks/lookup?op=vindex=0xEBCE84042C07D1D6

in the repo in the kernel.org directory here:

   https://git.kernel.org/cgit/linux/kernel/git/paulg/linux-4.18.y.git/
   git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-4.18.y.git

for merge to standard/base in linux-yocto-4.18 and then out from there
into the other base and BSP branches.

For those who are interested, the evolution of the commits is here:

   https://git.kernel.org/cgit/linux/kernel/git/paulg/longterm-queue-4.18.git/

This repo isn't needed for anything; it just exists for transparency and
so people can see the evolution of the raw commits that were originally
selected to create this 4.18.x release.

Paul.
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [yocto] devtmpfs failing to mount

[Loïc Domaigné]

> > > I'm using Yocto version rocko with a custom layer to run on the Zynq+ SoC
> > > on a custom board. When trying to boot I'm getting the following error in
> > > the boot output:
> > > ...
> > > [4.127997] EXT4-fs (mmcblk0p2): couldn't mount as ext3 due to feature
> > > incompatibilities
> > > [4.183737] EXT4-fs (mmcblk0p2): recovery complete
> > > [4.190840] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data
> > > mode. Opts: (null)
> > > [4.198870] VFS: Mounted root (ext4 filesystem) on device 179:2.
> > > [4.205861] devtmpfs: error mounting -2
> > >
> > > Are there common reasons for this happening I should check?
> >
> > Not sure if that helps, but I'd check:
> > a) What's the type of the mmcblk0p2 (=rootfs?) partition?  and
> > b) How is this partition mounted?

> Yes those are both useful things to know. I am booting by flashing an SD
> card with a wic image (made using sdimage-bootpart.wks), so the flashing
> process takes care of creating the partitions. So the partition should be
> of type EXT4. The mounting process is actually what I'm a little fuzzy on
> in the first place.

I am not familiar with the meta-xilinx layer yet.
From what I can read/understand:
- is mmcblk0p2 the rootfs? 
  If so: this partition should get mounted at kernel boot using the
  "root=..." boot arg. This, in turn, is set by "Das uboot" bootloader.
  I guess all the glory details can be found in the
  u-boot-zynq-uenv.bb recipe or similar. 
- if mmcblk0p2 is not the rootfs, this must be mounted somewhere. A 
  casual place to look at would be /etc/fstab. 

Is there a /etc/fstab available on your system?

Cordialement,
Loïc
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] devtmpfs failing to mount

[Emily S]

Hello!

Yes those are both useful things to know. I am booting by flashing an SD
card with a wic image (made using sdimage-bootpart.wks), so the flashing
process takes care of creating the partitions. So the partition should be
of type EXT4. The mounting process is actually what I'm a little fuzzy on
in the first place. In October I had no issues with a mounting error for
devtmpfs, and I've made few changes since, however I can't seem to shake
this error, even when checking out older versions of the yocto
repositories. The mounting process should be mostly taken from the
meta-xilinx repository.

Thanks,
Emily

On Mon, Mar 11, 2019 at 3:16 PM Loïc Domaigné  wrote:

> Bonsoir Emily,
>
> > I'm using Yocto version rocko with a custom layer to run on the Zynq+ SoC
> > on a custom board. When trying to boot I'm getting the following error in
> > the boot output:
> > ...
> > [4.127997] EXT4-fs (mmcblk0p2): couldn't mount as ext3 due to feature
> > incompatibilities
> > [4.183737] EXT4-fs (mmcblk0p2): recovery complete
> > [4.190840] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data
> > mode. Opts: (null)
> > [4.198870] VFS: Mounted root (ext4 filesystem) on device 179:2.
> > [4.205861] devtmpfs: error mounting -2
> >
> > Are there common reasons for this happening I should check?
>
> Not sure if that helps, but I'd check:
> a) What's the type of the mmcblk0p2 (=rootfs?) partition?  and
> b) How is this partition mounted?
>
> Cheers!
> Loïc
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [go] Any meta layers for InfluxDB, Telegraf, Kapacitor

[Shantanoo Desai]

Hello,

 

I have been using InfluxDB older version on an Embedded Board through Yocto
and was wondering if there is already someone on the list using the above
mentioned Stacks:

Telegraf, InfluxDB, Kapacitor

 

If not can someone guide me how to actually get them into recipes for them?
Not sure how go works when using with devtool

 

Thanks.

 

Shan

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

Re: [yocto] devtmpfs failing to mount

[Loïc Domaigné]

Bonsoir Emily,

> I'm using Yocto version rocko with a custom layer to run on the Zynq+ SoC
> on a custom board. When trying to boot I'm getting the following error in
> the boot output:
> ... 
> [4.127997] EXT4-fs (mmcblk0p2): couldn't mount as ext3 due to feature
> incompatibilities
> [4.183737] EXT4-fs (mmcblk0p2): recovery complete
> [4.190840] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data
> mode. Opts: (null)
> [4.198870] VFS: Mounted root (ext4 filesystem) on device 179:2.
> [4.205861] devtmpfs: error mounting -2
> 
> Are there common reasons for this happening I should check?

Not sure if that helps, but I'd check:
a) What's the type of the mmcblk0p2 (=rootfs?) partition?  and
b) How is this partition mounted?

Cheers!
Loïc
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 295 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7"
and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(stephen.k.jol...@intel.com  ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

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

[yocto] devtmpfs failing to mount

[Emily S]

Hi all -

I'm using Yocto version rocko with a custom layer to run on the Zynq+ SoC
on a custom board. When trying to boot I'm getting the following error in
the boot output:
[4.205861] devtmpfs: error mounting -2

dmesg | tail shows a similar result:

[4.127997] EXT4-fs (mmcblk0p2): couldn't mount as ext3 due to feature
incompatibilities
[4.183737] EXT4-fs (mmcblk0p2): recovery complete
[4.190840] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data
mode. Opts: (null)
[4.198870] VFS: Mounted root (ext4 filesystem) on device 179:2.
[4.205861] devtmpfs: error mounting -2

Are there common reasons for this happening I should check? I'm having
trouble isolating a cause. The only change I made was including an
additional python library in one of my recipes, which I will try rolling
back next.
Any ideas are greatly appreciated!

Thanks,
Emily
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] PREFERRED_VERSION ignored

[Mark Hatle]

On 3/11/19 12:46 PM, Marco wrote:
> Hello,
> using Yocto version 'rocko' I have a custom layer defining a new
> recipe and a distro.
> I have a recipe openssl_1.0.1u.bb in my meta-custom layer.
> My meta-custom layer.conf has BBFILE_PRIORITY_meta-custom = "9"
> 
> In my meta-custom layer I have a distro configuration saying
> PREFERRED_VERSION_openssl = "1.0.2o" so I expected to build 1.0.2o but
> when I build bitbake openssl is always selected the 1.0.1u
> 
> Same problem if I set PREFERRED_VERSION_openssl = "1.0.2o" in the local.conf
> 
> Is there an issue or am I doing something wrong?

I've seen this issue before.  There are issues with layer priority as well as
recipe priority.  The only way I've dealt with this is by blacklisting specific
versions of recipes...

PNBLACKLIST[] ?= "${@'Only version ' +
d.getVar('PREFERRED_VERSION_${BPN}') + ' (not ${PV}) is supported in this
configuration. ' if d.getVar('PREFERRED_VERSION_${BPN}') and not
d.getVar('PV').startswith(d.getVar('PREFERRED_VERSION_${BPN}').replace('%', ''))
else ''}"

(note the above is one single line)

--Mark

> --
> Marco
> 

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

[yocto] PREFERRED_VERSION ignored

[Marco]

Hello,
using Yocto version 'rocko' I have a custom layer defining a new
recipe and a distro.
I have a recipe openssl_1.0.1u.bb in my meta-custom layer.
My meta-custom layer.conf has BBFILE_PRIORITY_meta-custom = "9"

In my meta-custom layer I have a distro configuration saying
PREFERRED_VERSION_openssl = "1.0.2o" so I expected to build 1.0.2o but
when I build bitbake openssl is always selected the 1.0.1u

Same problem if I set PREFERRED_VERSION_openssl = "1.0.2o" in the local.conf

Is there an issue or am I doing something wrong?

--
Marco
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Guidance to start yocto project.

[Scott Rifenbark]

H Rahul,

I would start with the
https://www.yoctoproject.org/docs/2.6.1/brief-yoctoprojectqs/brief-yoctoprojectqs.html
manual.  Gets you up and running.

Scott

On Mon, Mar 11, 2019 at 9:32 AM rahul chauhan 
wrote:

> Hello,
>
> I am beginner with yocto project and i want to learn the yocto project and
> start working on it.
> can you please guide how can i proceed step by step and  what are the
> prerequisites?
>
> Thanks and Regards
> Rahul Chauhan
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Guidance to start yocto project.

[Paul Barker]

On Mon, 11 Mar 2019, at 15:32, rahul chauhan wrote:
> Hello,
> 
> I am beginner with yocto project and i want to learn the yocto project 
> and start working on it. 
>  can you please guide how can i proceed step by step and what are the 
> prerequisites? 

There's an excellent "Quick Build" guide in the documentation: 
https://www.yoctoproject.org/docs/

Beyond that I can highly recommend reading "Embedded Linux Systems with the 
Yocto Project" by Rudolf Streif.

> 
> Thanks and Regards
> Rahul Chauhan
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

-- 
Paul Barker
Managing Director & Principal Engineer
Beta Five Ltd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [yocto-doc][PATCH] ref-manual: fix copy-paste style error (`SRC_URI`)

[Filip Jareš]

The update fixes a copy-paste-and-forget-to-update-everything error
in the documentation of the `SRC_URI` entry in the Reference Manual.
The `maxdate` paragraph just repeated what is there for the
neighboring `mindate` paragraph which was incorrect.

What is documented (and patched) here is implemented in the
`should_apply` function in `meta/lib/oe/patch.py`.

Signed-off-by: Filip Jareš 
---
 documentation/ref-manual/ref-variables.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/ref-manual/ref-variables.xml 
b/documentation/ref-manual/ref-variables.xml
index 3ffa92c..b49fb25 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -13798,7 +13798,7 @@
 
 maxdate 
-
 Apply the patch only if 
SRCDATE
-is not later than mindate.
+is not later than maxdate.
 
 minrev 
-
 Apply the patch only if SRCREV
-- 
2.7.4

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

[yocto] Guidance to start yocto project.

[rahul chauhan]

Hello,

I am beginner with yocto project and i want to learn the yocto project and
start working on it.
can you please guide how can i proceed step by step and  what are the
prerequisites?

Thanks and Regards
Rahul Chauhan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Resizing extended partition in image created with wic (poky sumo)

[Smith, Peter1 (GE Renewable Energy)]

I am having trouble with resizing a partition inside of an extended partition 
in an image created using wic (poky sumo).

Here is the .wks file I have used:

part /mnt/boot --source bootimg-partition --ondisk mmcblk0 --label edgeos-boot 
--active --align 4096 --fixed-size=100M --fstype=msdos --use-uuid
part / --source rootfs --rootfs-dir=sdcard-image --ondisk mmcblk0 --use-uuid 
--uuid=EA2EEE0B-5C82-4817-8439-1202B5E5651A --fstype=ext3 --label edgeos-root 
--align 4096 --fixed-size 1G
part /mnt/rootfs2 --ondisk mmcblk0 --use-uuid 
--uuid=EA2EEE0B-5C82-4817-8439-1202B5E5651B --fstype=ext3 --label rootfs2 
--align 4096 --fixed-size 1G
part /mnt/conf --ondisk mmcblk0 --use-uuid --fstype=ext3 --label edgeos-conf 
--align 4096 --fixed-size 20M
part /mnt/data --ondisk mmcblk0 --use-uuid --fstype=ext3 --label edgeos-data 
--align 4096 --fixed-size 2947M
bootloader --ptable msdos

...and here is what parted thinks about the content of the image:

Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start EndSize  Type  File system  Flags
1  8192s 212991s204800s   primary   fat16boot
2  212992s   2310143s   2097152s  primary   ext3
3  2310144s  4407295s   2097152s  primary   ext3
4  4415487s  10500095s  6084609s  extended   lba
5  4415488s  4456447s   40960slogical   ext3
6  4464640s  10500095s  6035456s  logical   ext3

When I try and resize the extended partition to the end of the disk (it's a 
16GB SDCARD) with the following command I get an error

parted /dev/... resizepart 4 -1s
bash[177]: Expand extended partition(4)... Error: Unable to satisfy all 
constraints on the partition.

I have searched the internet but can't seem to find any suggestions about what 
could be wrong, any ideas?

Best Regards Peter Smith
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH] suricata: update to 4.1.3

[Armin Kuster]

Signed-off-by: Armin Kuster 
---
 .../suricata/{libhtp_0.5.28.bb => libhtp_0.5.29.bb} | 0
 recipes-security/suricata/suricata.inc  | 6 +++---
 .../suricata/{suricata_4.0.6.bb => suricata_4.1.3.bb}   | 5 +++--
 3 files changed, 6 insertions(+), 5 deletions(-)
 rename recipes-security/suricata/{libhtp_0.5.28.bb => libhtp_0.5.29.bb} (100%)
 rename recipes-security/suricata/{suricata_4.0.6.bb => suricata_4.1.3.bb} (97%)

diff --git a/recipes-security/suricata/libhtp_0.5.28.bb 
b/recipes-security/suricata/libhtp_0.5.29.bb
similarity index 100%
rename from recipes-security/suricata/libhtp_0.5.28.bb
rename to recipes-security/suricata/libhtp_0.5.29.bb
diff --git a/recipes-security/suricata/suricata.inc 
b/recipes-security/suricata/suricata.inc
index 368b2e0..7be403c 100644
--- a/recipes-security/suricata/suricata.inc
+++ b/recipes-security/suricata/suricata.inc
@@ -2,8 +2,8 @@ HOMEPAGE = "http://suricata-ids.org/;
 SECTION = "security Monitor/Admin"
 LICENSE = "GPLv2"
 
-VER = "4.0.6"
+VER = "4.1.3"
 SRC_URI = 
"http://www.openinfosecfoundation.org/download/suricata-${VER}.tar.gz;
 
-SRC_URI[md5sum] = "e8e9a401fef3b3ca1027c268c38c8f4b"
-SRC_URI[sha256sum] = 
"cbab847b33fc625b7a92241fdce2e1ca47b8bb415c9114de70819394229679a4"
+SRC_URI[md5sum] = "35c4a8e6be3910831649a073950195df"
+SRC_URI[sha256sum] = 
"6cda6c80b753ce36483c6be535358b971f3890b9aa27a58c2d2f7e89dd6c6aa0"
diff --git a/recipes-security/suricata/suricata_4.0.6.bb 
b/recipes-security/suricata/suricata_4.1.3.bb
similarity index 97%
rename from recipes-security/suricata/suricata_4.0.6.bb
rename to recipes-security/suricata/suricata_4.1.3.bb
index 6c0a109..d6f5937 100644
--- a/recipes-security/suricata/suricata_4.0.6.bb
+++ b/recipes-security/suricata/suricata_4.1.3.bb
@@ -16,7 +16,7 @@ SRC_URI += " \
 SRC_URI[rules.md5sum] = "205c5e5b54e489207ed892c03ad75b33"
 SRC_URI[rules.sha256sum] = 
"4aa81011b246875a57181c6a0569ca887845e366904bcaf0043220f33bd69798"
 
-inherit autotools-brokensep pkgconfig python-dir systemd ptest
+inherit autotools-brokensep pkgconfig python3-dir systemd ptest
 
 CFLAGS += "-D_DEFAULT_SOURCE"
 
@@ -26,6 +26,7 @@ CACHED_CONFIGUREVARS = "ac_cv_header_htp_htp_h=yes 
ac_cv_lib_htp_htp_conn_create
 EXTRA_OECONF += " --disable-debug \
 --enable-non-bundled-htp \
 --disable-gccmarch-native \
+--disable-suricata-update \
 "
 
 PACKAGECONFIG ??= "htp jansson file pcre yaml pcap cap-ng net nfnetlink nss 
nspr"
@@ -44,7 +45,7 @@ PACKAGECONFIG[jansson] = 
"--with-libjansson-includes=${STAGING_INCDIR} --with-li
 PACKAGECONFIG[file] = ",,file, file"
 PACKAGECONFIG[nss] = "--with-libnss-includes=${STAGING_INCDIR} 
--with-libnss-libraries=${STAGING_LIBDIR}, nss, nss," 
 PACKAGECONFIG[nspr] = "--with-libnspr-includes=${STAGING_INCDIR} 
--with-libnspr-libraries=${STAGING_LIBDIR}, nspr, nspr," 
-PACKAGECONFIG[python] = "--enable-python, --disable-python, python, python" 
+PACKAGECONFIG[python] = "--enable-python, --disable-python, python3, python3" 
 PACKAGECONFIG[unittests] = "--enable-unittests, --disable-unittests," 
 
 export logdir = "${localstatedir}/log"
-- 
2.17.1

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