I tested the eoan kernel 5.2.0-10-generic and the suspected problems in
the block layer didn't happen anymore after removing the workarounds
(artificial delays and module insertion) needed by the bionic kernel
4.15.0-54-generic used in core18. 5.3.0-050300rc4-generic also works
without any
That sounds awesome, Claudio, thank you! We'll start with Eoan and I
will work on getting a debug kernel ready in the meantime.
--
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/1835279
Thanks Connor. My test configuration is a custom core system using the
official core18 kernel snap on a KVM-based virtual machine. The kernel
snap is installed from channel 18 (snap download --channel 18 pc-kernel)
and my current revision is 240. That said, it's easy to test new kernels
as long as
Hey Claudio,
Did you experience this only after upgrading from a previous kernel? If
so, what was the kernel that you upgraded from?
I've been trying to reproduce this issue locally in a VM but haven't had
any luck so far. So, I've been working from the kernel Oops in comment
#1 and I am pretty
** Changed in: linux (Ubuntu)
Assignee: Connor Kuehl (connork) => (unassigned)
** Changed in: linux (Ubuntu)
Importance: Medium => Undecided
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: cscc
--
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/1835279
Title:
4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open
Status in linux package in Ubuntu:
Invalid
Thanks. I tested the proposed kernel and it does not prevent the crash,
which still occurs under the same circumstances when cryptsetup open
runs. It's possible, however, that the patch decreases the likehood of a
crash. In a very un-scientific test the latest patched kernel crashed in
3 out of 10
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
The udev workaround preloading is unrelated and can be removed, crashes
will also happen without using it.
--
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/1835279
Title:
** Attachment added: "4.15.0-54-generic #58+lp1835279 kernel log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835279/+attachment/5277230/+files/kernel-arighi.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
We're now opening the LUKS device using the master key directly and the
crash is happening again in both the original 4.15.0-54-generic
(buildd@lgw01-amd64-014) kernel or the patched 4.15.0-54-generic
(arighi@kathleen) kernel. The backtrace is very similar but unlike the
previous scenario it
Thanks Andrea. The new kernel seems to address the problem in such a way
that the block device made available is still not immediately usable,
but the kernel crash is prevented (at least in the test runs so far).
Now errors can be handled from userspace to retry the operation in case
of failure.
It would be interesting to try this fix:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=37f9579f4c31a6d698dbf3016d7bf132f9288d30
I've uploaded a test kernel (based on 4.15.0-54 + the fix mentioned above):
https://kernel.ubuntu.com/~arighi/LP-1835279/
Claudio, it
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Connor Kuehl (connork)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Connor Kuehl (connork)
** Changed in: linux (Ubuntu)
Status:
Further testing suggests that the problem is caused by the kernel not
having enough time to settle after partx -u exits (race between
acknowledging the new block device and actually having it available?).
Adding a 1s pause after the partition table is re-read seems to prevent
this crash.
--
You
This problem happens on Ubuntu Core (Core 20 development branch based on
Core 18) and apport is not available.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Description changed:
This is Linux version 4.15.0-54-generic (buildd@lgw01-amd64-014) (gcc
version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun 24
10:55:24 UTC 2019 (Ubuntu 4.15.0-54.58-generic 4.15.18), from pc-
kernel_240.snap
Version signature:
18 matches
Mail list logo
