** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762468
Title:
Cryptoswap not working in Bionic
To manage notifications about this bug go to:
-update-
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1310058
that is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762468
Title:
Cryptoswap not working in Bionic
To manage
At the risk of saying something completely unrelated; any change this is
a regression of #1310058 where the UUID got overwritten? It came back a
few times around 2015, leading me to believe that the devs don't
actually use this method, and might not test for this scenario, making a
regression
Some good and bad news: I have been testing this in a running Gnome 3
environment. I decided to start testing on console. On console, all
kernels seem to fail using crypt swap. This suggests to me that failure
must depend on current memory usage, dirty ratio, or some such runtime
condition.
Thanks for finding the mainline 4.10 does not have the bug and 4.11
final does. Can you also test v4.11-rc1, so we can find which release
candidate introduced the bug?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc1
--
You received this bug notification because you are a member of
In response to #7, I don't think this is the same issue. The cryptswap
initiates with no difficulties, timeouts, etc. on boot. When I first
installed Bionic, ubiquity did not correctly install the swap, and I
filed #1759253 on that issue.
--
You received this bug notification because you are a
BTW, I _do_ realize that you want a starting point for bisection; I'm
sorry this is turning out so messy.
On 04/11/2018 05:51 PM, Martin Weinberg wrote:
> The first kernel on that list that exhibits the bug is the first one:
> 4.14 Final. Recall: the bug results in a full up hang. The disk
The first kernel on that list that exhibits the bug is the first one:
4.14 Final. Recall: the bug results in a full up hang. The disk stops
swapping (it's audible). I can reboot with sysctl SUB however.
I then tested 4.13.0-36 from the Ubuntu 17.10 respoitory, followed by
I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the latest kernel that did not have this
issue.
Can you test the following kernels and report back? We are looking for
the first
Looks like the same issue as reported on lp:#1736072
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762468
Title:
Cryptoswap not working in Bionic
To manage notifications about this bug go to:
Yes, the problem does occur in mainline 4.16 and I have added the
requested tag.
If anything, 4.16.1 seems slower than 4.15 release kernel even for no
cryptswap. It could be that my disk is too slow for cryptswap, but it
did work in 17.10.
The obvious work around is not to use cryptswap, of
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 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
It seems that cryptswap is working correctly on 17.10 with the kernel
4.13.0-36-generic on a different machine using the same test as
described above. I tried the same kernel (4.13.0-36) on 18.04 (machine
used in original post) and it still fails. Of course, I checked that
the swap appears in
The code that I used to force failure, memtest.c, is attached to the bug
report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762468
Title:
Cryptoswap not working in Bionic
To manage
14 matches
Mail list logo
