On Sat, Mar 13, 2021 at 03:01:45AM -0500, Michael Grant wrote: > > I'd say it is a Linode problem, unless you run custom kernel modules. > > It looks like a "memory" corruption to me and since it is virtualized > > system, > > you should check if host system is ok. > > Memory in quotes because this issue could be also related to a storage > > sub-system (local or network attached) of the host or VM. > > I'm definitely not running a custom kernel.
You do run non-Debian kernel. It says so in your dmesg: kworker/0:3 Tainted: G B 5.10.13-x86_64-linode141 #1 Reco
