So in my case, my VM was configured with only 256MB of memory. This
caused no problem on the normal -virtual kernel but caused all sorts of
problems when I installed -lowlatency in the guest.
Upgrading to 384MB solved the problem reliably here, so perhaps this is
not the same thing afterall.
- So
Kernel version 5.4.0-37-lowlatency, btw
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1872964
Title:
Reliable crash in lowlatency kernel with LXD
Status in linux-signed package
I have an LXD Virtual Machine refusing to boot after installing the
-lowlatency kernel on it. Sounds like these _might_ be related, so
here's my info. I'm on a NUC too, btw.
Host: Ubuntu 20.04 LTS, LXD 4.2 snap (running -lowlatency)
Guest: Ubuntu 20.04 LTS
The guest was running without problems o
OK, will circle back to this bug in due course. From what you say it
might even be specific to that Nuc.
Mark
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1872964
Title:
Reliab
I'm not sure that it's workload-specific, it could also be an issue with
a specific driver or any number of things. RCU is widely used in the
kernel, so at this point I'm looking for the proverbial needle in the
haystack. I am trying to uncover code paths that you might have been
exercising that I
Hi Seth
I have been deploying charmed-kubernetes on a LXD cluster. I didn't
think the kernel crash was workload-specific, but of course it might be.
It looked more likely to be ZFS + lowlatency + snaps triggering the issue.
For now I have had to move to -generic on the machine which was causing
t
My attempts to reproduce this have been unsuccessful. Can you give me an
idea of how many containers you're running on the machine and what kind
of workloads they are running?
** Changed in: linux-signed (Ubuntu)
Status: New => Confirmed
** Changed in: linux-signed (Ubuntu)
Assignee:
Please disregard comment #2. These warnings are related to preempt rcu,
which is only used in the lowlatency kernel.
This seems likely to be caused by an unbalanced
rcu_read_lock()/rcu_read_unlock() happening somewhere before the task
schedules.
--
You received this bug notification because you
When you see this in -24, is that still the lowlatency kernel or had you
switched it out for generic like you mentioned in the description?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/
Just to confirm and still seeing this with today's -24 package.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1872964
Title:
Reliable crash in lowlatency kernel with LXD
Status
10 matches
Mail list logo
