LUV support for HW with NVDIMM's( DCPMM - Apachepass)
by R, Dilip Kumar (FEL)
Hi All,
We are working on an OEM server platform that's getting enabled with Cascade lake processors and Apache pass DIMM's( NVDIMM's). When we attempt to run LUV, we hit the below failure
Can you please let us know if LUV has the required support?
FYI - SLES 15 and SLES SP3 kernels works OK on this platform. ( has ndctl lib version 60.1)
~~~~~
[ OK ] Stopped target Network is Online.
[ OK ] Stopped target Network.
[ OK ] Stopped target Host and Network Name Lookups.
Stopping Network Name Resolution...
[ OK ] Stopped target System Time Synchronized.
[ OK ] Stopped D-Bus System Message Bus.
[ 105.870503] systemd-network (5346) used greatest stack depth: 12208 bytes left
[ 155.514721] ACPI Error: Field [DATB] at bit offset/length 32/96 exceeds size of target Buffer (32 bits) (20180313/dsopcode-201)
[ 155.527741] ACPI Error: Method parse/execution failed \_SB.CRRD, AE_AML_BUFFER_LIMIT (20180313/psparse-516)
[ 155.538670] ACPI Error: Method parse/execution failed \_SB.NVDR._DSM, AE_AML_BUFFER_LIMIT (20180313/psparse-516)
[ 155.550079] ACPI: \_SB_.NVDR: failed to evaluate _DSM (0x300a)
[ 155.585321] systemd-udevd (5693) used greatest stack depth: 10864 bytes left
[ 155.921343] i40e 0000:c3:00.3: Failed to update MAC address registers; cannot enable Multicast Magic packet wake up
[ 156.699313] i40e 0000:c3:00.2: Failed to update MAC address registers; cannot enable Multicast Magic packet wake up
[ 157.472201] i40e 0000:c3:00.1: Failed to update MAC address registers; cannot enable Multicast Magic packet wake up
[ 158.221662] i40e 0000:c3:00.0: Failed to update MAC address registers; cannot enable Multicast Magic packet wake up
[ 158.823546] sd 5:0:0:0: [sda] Synchronizing SCSI cache
[ 158.829781] sd 5:0:0:0: [sda] Stopping disk
[ 158.955640] reboot: System halted
Regards,
Dilip
3 years, 2 months
[PATCH v2 0/2] chipsec: Updates for LUV v2.3
by Ricardo Neri
Hi Megha,
Please find these two patches needed to have CHIPSEC working on top
of commit 1597a0a47da4("luv-image: Add hddimg to IMAGE_FSTYPES"), in the
current next branch.
The first patch deals with a build break as a result of recent updates
to Poky; all the details are described in the patch.
The second patch is a trivial one that simply removes dead code.
I tested these patches on my end and CHIPSEC runs correctly.
Changes since v1:
* The previous submission did not update all the file paths that were
impacted by the aforementioned patch in poky. I corrected this. Hence,
only patch 1 chaged, patch 2 remains the same. I am submitting the
whole series for clarity.
Thanks and BR,
Ricardo
Ricardo Neri (2):
chipsec: do not correct the installation path
chipsec: remove unneeded text stream edition
meta-luv/recipes-core/chipsec/chipsec_git.bb | 23 +++-----------------
1 file changed, 3 insertions(+), 20 deletions(-)
--
2.17.1
3 years, 3 months
[PATCH 0/2] chipsec: Updates for LUV v2.3
by Ricardo Neri
Hi Megha,
Please find these two patches needed to have CHIPSEC working on top
of your mdey/for_luv_v2.3.
The first patch deals with a build break as a result of recent updates
to Poky; all the details are described in the patch.
The second patch is a trivial one that simply removes dead code.
I tested these patches on my end and CHIPSEC runs correctly.
Thanks and BR,
Ricardo
Ricardo Neri (2):
chipsec: do not correct the installation path
chipsec: remove unneeded text stream edition
meta-luv/recipes-core/chipsec/chipsec_git.bb | 19 +------------------
1 file changed, 1 insertion(+), 18 deletions(-)
--
2.17.1
3 years, 4 months
[PATCH V2] luv-image: Add hddimg to IMAGE_FSTYPES
by Megha Dey
>From yocto project commit :
commit 83d791089fb220553d4df144f56ebea61d9e0713
Author: Richard Purdie <richard.purdie(a)linuxfoundation.org>
Date: Mon Jun 18 11:04:59 2018 +0000
image/image-live: Improve handling of live/iso/hddimg types (drop
NOISO/NOHDD)
the NOHDD and NOISO variables have been dropped and now to create an HDD
image, the IMAGE_FSTYPES variable should contain live or hddimg. Since
luv-image(both luv-live-image as well as luv-netboot-image) should create
an hdd image, we need to add 'hddimg' to the IMAGE_FSTYPES variable.
Changes V1->V2:
Moved the change to luv-image.inc from luv-live-image.bb as this change
is valid even for luv-netboot-image.
Signed-off-by: Megha Dey <megha.dey(a)linux.intel.com>
---
meta-luv/recipes-core/images/luv-image.inc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta-luv/recipes-core/images/luv-image.inc b/meta-luv/recipes-core/images/luv-image.inc
index def2344..adf0984 100644
--- a/meta-luv/recipes-core/images/luv-image.inc
+++ b/meta-luv/recipes-core/images/luv-image.inc
@@ -9,6 +9,8 @@ HDDDIR = "${S}/hddimg"
INITRD_IMAGE_LIVE = "core-image-efi-initramfs"
IMGDEPLOYDIR = "${DEPLOY_DIR_IMAGE}"
+IMAGE_FSTYPES+="hddimg"
+
# Tell plymouth to ignore serial consoles and limit the amount of systemD logs.
CMDLINE_USERSPACE = "systemd.log_target=null plymouth.ignore-serial-consoles"
--
1.9.1
3 years, 4 months
[PATCH V2] sbsigntool: use mainline git repo
by Megha Dey
Until now, we were using a fork of sbsigntool git repo. This was based
on a older version of sbsigntool mainline repo. It is better for
us to switch to the mainline repo so that it uses updated dependencies.
For example, the older sbsigntool was compatible with openssl10 and not
the newer openssh1.1.
We have to accordingly rebase the patch files associated with this
recipe.
Changes V1->V2:
Update the sbsigntool repo instead of updating dependencies of the older
sbsigntool repo.
Signed-off-by: Megha Dey <megha.dey(a)linux.intel.com>
---
.../sbsigntool/0001-configure-fix-cross-compilation.patch | 15 ++++++++-------
meta-luv/recipes-devtools/sbsigntool/sbsigntool_git.bb | 7 ++++---
2 files changed, 12 insertions(+), 10 deletions(-)
diff --git a/meta-luv/recipes-devtools/sbsigntool/sbsigntool/0001-configure-fix-cross-compilation.patch b/meta-luv/recipes-devtools/sbsigntool/sbsigntool/0001-configure-fix-cross-compilation.patch
index 4564a8d..77e96be 100644
--- a/meta-luv/recipes-devtools/sbsigntool/sbsigntool/0001-configure-fix-cross-compilation.patch
+++ b/meta-luv/recipes-devtools/sbsigntool/sbsigntool/0001-configure-fix-cross-compilation.patch
@@ -1,6 +1,6 @@
-From 763589e15cc7c7acca7372d1f0c645605a240b9b Mon Sep 17 00:00:00 2001
-From: Ricardo Neri <ricardo.neri-calderon(a)linux.intel.com>
-Date: Wed, 5 Aug 2015 10:17:57 -0700
+From 171892a8d92e72515e82751a44b11c3ead4df07a Mon Sep 17 00:00:00 2001
+From: Megha Dey <megha.dey(a)linux.intel.com>
+Date: Thu, 13 Sep 2018 16:13:12 -0700
Subject: [PATCH] configure: Prevent unsafe cross-compilation
When cross-compiling, directories from the host machine are included in
@@ -23,18 +23,19 @@ as described in the gcc documentation.
Upstream status: applicable only to LUV.
Signed-off-by: Ricardo Neri <ricardo.neri-calderon(a)linux.intel.com>
+Signed-off-by: Megha Dey <megha.dey(a)linux.intel.com>
---
configure.ac | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
-index 0d8f0bb..6c6fb0b 100644
+index bce6f0e..7115553 100644
--- a/configure.ac
+++ b/configure.ac
-@@ -65,7 +65,7 @@ PKG_CHECK_MODULES(uuid, uuid,
+@@ -79,7 +79,7 @@ if test -z "$CRTPATH"; then
+ AC_MSG_ERROR([cannot find the gnu-efi crt path])
+ fi
- dnl gnu-efi headers require extra include dirs
- EFI_ARCH=$(uname -m)
-EFI_CPPFLAGS="-I/usr/include/efi -I/usr/include/efi/$EFI_ARCH \
+EFI_CPPFLAGS="-I=/usr/include/efi -I=/usr/include/efi/$EFI_ARCH \
-DEFI_FUNCTION_WRAPPER"
diff --git a/meta-luv/recipes-devtools/sbsigntool/sbsigntool_git.bb b/meta-luv/recipes-devtools/sbsigntool/sbsigntool_git.bb
index 69f050b..45a699e 100644
--- a/meta-luv/recipes-devtools/sbsigntool/sbsigntool_git.bb
+++ b/meta-luv/recipes-devtools/sbsigntool/sbsigntool_git.bb
@@ -3,13 +3,14 @@ SUMMARY = "Signing utility for UEFI secure boot"
LICENSE = "GPLv3"
LIC_FILES_CHKSUM = "file://LICENSE.GPLv3;md5=9eef91148a9b14ec7f9df333daebc746"
-SRC_URI = "gitsm://kernel.ubuntu.com/jk/sbsigntool;protocol=git \
+SRC_URI = "gitsm://git.kernel.org/pub/scm/linux/kernel/git/jejb/sbsigntools.git;prot... \
file://fix-mixed-implicit-and-normal-rules.patch;apply=1 \
file://disable-man-page-creation.patch \
file://0001-configure-fix-cross-compilation.patch \
"
-SRCREV="${AUTOREV}"
+SRCREV="a631793f2d02ef219b5348eab0ac2ae604ed1269"
+PV = "v0.9.1+git${SRCPV}"
inherit autotools-brokensep pkgconfig
@@ -26,7 +27,7 @@ do_configure() {
export CC="${BUILD_CC}"
lib/ccan.git/tools/create-ccan-tree \
--build-type=automake lib/ccan \
- talloc read_write_all build_assert array_size
+ endian talloc read_write_all build_assert array_size
fi
export CC="${OLD_CC}"
--
1.9.1
3 years, 4 months
[PATCH V2] linux-luv: Remove kernel-sample.scc from KERNEL_FEATURES
by Megha Dey
The Yocto Project commit
commit 28a1f5cd95cfd6888db969485a6164ae98ef7aa0
Author: Hongzhi.Song <hongzhi.song(a)windriver.com>
Date: Fri Jun 29 02:16:19 2018 -0400
linux-yocto: Enable kernel-sample features for runtime tests
Enable kernel-sample features by default with the machine of qemu.
made KERNEL_FEATURES include kernel-sample.scc. The Yocto Project kernel
uses metadata for kernel configuration. LUV kernel does not use this
metadata because we rely on our own configuration fragments. Thus, we
need to remove the kernel-sample.scc metadata file.
Changes V1->V2:
Merged this change into a single KERNEL_FEATURES_remove to be inline with the
general style of recipes in poky.
Signed-off-by: Megha Dey <megha.dey(a)linux.intel.com>
---
meta-luv/recipes-kernel/linux/linux-luv_4.18.bb | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta-luv/recipes-kernel/linux/linux-luv_4.18.bb b/meta-luv/recipes-kernel/linux/linux-luv_4.18.bb
index 57e9f35..093604f 100644
--- a/meta-luv/recipes-kernel/linux/linux-luv_4.18.bb
+++ b/meta-luv/recipes-kernel/linux/linux-luv_4.18.bb
@@ -55,7 +55,9 @@ KBRANCH="master"
inherit kernel
require recipes-kernel/linux/linux-yocto.inc
-KERNEL_FEATURES_remove= " features/debug/printk.scc"
+KERNEL_FEATURES_remove= " features/debug/printk.scc \
+ features/kernel-sample/kernel-sample.scc \
+ "
# Override SRC_URI in a bbappend file to point at a different source
# tree if you do not want to build from Linus' tree.
--
1.9.1
3 years, 4 months
[PATCH V2] bits: Add bison-native dependency
by Megha Dey
While building bits, the following error was observed:
| checking for bison... no
| configure: error: bison is not found
| make: *** [build-grub-x86_64-efi] Error 1
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile
We already have a dependency on bison, but needed to added a dependency
on bison-native instead.
Changes V1->V2
Add the error message which prompted this change in the commit message
Signed-off-by: Megha Dey <megha.dey(a)linux.intel.com>
---
meta-luv/recipes-bsp/bits/bits_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-luv/recipes-bsp/bits/bits_git.bb b/meta-luv/recipes-bsp/bits/bits_git.bb
index 03627c9..c0a69da 100644
--- a/meta-luv/recipes-bsp/bits/bits_git.bb
+++ b/meta-luv/recipes-bsp/bits/bits_git.bb
@@ -76,7 +76,7 @@ SRC_URI = "gitsm://github.com/biosbits/bits.git;protocol=http \
S = "${WORKDIR}/git"
DEPENDS = "virtual/gettext autogen-native gettext-native sqlite3-native zip-native \
- xorriso-native bits-native flex bison autogen-native"
+ xorriso-native bits-native flex bison-native autogen-native"
RDEPENDS_${PN}_class-target = "coreutils findutils cpio"
COMPATIBLE_HOST = '(x86_64.*|i.86.*)-(linux|freebsd.*)'
--
1.9.1
3 years, 4 months
[PATCH V2] bits: Do not treat warnings as errors.
by Megha Dey
By default, CFLAGS has a -Werror which ensures all warnings are trated
as errors. After updating LUV with the latest poky, we are using GCC 8
which introduces many new warnings which are all treated as error. Since
BITS has a dependency on grub and python and no one is actively
maintaining it, resolving all these warnings consumes a lot of time.
Thus, we have decided to not treat the warnings as errors.
Changes V1->V2:
Added a comment for this change in the bits recipe.
Signed-off-by: Megha Dey <megha.dey(a)linux.intel.com>
---
meta-luv/recipes-bsp/bits/bits_git.bb | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/meta-luv/recipes-bsp/bits/bits_git.bb b/meta-luv/recipes-bsp/bits/bits_git.bb
index d77811f..03627c9 100644
--- a/meta-luv/recipes-bsp/bits/bits_git.bb
+++ b/meta-luv/recipes-bsp/bits/bits_git.bb
@@ -16,6 +16,12 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=71a9ec458a3c65c2bfb461b227ef3049"
BBCLASSEXTEND = "native"
+# CFLAGS has a -Werror which ensures all warnings are treated as errors.
+# Since BITS has a dependency on grub and python and no one is actively
+# maintaining it, resolving all these warnings consumes a lot of time.
+# Thus, we have decided to not treat the warnings as errors.
+CFLAGS_append = " -Wno-error "
+
BITSVERSION="2079"
PV="${BITSVERSION}+git${SRCPV}"
--
1.9.1
3 years, 4 months
[PATCH] chipsec: Install chipsec in correct location.
by Megha Dey
After updating to the latest poky and to chipsec v1.3.6rc1, chipsec
gets installed under a different directory compared to earlier. Hence
this needs to be updated.
Signed-off-by: Megha Dey <megha.dey(a)linux.intel.com>
---
meta-luv/recipes-core/chipsec/chipsec_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-luv/recipes-core/chipsec/chipsec_git.bb b/meta-luv/recipes-core/chipsec/chipsec_git.bb
index 872cb31..1a4c9a1 100644
--- a/meta-luv/recipes-core/chipsec/chipsec_git.bb
+++ b/meta-luv/recipes-core/chipsec/chipsec_git.bb
@@ -81,7 +81,7 @@ do_install_append() {
#
install -d ${D}${PYTHON_SITEPACKAGES_DIR}/${PN}
- mv ${D}${PYTHON_SITEPACKAGES_DIR}${D}${PYTHON_SITEPACKAGES_DIR}/* ${D}${PYTHON_SITEPACKAGES_DIR}/${PN}
+ mv ${D}${PYTHON_SITEPACKAGES_DIR}${RECIPE_SYSROOT_NATIVE}${PYTHON_SITEPACKAGES_DIR}/* ${D}${PYTHON_SITEPACKAGES_DIR}/${PN}
# remove old files
cd ${D}${PYTHON_SITEPACKAGES_DIR}
ls | grep -v chipsec | xargs rm -fr
--
1.9.1
3 years, 4 months
[PATCH] bits: Do not treat warnings as errors.
by Megha Dey
By default, CFLAGS has a -Werror which ensures all warnings are treated
as errors. After updating LUV with the latest poky, we are using GCC 8
which introduces many new warnings which are all treated as errors. Since
BITS has a dependency on grub and python and no one is actively
maintaining it, resolving all these warnings consumes a lot of time.
Thus, we have decided to not treat the warnings as errors.
Signed-off-by: Megha Dey <megha.dey(a)linux.intel.com>
---
meta-luv/recipes-bsp/bits/bits_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-luv/recipes-bsp/bits/bits_git.bb b/meta-luv/recipes-bsp/bits/bits_git.bb
index d77811f..5f3caca 100644
--- a/meta-luv/recipes-bsp/bits/bits_git.bb
+++ b/meta-luv/recipes-bsp/bits/bits_git.bb
@@ -15,7 +15,7 @@ LICENSE = "GPLv3"
LIC_FILES_CHKSUM = "file://COPYING;md5=71a9ec458a3c65c2bfb461b227ef3049"
BBCLASSEXTEND = "native"
-
+CFLAGS_append = " -Wno-error "
BITSVERSION="2079"
PV="${BITSVERSION}+git${SRCPV}"
--
1.9.1
3 years, 4 months
