** This bug is no longer a duplicate of bug 1796292
Tight timeout for bcache removal causes spurious failures
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Andrea Righi (arighi)
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned) => Andrea Righi (
Hi Ryan, I've uploaded a new test kernel:
https://kernel.ubuntu.com/~arighi/LP-1796292/4.15.0-54.58+lp1796292/
This one is based on 4.15.0-54.58 and it addresses specifically the
bch_bucket_alloc() problem (with this patch applied:
https://lore.kernel.org/lkml/20190710093117.GA2792@xps-13/T/#u).
... and, just in case, I've uploaded also a test kernel based on the latest
bionic's master-next + a bunch of extra bcache fixes:
https://kernel.ubuntu.com/~arighi/LP-1796292/4.15.0-55.60+lp1796292+1/
If the previous kernel is still buggy it'd be nice to try also this one.
--
You received this
I've found other upstream fixes that might be interesting to test:
https://git.launchpad.net/~arighi/+git/bionic-linux/log/?h=lp-1835279
I've uploaded a new test kernel here (still based of 4.15.0-54 + the
backported fixes): https://kernel.ubuntu.com/~arighi/LP-1835279/
It'd be great if you could
eam) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-work
eam) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
** Changed in: kernel-
cal-kernel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
** Changed in
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Andrea Righi (arighi)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1822579
Title:
Remove btrfs module afte
Adding a test case script to reproduce the bug.
** Attachment added: "btrfs-fallocate-test.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822579/+attachment/5252459/+files/btrfs-fallocate-test.sh
--
You received this bug notification because you are a member of Kernel
Packages, wh
This problem is fixed by
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=be2d253cc98244765323a7c94cc1ac5cd5a17072.
Only Xenial seems to be affected. I'll post an SRU soon.
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
** Description changed:
- If one issues a rmmod (or modprobe -r) command after a failed fallocate
- attempt, it will cause error with call trace:
+ SRU Justification:
- =
- BUG btrfs_extent_map (Not tainted): Objects
nel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
--
You recei
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Khaled El Mously (kmously) => Andrea Righi (arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Khaled El Mously (kmously) => Andrea Righi (arighi)
** Changed in: kernel-sru-workflow/prepare-p
cal-kernel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
** Changed in
nel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
--
You recei
nel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
--
You recei
I've done a test with the fix from bug #1813244 and the problem doesn't
seem to happen. Probably a duplicate bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736390
Title:
openvswitc
Fix has been merged upstream.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1813244
Title:
systemd cause kernel trace "BUG: unable to handle kernel paging
request at 6db23a14" on Cosm
eam (canonical-kernel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
*
Moreover, any chance to add slub_debug=FZPU to the kernel boot
parameters and see if we can trigger the problem again? This would add
useful information to the kernel oops reported in syslog. Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
This seems to be fixed upstream by:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4a8ab5ea0cde753b03bfefe4c98a8c4c61f46550
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
sis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-3.1
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-3.
I'll take a look at the other patches, I think they can be easily
applied to 4.15 if they don't require too much backporting work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823972
Ti
@navytux yes, a few of them require minimal changes, but most of them
can be applied cleanly to 4.15.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823972
Title:
bionic, xenial/hwe: mi
All fixes applied here:
git://git.launchpad.net/~arighi/+git/bionic-linux fuse-fixes
And also sent an SRU pull request. Let's see if they get merged.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
Assignee: Andrea Righi (arighi)
Status: Invalid
** Affects: linux (Ubuntu Bionic)
Importance: Medium
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andrea Righi (arighi)
--
You received this bug n
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Andrea Righi (arighi)
** Changed in: linux (Ubuntu)
Assignee: Andrea Righi (arighi) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Summary changed:
- Bionic update: update stable patchset for fuse 2019-04-12
+ Bionic update: upstream stable patchset for fuse 2019-04-12
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs
@jason-hobbs, I don't see any kernel error in the log attached to
comment #53, so it seems to be a different issue, maybe a performance
regression that is causing curtin to timeout. I would keep this bug
closed / fixed and open a new one.
If you can easily reproduce it, could you open a new bug an
Interesting that the d3cold_allowed change made some differences (I'm
assuming it was failing 100% of the times before that change).
Few more questions. After a bad resume:
1) are there unkillable processes (D state) in the system (`ps axuw |
grep D`)?
2) does `sudo iwlist wlp4s0 scan` return an
kernel git (x86_64-generic flavour).
commit c50532b9d7b623ff98aeaf0b848e58adae54ca75 (HEAD -> master, tag:
Ubuntu-4.15.0-48.51, origin/master, origin/HEAD)
Author: Andrea Righi
Date: Tue Apr 2 18:31:55 2019 +0200
UBUNTU: Ubuntu-4.15.0-48.51
Signed-off-by: Andrea Righi
1. B
** Tags added: patch
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andrea Righi (arighi)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
gin/master, origin/HEAD)
Author: Andrea Righi
Date: Tue Apr 2 18:31:55 2019 +0200
UBUNTU: Ubuntu-4.15.0-48.51
Signed-off-by: Andrea Righi
1. Build a kernel image with 'zfs_enable' flag set as false.
2. Build SPL/ZFS modules independently by 'make' command (de
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andrea Righi (arighi)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: bionic cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1825942
Title:
kernel crash : net_sched race condition in tcindex_destroy()
Status in linux package in Ubunt
EAD)
Author: Andrea Righi
Date: Tue Apr 2 18:31:55 2019 +0200
- UBUNTU: Ubuntu-4.15.0-48.51
-
- Signed-off-by: Andrea Righi
+ UBUNTU: Ubuntu-4.15.0-48.51
+
+ Signed-off-by: Andrea Righi
1. Build a kernel image with 'zfs_enable' flag set as false.
2
** Description changed:
+ [Impact]
+
+ It is possible to trigger a NULL pointer dereference in tcindex_delete()
+ with a simple reproducer script, this is because in tcindex_set_parms()
+ when old_r doesn't exist we set the new exts to cr.exts that can be
+ uninitialized, triggering the NULL poin
nel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
--
You recei
nel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
--
You recei
nel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
--
You recei
nel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
--
You recei
cal-kernel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
** Changed in
Hi Chris, just to make sure I understand (from a kernel perspective),
can you confirm that `echo mem > /sys/power/state` is also fast at
reaching the suspend state?
In that case it would be interesting to check if there's a delay at
detecting the state of the lid switch. For this, could you run th
@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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1766201
Title:
Fix against bionic submitted to the kernel ML:
https://lists.ubuntu.com/archives/kernel-team/2019-May/100741.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1825942
Title:
kernel cra
Hi Kim,
I've applied the following patches to the bionic kernel (4.15):
[from LP #1816669]
818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum
e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register
90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode
[from LP #18
Alright, the fact that `echo mem > /sys/power/state` is fast means that
the delay issue is not in the "suspend" path and we also know that it's
not even in the detection path (/proc/acpi/button/lid/LID0/state). So
the delay must be somewhere between the detection of the event and the
delivery of th
*** This bug is a duplicate of bug 1819485 ***
https://bugs.launchpad.net/bugs/1819485
** This bug has been marked a duplicate of bug 1819485
AMD Rome : Additional patches
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
** Summary changed:
- AMD Rome : Additional patches
+ x86: add support to AMD Rome CPU
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1819485
Title:
x86: add support to AMD Rome CPU
S
mily: Default string
dmi.product.name: DAYTONA_X
dmi.product.sku: Default string
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: AMD Corporation
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andrea Righi (arighi)
--
You received this bug notification because you ar
** Summary changed:
- x86: add support to AMD Rome CPU
+ x86: add support for AMD Rome
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1819485
Title:
x86: add support for AMD Rome
Statu
This patch seems to fix the problem for me.
See also:
https://lkml.org/lkml/2019/3/13/181
** Patch added: "btrfs-raid56-properly-unmap-parity-page-in-finish_pa.patch"
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812845/+attachment/5245817/+files/btrfs-raid56-properly-unmap-parity-page
nel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
--
You recei
cal-kernel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
** Changed in
cal-kernel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
** Changed in
eam (canonical-kernel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
*
Tested the following on bionic:
$ cat main.cpp
#include
#include
static __attribute__ ((noinline)) int my_really_big_function()
{
for(size_t i = 0; i < 1000; ++i)
{
benchmark::DoNotOptimize(i % 5);
}
return 0;
}
static __attribute__ ((noinline)) void caller1()
{
for(size_t i = 0;
I have also been able to reproduce this bug with 4.18.0-10, 4.18.0-13,
4.18.0-14 and 4.18.0-16. So it doesn't seem to be a regression.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1813244
According to the trace reported in syslog the problem happened in
btrfs_get_or_create_delayed_node(), specifically the faulty function was
prefetch_freepointer() defined in mm/slub.c.
Considering that btrfs_get_or_create_delayed_node() is allocating a
"node" object using kmem_cache_zalloc() from a
I did more tests with this, it looks like the problem is hidden
somewhere in openvswitch. The specific test case that seems to trigger
the bug 100% of the time is the one attached, but it requires to change
the time immediately before running it (for example using date --set
"23:57:00", as suggeste
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.
With this patch applied I can't reproduce the problem anymore.
See also: https://lkml.org/lkml/2019/3/27/1762
** Patch added: "openvswitch: fix flow actions reallocation"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813244/+attachment/5249928/+files/0001-openvswitch-fix-flow-actions-r
New patch after the review from the LKML.
** Patch added: "openvswitch: fix flow actions reallocation - v2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813244/+attachment/5250007/+files/0001-openvswitch-fix-flow-actions-reallocation.patch
--
You received this bug notification becau
** Description changed:
+ SRU Justification:
+
+ [Impact]
+
+ * Parity page in btrfs raid56 is incorrectly unmapped, allowing to
+ easily trigger a reference counter bug on i386 causing a kernel panic
+
+ * The fix unmaps the right rbio pages and adds the proper kunmap() call
+ for the parity
** Description changed:
SRU Justification:
[Impact]
- * Parity page in btrfs raid56 is incorrectly unmapped, allowing to
+ * Parity page in btrfs raid56 is incorrectly unmapped, allowing to
easily trigger a reference counter bug on i386 causing a kernel panic
- * The fix unmaps t
*** This bug is a duplicate of bug 1766201 ***
https://bugs.launchpad.net/bugs/1766201
The following patch should be applied to downgrade the "integrity: Unable to
open file:" errors:
https://lists.ubuntu.com/archives/kernel-team/2017-February/082526.html, as
addressed in the duplicate bug #
** Description changed:
+ SRU Justification:
+
+ [Impact]
+
+ * Flow action buffer can be incorrectly resized to contain the newly
+ added action entries: the buffer is always resized multiplying the
+ previous size by 2, but this might be not enough if the requested size
+ is bigger than previ
ffects: linux (Ubuntu)
Importance: High
Assignee: Andrea Righi (arighi)
Status: New
** Affects: linux (Ubuntu Bionic)
Importance: High
Assignee: Andrea Righi (arighi)
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
Considering that only one of the two fixes mentioned in comment #11 are
applied to the bionic kernel, I've uploaded a new test kernel here
https://kernel.ubuntu.com/~arighi/LP-1752002/ with both fixes applied.
It would be great if someone could test this kernel to confirm that the
problem is actua
Thanks Chris, looking at journalct it seems that from the "Lid closed"
event and "Reached target Sleep" there's just 1s. So, the time between
these two events is also definitely fast, therefore the bottleneck is
not in the part of systemd that processes the "lid closed" event.
At this point I'm wo
signed) => Andrea Righi (arighi)
** Changed in: linux (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1825942
Title:
kernel crash : net_sched race
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
--
Yo
This module in attach (similar to the one posted by @mjeanson) has been
used as an effective reproducer for this bug. It looks like we need to
reboot the system a couple of times and load this module to immediately
trigger the bug.
** Attachment added: "vmalloc_sync_all() stress test"
https://
** Description changed:
+ [Impact]
+
+ Commit d653420532d580156c8486686899ea6a9eeb7bf0 in bionic enabled kernel
+ page table isolation for x86_32, but also introduced a kernel bug (the
+ BUG_ON() condition in vmalloc_sync_one()) that seems to happen when
+ vmalloc_sync_all() is called multiple ti
nel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
--
You recei
nel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
--
You recei
nel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
--
You recei
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1831103
Title:
bionic: netlink: potential shift overflo
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&id=58441dc86d7b066a2c02079829a96035587a7066) and the cosmic kernel
(http
@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 K
** 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-
+
** 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 the
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
nel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
--
You recei
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1813244
Title:
systemd cause kernel trace "BUG: unable
nel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
--
You recei
eam (canonical-kernel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
*
Verification done using the test case reported in the description
(https://launchpadlibrarian.net/416589265/lp1262692)
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is s
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1822579
Title:
Remove btrfs module after a failed fallo
Verification done in bionic using the test case reported in the
description (https://launchpadlibrarian.net/416589265/lp1262692)
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages,
Can you try to set the following before suspend:
echo 0 > /sys/class/net/wlp4s0/device/d3cold_allowed
And then test a suspend/resume cycle.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs
I've uploaded a new test kernel based on the latest bionic kernel from
master-next:
https://kernel.ubuntu.com/~arighi/LP-1796292/4.15.0-56.62~lp1796292/
In addition to that I've backported all the recent upstream bcache fixes
and applied my proposed fix for the potential deadlock in
bch_allocator
Thanks Ryan, this is very interesting:
[ 259.411486] bcache: register_bcache() error /dev/vdg: device already
registered (emitting change event)
[ 259.537070] bcache: register_bcache() error /dev/vdg: device already
registered (emitting change event)
[ 259.797830] bcache: register_bcache() error
Ryan, unfortunately the last reproducer script is giving me a lot of
errors and I'm still trying to figure out how to make it run to the end
(or at least to a point where it's start to run some bcache commands).
In the meantime (as anticipated on IRC) I've uploaded a test kernel
reverting the patc
After some help from Ryan (on IRC) I've been able to run the last
reproducer script and trigger the same trace. Now I should be able to
collect all the information that I need and hopefully post a new test
kernel (fixed for real...) soon.
--
You received this bug notification because you are a me
Some additional info about the deadlock:
crash> bt 16588
PID: 16588 TASK: 9ffd7f332b00 CPU: 1 COMMAND: "bcache_allocato"
[exception RIP: bch_crc64+57]
RIP: c093b2c9 RSP: ab9585767e28 RFLAGS: 0286
RAX: f1f51403756de2bd RBX: RCX: 0
** Description changed:
- $ cat /proc/version_signature
+ [Impact]
+
+ bcache_allocator() can call the following:
+
+ bch_allocator_thread()
+ -> bch_prio_write()
+ -> bch_bucket_alloc()
+ -> wait on &ca->set->bucket_wait
+
+ But the wake up event on bucket_wait is supp
Ryan, I've uploaded a new test kernel with the fix mentioned in the
comment before:
https://kernel.ubuntu.com/~arighi/LP-1796292/4.15.0-56.62~lp1796292+4/
I've performed over 100 installations using curtin-nvme.sh
(install_count = 100), no hung task timeout. I'll run other stress tests
to make su
*** This bug is a duplicate of bug 1784665 ***
https://bugs.launchpad.net/bugs/1784665
** This bug has been marked a duplicate of bug 1784665
bcache: bch_allocator_thread(): hung task timeout
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
1 - 100 of 689 matches
Mail list logo
