Returned to computer to find Firefox frozen, tried to kill Firefox but it
turned zombie, after that system froze. Still answered ping but nothing else.
Rebooted by "sysrq + b".
I have swap on an LVM lv on a sata SSD.
I don't run luks.
** Attachment added: "kernel.log cutout."
Pardon the comment spam, I made a mistake, your use case is
* sw -> LVM -> LUKS -> nvme
so both our failure cases have an extra layer between swap and LUKS
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Oh also another common thing we have is, both devices are SSDs. My LUKS
containers are open with 'discard' option.
--
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/1690796
Title:
Kernel
I don't think it's encrypted swap per se, as I also have it, I think
it's additional layering. In my case:
* sw -> LUKS -> sda5 = OK
* swapfile -> ext4 (root fs) -> LUKS -> sda2 = problem
And from what I see in your case:
* sw -> LUKS -> LVM -> nvme0n1p3 = problem
--
You received this bug
Yes, I have swap on LVM, of which the PVs are on a crypted fs.
So:
- /dev/nvme0n1p3 --> cryptsetup(luks) --> /dev/mapper/nvme0n1p3_crypt
- /dev/mapper/nvme0n1p3_crypt is the physical volume in my LVM setup
- swap is a logical volume in the LVM
So that would be quite a curious bug, caused by
I had a default swapfile as set up by the 17.04 installer. Suspecting
that might be the cause I changed and made a swap partition instead. So
far so good, haven't had this problem since.
@baszoetekouw, am I reading your UdevDB.txt correctly, you're using a
swap partition in a LUKS container? Is
I had the same happen to me, I suppose, except the process involved was
Firefox. I filed the report with Bug #1692482. Marking it as duplicate.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Unfortunately, I can't really reproduce it. Journalctl shows the bug
having occurred twice since the beginnen of March, om kernel 4.10.0.
I'll install the 4.12 kernel and see the coming weeks if it triggers
again.
Thanks!
Bas.
On 15-05-17 22:03, Joseph Salisbury wrote:
> Do you have a way to
Do you have a way to reproduce this bug?
If so, would it be possible for you to test the latest upstream kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.12 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag
9 matches
Mail list logo
