** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package linux - 4.15.0-51.55
---
linux (4.15.0-51.55) bionic; urgency=medium
* linux: 4.15.0-51.55 -proposed tracker (LP: #1829219)
* disable a.out support (LP: #1818552)
- [Config] Disable a.out support
* [UBUNTU] qdio: clear intparm during
This bug was fixed in the package linux - 4.18.0-21.22
---
linux (4.18.0-21.22) cosmic; urgency=medium
* linux: 4.18.0-21.22 -proposed tracker (LP: #1829186)
* disable a.out support (LP: #1818552)
- [Config] Turn off a.out support
* ftrace in ubuntu_kernel_selftests hang
This bug was fixed in the package linux - 5.0.0-16.17
---
linux (5.0.0-16.17) disco; urgency=medium
* linux: 5.0.0-16.17 -proposed tracker (LP: #1829173)
* shiftfs: lock security sensitive superblock flags (LP: #1827122)
- SAUCE: shiftfs: lock down certain superblock flags
ubuntu@lewis:~$ uname -a
Linux lewis 4.18.0-21-generic #22-Ubuntu SMP Wed May 15 13:12:45 UTC 2019
ppc64le ppc64le ppc64le GNU/Linux
ubuntu@lewis:~$ apt policy linux-image-generic
linux-image-generic:
Installed: 4.18.0.21.22
Candidate: 4.18.0.21.22
Version table:
*** 4.18.0.21.22 500
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag
ubuntu@tiselius:~$ uname -a
Linux tiselius 5.0.0-16-generic #17-Ubuntu SMP Wed May 15 10:51:32 UTC 2019
ppc64le ppc64le ppc64le GNU/Linux
ubuntu@tiselius:~$ apt policy linux-image-generic
linux-image-generic:
Installed: 5.0.0.16.17
Candidate: 5.0.0.16.17
Version table:
*** 5.0.0.16.17 500
ubuntu@tiselius:~$ uname -a
Linux tiselius 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:26:12 UTC 2019
ppc64le ppc64le ppc64le GNU/Linux
ubuntu@tiselius:~$
ubuntu@tiselius:~$ apt policy linux-image-generic
linux-image-generic:
Installed: 4.15.0.51.53
Candidate: 4.15.0.51.53
Version
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
@manjo can you confirm that the "integrity: Unable to open file" errors
are not reported anymore with the fix applied? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766201
Title:
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766201
Title:
CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX
** Changed in: ubuntu-power-systems
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766201
Title:
CTAUTO:DevOps:860.50:devops4fp1:Error occurred during
** Changed in: linux (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Cosmic)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Disco)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
There appears to be more than one problem being described in this bug
report. Since they are separate issues they should be tracked as
separate bugs (this helps keeping tracking of the fixes).
We'll use this bug to track the original issue described in the bug
description (downgrading the x509
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because
And about the error "vio vio: uevent:" happening at boot, it could be
triggered by something in the initramfs. I think the best thing we can
do from a kernel perspective is to add extra information to the error
message to figure out exactly which task is triggering this error, and
maybe also print
** Description changed:
[Impact]
The integrity subsystem is still reporting error messages like this at
boot:
- integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
+ integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
- In a previous commit we have downgraded
** Description changed:
+ [Impact]
+
+ The integrity subsystem is still reporting error messages like this at
+ boot:
+
+ integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
+
+ In a previous commit we have downgraded these errors to warnings:
+
+ https://git.launchpad.net/~ubuntu-
@manjo thanks for testing again! Now I see, we need to apply another
small patch to security/integrity/digsig.c, that seems to have exactly
the same error message that should be considered a warning instead. I'll
post a fix soon.
--
You received this bug notification because you are a member of
Fresh install of 18.04 on Power9 system, installed linux-image-generic-
hwe-18.04
ubuntu@bobone:~$ uname -a
Linux bobone 4.18.0-18-generic #19~18.04.1-Ubuntu SMP Fri Apr 5 10:21:11 UTC
2019 ppc64le ppc64le ppc64le GNU/Linux
ubuntu@bobone:~$
ubuntu@bobone:~$ dmesg -xT -l emerg,alert,crit,err
Update: the patch to downgrade the error "Unable to open file..." to a
warning seems to be already applied to the bionic kernel
(https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/commit/?h=master-
next=58441dc86d7b066a2c02079829a96035587a7066) and the cosmic kernel
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: ubuntu-power-systems
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766201
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: ubuntu-power-systems
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766201
About the first two errors ("Unable to open file ... x509_ima.der") they should
be downgraded to warnings and this was previously addressed here:
https://lists.ubuntu.com/archives/kernel-team/2017-February/082526.html
Apparently this patch didn't get merged. I think we can easily apply
this one.
** Changed in: linux (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766201
Title:
CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg
error
reference: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771555
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766201
Title:
CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX
I can reproduce the same error on 18.04 runinng 4.18 HWE kernel. Seems
like we need to take a closer look..
ubuntu@P8lpar1:~$ dmesg -xT -l emerg,alert,crit,err
kern :err : [Wed Feb 6 15:08:08 2019] integrity: Unable to open file:
/etc/keys/x509_ima.der (-2)
kern :err : [Wed Feb 6
** Changed in: ubuntu-power-systems
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766201
Title:
CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg
** Tags added: powervm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766201
Title:
CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg
error Checking for all LINUX clients for
To re-iterate the question in comment #4, the bug description appears to
describe use of an LPAR. Does this report refer to running Ubuntu as a
guest under PowerVM? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Canonical Kernel Team (canonical-kernel-team)
--
You received this bug notification because you are a member of Ubuntu
The bug description describes use of an LPAR. Does this report refer to
running Ubuntu as a guest under PowerVM?
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)
** Changed in: ubuntu-power-systems
Importance: Undecided => High
** Changed in: ubuntu-power-systems
Assignee:
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766201
Title:
CTAUTO:DevOps:860.50:devops4fp1:Error occurred during
35 matches
Mail list logo