[PATCH V2 0/6] luv : Write messages to a console and/or debug file
by Megha Dey
Currently, we only use the plymouth graphical manager to display
certain messages to the user. Hence, someone with access to only
serial console or netconsole will not know what is going on. We
need to write these messages to a console and/or a debug file.
To ensure this, we:
1. Add a new script , luv_message, which contains the function
definitions of plymouth_write and plymouth_hide. Other luv scripts
can source this file to use these functions.
2. Update the standard output to /dev/ttyS0 for x86 and /dev/ttyAMA0
for ARM architectures
3. Do not redirect results to kmsg, instead use information
from /proc/uptime to provide us the timestamp for every test run.
4. Suppress unwanted messages from being displayed to the console and
avoid message being printed twice on the console.
This patch-set address:
https://github.com/01org/luv-yocto/issues/96
Changes V0->V1
1. Depending on the architecture, update the standard output to /dev/ttyS0
for x86 and /dev/ttyAMA0 for ARM respectively.
Changes V1->V2
1. Split 1 big patch into several smaller patches to increase modularity
2. Comment on the purpose of installing the luv-message file
3. Added a second parameter (number of seconds to display message) to
plymouth_write
Megha Dey (6):
luv-test: Move plymouth functions to new script
luv-test: update standard output for luv scripts
luv-test: Send messages to console and debug file
luv-test: Rename plymouth function names
luv-test-manager: Do not redirect results to kmsg
luv-test: Do not print unnecessary messages to console
meta-luv/recipes-core/luv-test/luv-test.bb | 24 ++++++++-
.../luv-test/luv-test/luv-crash-handler | 20 +++-----
.../luv-test/luv-test/luv-crash-handler.service | 2 +
.../luv-test/luv-test/luv-dmesg-acpi-tables-dump | 12 ++---
.../recipes-core/luv-test/luv-test/luv-message | 23 +++++++++
.../recipes-core/luv-test/luv-test/luv-netconsole | 22 +++-----
.../luv-test/luv-test/luv-netconsole.service | 2 +
.../luv-test/luv-test/luv-test-manager | 58 +++++++++-------------
.../luv-test/luv-test/luv-test-manager.service | 2 +
.../recipes-core/luv-test/luv-test/submit_results | 7 +--
10 files changed, 95 insertions(+), 77 deletions(-)
create mode 100755 meta-luv/recipes-core/luv-test/luv-test/luv-message
--
1.9.1
3 years, 11 months
[PATCH V0] linux-yocto-efi-test: Use custom LINUX_VERSION_EXTENSION
by Megha Dey
Poky has recently made the LINUX_VERSION_EXTENSION weaker in commit
9cc5cf0a64d("linux-yocto: Make LINUX_VERSION_EXTENSION weaker").
Use the custom LUV kernel extension in the LUV kernel recipe to remove
the actual nvdimm drivers and keep only the testing drivers.
Signed-off-by: Megha Dey <megha.dey(a)linux.intel.com>
---
meta-luv/recipes-kernel/linux/linux-yocto-efi-test_4.14.bb | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/meta-luv/recipes-kernel/linux/linux-yocto-efi-test_4.14.bb b/meta-luv/recipes-kernel/linux/linux-yocto-efi-test_4.14.bb
index faa9c6a..38d635e 100644
--- a/meta-luv/recipes-kernel/linux/linux-yocto-efi-test_4.14.bb
+++ b/meta-luv/recipes-kernel/linux/linux-yocto-efi-test_4.14.bb
@@ -124,8 +124,8 @@ KCONFIG_MODE = 'alldefconfig'
KBUILD_DEFCONFIG = "defconfig"
KBUILD_DEFCONFIG_x86 = "i386_defconfig"
KBUILD_DEFCONFIG_x86-64 = "x86_64_defconfig"
-LINUX_VERSION ?= "4.14"
-LINUX_VERSION_EXTENSION ?= "-efitest"
+LINUX_VERSION = "4.14"
+LINUX_VERSION_EXTENSION = "-efitest"
# Override SRCREV to point to a different commit in a bbappend file to
# build a different release of the Linux kernel.
@@ -143,8 +143,8 @@ do_install_append() {
if [ "${TARGET_ARCH}" = "x86_64" ]; then
# There are 2 copies of the NVDIMM modules which are built. This is a
# temporary fix to make sure the correct set of modules are used.
- rm -rf ${D}/lib/modules/${LINUX_VERSION}.0-yocto-standard/kernel/drivers/nvdimm/
- rm -rf ${D}/lib/modules/${LINUX_VERSION}.0-yocto-standard/kernel/drivers/dax/
- rm -rf ${D}/lib/modules/${LINUX_VERSION}.0-yocto-standard/kernel/drivers/acpi/
+ rm -rf ${D}/lib/modules/${LINUX_VERSION}.0${LINUX_VERSION_EXTENSION}/kernel/drivers/nvdimm/
+ rm -rf ${D}/lib/modules/${LINUX_VERSION}.0${LINUX_VERSION_EXTENSION}/kernel/drivers/dax/
+ rm -rf ${D}/lib/modules/${LINUX_VERSION}.0${LINUX_VERSION_EXTENSION}/kernel/drivers/acpi/
fi
}
--
1.9.1
3 years, 11 months
[PATCH] fwts: Update fwts v17.12.00
by Naresh Bhat
Update FWTS to version v17.12.00
Signed-off-by: Naresh Bhat <naresh.bhat(a)linaro.org>
---
meta-luv/recipes-core/fwts/fwts_git.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-luv/recipes-core/fwts/fwts_git.bb b/meta-luv/recipes-core/fwts/fwts_git.bb
index affe840..3f52dce 100644
--- a/meta-luv/recipes-core/fwts/fwts_git.bb
+++ b/meta-luv/recipes-core/fwts/fwts_git.bb
@@ -4,9 +4,9 @@ HOMEPAGE = "https://wiki.ubuntu.com/Kernel/Reference/fwts"
LICENSE = "GPLv2+"
LIC_FILES_CHKSUM = "file://src/main.c;beginline=1;endline=16;md5=31da590f3e9f3bd34dcdb9e4db568519"
-PV = "V17.11.00+git${SRCPV}"
+PV = "V17.12.00+git${SRCPV}"
-SRCREV = "0ec5075e19e14b6f7a81732ee4c7f1481e1ed523"
+SRCREV = "df2784c6fbff02288c736f85354b22f46dc193f4"
SRC_URI = "git://kernel.ubuntu.com/hwe/fwts.git \
file://0001-acpi-madt-only-inspect-Local-APIC-x2APIC-SAPIC-table.patch \
file://luv-parser-fwts \
--
2.7.4
3 years, 11 months
luv live GPT image issue
by Naresh Bhat
Hi Megha,
When I burn and boot LUV GPT image on a real hardware I can see the
following issue in a boot log
..
.......
[ 18.098295] pcieport 0000:0a:00.0: Refused to change power state,
currently in D0
[ 18.175166] GPT:Primary header thinks Alt. header is not at the end of
the disk.
[ 18.175169] GPT:223231 != 312581807
[ 18.175169] GPT:Alternate GPT header not at the end of the disk.
[ 18.175170] GPT:223231 != 312581807
[ 18.175171] GPT: Use GNU Parted to correct GPT errors.
[ 18.175178] sda: sda1 sda2
[ 18.175693] sd 0:0:0:0: [sda] Attached SCSI disk
[ 18.805875] Freeing unused kernel memory: 1600K
[ 18.817666] NET: Registered protocol family 10
[ 18.822684] Segment Routing with IPv6
Welcome to Linux UEFI Validation Distribution 2.2-dev!
..
......
I am assuming there should be an issue in GPT partition creation
implementation logic. Are you guys able to see the same issue on x86 too
?
Regards
-Naresh
3 years, 11 months
[PATCH] fwts: Update fwts v18.01.00
by Naresh Bhat
Update FWTS to version v18.01.00
Signed-off-by: Naresh Bhat <naresh.bhat(a)linaro.org>
---
meta-luv/recipes-core/fwts/fwts_git.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-luv/recipes-core/fwts/fwts_git.bb b/meta-luv/recipes-core/fwts/fwts_git.bb
index 62d2430..ef29b1e 100644
--- a/meta-luv/recipes-core/fwts/fwts_git.bb
+++ b/meta-luv/recipes-core/fwts/fwts_git.bb
@@ -4,9 +4,9 @@ HOMEPAGE = "https://wiki.ubuntu.com/Kernel/Reference/fwts"
LICENSE = "GPLv2+"
LIC_FILES_CHKSUM = "file://src/main.c;beginline=1;endline=16;md5=31da590f3e9f3bd34dcdb9e4db568519"
-PV = "V17.12.00+git${SRCPV}"
+PV = "V18.01.00+git${SRCPV}"
-SRCREV = "df2784c6fbff02288c736f85354b22f46dc193f4"
+SRCREV = "0a8f0b8a75d047f790a0a4730965363b2e7bc6ee"
SRC_URI = "git://kernel.ubuntu.com/hwe/fwts.git \
file://luv-parser-fwts \
"
--
2.7.4
3 years, 11 months
Firmware Test Suite 18.01.00 is released
by ivanhu
FWTS 18.01.00 is released.
It is available from:
Tar: http://fwts.ubuntu.com/release/fwts-V18.01.00.tar.gz
PPA: https://launchpad.net/~firmware-testing-team/+archive/ubuntu/ppa-fwts-stable
Release notes: https://wiki.ubuntu.com/FirmwareTestSuite/ReleaseNotes/18.01.00
= New Features =
* ACPICA: Update to version 20180105
= Fixed Bugs =
* acpi: LPIT: check for monotonically increasing UID
* fwts-test: sync up with changes in lpit test
* Treewide: update copyright year to 2018
* fwts-test: arg-help: sync up with copyright year changes
* acpica: fix linking issues when building non ACPI builds
* lib: fwts-battery: use PRIu32 format specifier, fixes cppcheck warning
* acpi: acpidump: move declaration to before statements, add blank lines
* lib: fwts_safe_mem: don't perform void * pointer arithmetic, fix 32 bit end
* lib: fwts_alloc: move 'pos' to a deeper scope, minor style change
* opal: reserve_mem: remove redundant initialization of pointer p
* opal: reserve_mem: remove unused variable 'i' and move scope of variable 'value'
* sbbr: rsdp: remove redundant initialization of boolean 'signature_pass'
* acpi: madt: move scope of boolean 'passed'
* acpi: pptt: move scope of index variable 'i'.
* acpi: rasf: move scope of index variable 'i'
* sbbr: acpitables: clean up code, move scope of some variables
* acpi: erst: cast size to uint64_t to clean up static analysis warning
* uefi: uefidump: clean up some static analysis warnings
* securebootcert: add checking read-only for the AuditMode and DeployedMode
* securebootcert: move to UNSAFE category
= Detail Changelog =
To check /usr/share/doc/fwts/changelog.Debian.gz or fwts_18.01.00-0ubuntu1.debian.tar.gz from https://launchpad.net/ubuntu/+source/fwts
-- Fwts-announce mailing list Fwts-announce(a)lists.ubuntu.com Modify
settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/fwts-announce
3 years, 11 months
Linux UEFI Validation Project v2.2 release
by Megha Dey
Hello,
This is to announce the release of LUV v2.2
Since this release includes mostly bug fixes, stabilization and
fine-tuning updates, it made sense to issue the final release of LUVv2.2
and start a new release cycle of LUV v2.3.
=== Features
1. Add a wrapper script to setup build environment which makes
configuring LUV build systems very simple. It also makes it easy to
perform automated builds from a fresh clone of the git repository.
2. Write messages to a console and/or debug file so that someone with
access to only a serial console or netconsole will also know what is
going on. Currently, we only use the plymouth graphical manager to
display certain messages to the user.
=== Bug Fixes
1. When configuring netconsole in preboot environment, the script kept
waiting for network to be up to create a socket. This wait keeps bits
from running, thus giving the user the impression of a hang. Gayatri
fixed this issue by creating a socket only if netconsole parameters are
valid and there is network connectivity.
2. Test-suites may use some characters in their output which may have
special meaning in HTML. Thus, the text rendered in the HTML report
would be incorrect. Ricardo fixed this issue by introducing a new
function which groups together the text substitutions that need to be
performed in text intended to be included in the HTML report.
3. The pstore-clean service of the telemetrics-client copies crash
contents out of pstore directory before clearing it out to free up space
for any further crash. LUV writes crash log to efi variables in normal
kernel (if it crashes) and collects crash report only in kexec kernel
and sends it to telemetrics server only when luv.telemetrics is enabled.
Sai added these conditions to the pstore-clean service file.
=== Updates:
1. We have updated the LUV rocko branch with contents from Poky and
meta-oe rocko branches.
2. We include FWTS v17.12.00 which us the latest version as of this
week.
== Binary images for x86:
The release images for x86 (disk and network) will be available on
https://01.org/linux-uefi-validation/v2.2 on 26th Jan 2018
=== Known issues
1. If you have an existing build environment and do a git pull to get
the latest code, you might see the following error because TEMPLATECONF
is pointing to non-existing directory. (Latest poky has removed the
meta-yocto layer) Error: TEMPLATECONF value points to nonexistent
directory 'meta-yocto/conf'. To resolve this issue, one needs to do a
clean build of LUV or use the newly added luv-setup script to set their
environment.
2. Netconsole in bits does not work if the listener is on a different
subnet compared to the host.
3. If we pull out USB stick before LUV completes, the first boot file
remains (which contains a list of completed test-suites). If we reuse
the same USB stick again, LUV will not execute the previously completed
test-suites.
== Git Repository URL change:
The LUV git repository URL has been updated from
https://github.com/01org/luv-yocto.git
to https://github.com/intel/luv-yocto.git
=== Short log:
Many thanks to all the contributors of this release. This is how the
short log looks like:
Gayatri Kammela (1):
bits: skip network configuration when unavailable
Megha Dey (18):
luv: Remove kexec-tools recipe
Merge branch master of git://git.yoctoproject.org/poky
Merge branch master of
git://git.openembedded.org/meta-openembedded
qemu: Update to 2.11.0
chipsec: fix RDEPENDS and DEPENDS due to non-existent packages
luv: increase the maximum size of the initramfs
luv: Add custom conf files
luv-setup: Tiny wrapper to make configuration easier
meta-luv/README: Update README to setup LUV builds
plymouth: Update number of test suites
plymouth: Prevent overwriting of messages
luv-test: Move plymouth functions to new script
luv-test: update standard output for luv scripts
luv-test: Send messages to console and debug file
luv-test: Rename plymouth function names
luv-test-manager: Do not redirect results to kmsg
luv-test: Do not print unnecessary messages to console
luv-test: Add missing return in submit_results
Naresh Bhat (1):
fwts: Update fwts v17.12.00
Ricardo Neri (1):
luv-test-parser: Sanitize plain text for HTML report
Sai Praneeth (1):
telemetrics: Run pstore-clean *only* when luv.telemetrics is
enabled and in kexec kernel
Thanks,
Megha
3 years, 11 months
[PATCH] telemetrics: Run pstore-clean *only* when luv.telemetrics is enabled and in kexec kernel
by Sai Praneeth Prakhya
From: Sai Praneeth <sai.praneeth.prakhya(a)intel.com>
pstore-clean service, copies crash contents out of pstore directory and
cleans up the directory; so as to free up the space. LUV writes crash
log to efi variables in normal kernel (if it crashes) and collects crash
report *only* in kexec kernel and sends it to telemetrics server only
when luv.telemetrics is enabled. Hence, add these conditions to
pstore-clean service file.
Cc: Naresh Bhat <naresh.bhat(a)linaro.org>
Cc: Megha Dey <megha.dey(a)linux.intel.com>
Cc: Ricardo Neri <ricardo.neri-calderon(a)linux.intel.com>
Signed-off-by: Sai Praneeth Prakhya <sai.praneeth.prakhya(a)intel.com>
---
...n-Run-pstore-clean-only-when-luv.telemetr.patch | 33 ++++++++++++++++++++++
.../recipes-core/telemetrics/telemetrics_git.bb | 1 +
2 files changed, 34 insertions(+)
create mode 100644 meta-luv/recipes-core/telemetrics/files/0001-pstore-clean-Run-pstore-clean-only-when-luv.telemetr.patch
diff --git a/meta-luv/recipes-core/telemetrics/files/0001-pstore-clean-Run-pstore-clean-only-when-luv.telemetr.patch b/meta-luv/recipes-core/telemetrics/files/0001-pstore-clean-Run-pstore-clean-only-when-luv.telemetr.patch
new file mode 100644
index 000000000000..4336375c385f
--- /dev/null
+++ b/meta-luv/recipes-core/telemetrics/files/0001-pstore-clean-Run-pstore-clean-only-when-luv.telemetr.patch
@@ -0,0 +1,33 @@
+From d44e31757fde2744b1f936176435f2d2522e6189 Mon Sep 17 00:00:00 2001
+From: Sai Praneeth <sai.praneeth.prakhya(a)intel.com>
+Date: Tue, 23 Jan 2018 16:33:19 -0800
+Subject: [PATCH] pstore-clean: Run pstore-clean *only* when luv.telemetrics is
+ enabled and in kexec kernel
+
+pstore-clean service, copies crash contents out of pstore directory and
+cleans up the directory; so as to free up the space. LUV writes crash
+log to efi variables in normal kernel (if it crashes) and collects crash
+report *only* in kexec kernel and sends it to telemetrics server only
+when luv.telemetrics is enabled. Hence, add these conditions to
+pstore-clean service file.
+
+Signed-off-by: Sai Praneeth Prakhya <sai.praneeth.prakhya(a)intel.com>
+---
+ src/data/pstore-clean.service.in | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/src/data/pstore-clean.service.in b/src/data/pstore-clean.service.in
+index 34647dbec070..9b9d9b59b223 100644
+--- a/src/data/pstore-clean.service.in
++++ b/src/data/pstore-clean.service.in
+@@ -1,5 +1,7 @@
+ [Unit]
+ Description=Telemetrics Pstore Clean Service
++ConditionKernelCommandLine=luv.telemetrics
++ConditionKernelCommandLine=luv.crash
+
+ [Service]
+ ExecStart=@bindir@/pstoreclean
+--
+2.1.4
+
diff --git a/meta-luv/recipes-core/telemetrics/telemetrics_git.bb b/meta-luv/recipes-core/telemetrics/telemetrics_git.bb
index 5a5d7e13c0ae..a397bd9e40ca 100644
--- a/meta-luv/recipes-core/telemetrics/telemetrics_git.bb
+++ b/meta-luv/recipes-core/telemetrics/telemetrics_git.bb
@@ -20,6 +20,7 @@ SRC_URI = "git://github.com/clearlinux/telemetrics-client \
file://0001-Add-Kernel-panic-to-the-list.patch \
file://0001-pstore-start-after-network.patch \
file://config.site \
+ file://0001-pstore-clean-Run-pstore-clean-only-when-luv.telemetr.patch \
"
SRCREV="3d24527096bc14ca8b425f66daed4547b9ee93da"
--
2.1.4
3 years, 11 months
[PATCH V2 0/3] luv : Add a wrapper script to setup build env
by Megha Dey
There are a number of steps required to configure the luv-yocto
development environment correctly, and it's really easy to miss one,
which results in a non-working system.
Other projects based on the Yocto Project provide a wrapper script
that does all the necessary configuration.
Having this done in a wrapper script would also make it much, much
simpler to perform automated builds from a fresh clone of the git
repository.
In this patchset, we add a script "luv-setup" which makes configuring
LUV build systems very simple. This patchset addresses:
https://github.com/01org/luv-yocto/issues/31
Changes V1->V2
1. Fixed some typos.
Megha Dey (3):
luv: Add custom conf files
luv-setup: Tiny wrapper to make configuration easier
meta-luv/README: Update README to setup LUV builds
luv-setup | 10 ++
meta-luv/README | 34 ++----
meta-luv/conf/bblayers.conf.sample | 14 +++
meta-luv/conf/conf-notes.txt | 12 ++
meta-luv/conf/local.conf.sample | 236 +++++++++++++++++++++++++++++++++++++
5 files changed, 282 insertions(+), 24 deletions(-)
create mode 100755 luv-setup
create mode 100644 meta-luv/conf/bblayers.conf.sample
create mode 100644 meta-luv/conf/conf-notes.txt
create mode 100644 meta-luv/conf/local.conf.sample
--
1.9.1
3 years, 11 months
[PATCH V3 0/3] luv : Add a wrapper script to setup build env
by Megha Dey
There are a number of steps required to configure the luv-yocto
development environment correctly, and it's really easy to miss one,
which results in a non-working system.
Other projects based on the Yocto Project provide a wrapper script
that does all the necessary configuration.
Having this done in a wrapper script would also make it much, much
simpler to perform automated builds from a fresh clone of the git
repository.
In this patchset, we add a script "luv-setup" which makes configuring
LUV build systems very simple. This patchset addresses:
https://github.com/01org/luv-yocto/issues/31
Changes V1->V2
1. Fixed some typos.
Changes V2->V3
1. Added Matt's Originally-by line
Megha Dey (3):
luv: Add custom conf files
luv-setup: Tiny wrapper to make configuration easier
meta-luv/README: Update README to setup LUV builds
luv-setup | 10 ++
meta-luv/README | 34 ++----
meta-luv/conf/bblayers.conf.sample | 14 +++
meta-luv/conf/conf-notes.txt | 12 ++
meta-luv/conf/local.conf.sample | 236 +++++++++++++++++++++++++++++++++++++
5 files changed, 282 insertions(+), 24 deletions(-)
create mode 100755 luv-setup
create mode 100644 meta-luv/conf/bblayers.conf.sample
create mode 100644 meta-luv/conf/conf-notes.txt
create mode 100644 meta-luv/conf/local.conf.sample
--
1.9.1
3 years, 11 months
