This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1921355
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/1921355
Title:
cgroups related kernel panics
Status in linux package in Ubuntu:
Incomplete
Status in linux-hwe-5.4 package in Ubuntu:
Confirmed
Bug description:
Hi!
Recently (throughout the last 6 months) we've upgraded our hypervisor
compute hosts from ubuntu bionic kernel 4.15.* to ubuntu bionic hwe
kernel 5.4.
This month we noticed that several nodes failed due to bugs in cgroups.
Trace was different almost every time, but it all revolves around cgroups -
either null pointer failures, or panic caught by BUG_ON() macro. Looked like
some cgroup didn't exist anymore but somebody tried to access it, thus causing
kernel panic.
Please find the logs attached.
3 of 4 cases happened after a VM shutdown. We tried to spawn lots of VMs,
load them, shut them down, but didn't manage to reproduce the behavior.
Actually, every case is sort of different - patch kernel versions (5.4.0-42
to 5.4.0-66), uptime vary (from 1 day to ~half a year). There are also lots of
hosts with several months of uptime, no issue with them. Also, on 4.15 we've
never seen this behavior, at all.
That's quite disturbing, as I don't want dozens of VMs crash (due to host
outage) at random times for some vague reason...
I didn't manage to find any related bugs on the bug tracker, thus creating
this one.
I wonder if anybody in the community came across something like that.
Could somebody give an advice how to debug further, or where else to report /
look for a similar the case?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921355/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
