CPU /KVM Tainted error causing AP to go down

[jvlarc]

Hey everyone,

 

my unRAID server has been running really strong the past few months but recently I'm running into some issues with the CPU /KVM tainted error recently after my cache drive was full the other day which corrupted my docker img as well. After going on discord and getting some help, I managed to solve my reverse proxy issues, however this tainted error seems very persistent and even took my access point down this morning, AP only worked when I unplugged the LAN. Only realized it as it happened to me a few months prior with bad ram and corrupted BTRFS files, doing a scrub on a few of my BTRFS drives as we speak. Have tried doing a memtest86+, but for whatever reason when in the boot menu to select the memtest86+, the system would reboot.

 

This error seems to only show when I'm running my Windows 10 VM for my wife, which from the start has been constantly stuttering every 20-30 secs where we have an inside joke while listening to Taylor Swift that it was Taylor Twift instead. Have tried applying the MSI Interrupt fix from the start, yet still unable to get it solved.

 

Also I'm getting the error in the last line quite abit too recently where my dynamix system stats seems to have some missing file.

 

another small issue while watching PleX locally on a web browser, it'll show insecure connection, and this has been the case ever since I restarted the whole unRAID install the last time. But plays perfectly fine on local and external clients.

 

Appreciate any help! 

Below are my logs and diagnostic file

Quote

Sep 23 10:03:47 Tower kernel: CPU 0/KVM: page allocation failure: order:4, mode:0xdc0(GFP_KERNEL|__GFP_ZERO), nodemask=(null),cpuset=vcpu0,mems_allowed=0 Sep 23 10:03:47 Tower kernel: CPU: 2 PID: 16938 Comm: CPU 0/KVM Tainted: G U W 5.13.8-Unraid #1 Sep 23 10:03:47 Tower kernel: Call Trace: Sep 23 10:08:00 Tower kernel: CPU 1/KVM: page allocation failure: order:4, mode:0xdc0(GFP_KERNEL|__GFP_ZERO), nodemask=(null),cpuset=vcpu1,mems_allowed=0 Sep 23 10:08:00 Tower kernel: CPU: 3 PID: 16939 Comm: CPU 1/KVM Tainted: G U W 5.13.8-Unraid #1 Sep 23 10:08:00 Tower kernel: Call Trace: Sep 23 10:08:55 Tower kernel: CPU 0/KVM: page allocation failure: order:4, mode:0xdc0(GFP_KERNEL|__GFP_ZERO), nodemask=(null),cpuset=vcpu0,mems_allowed=0 Sep 23 10:08:55 Tower kernel: CPU: 2 PID: 16938 Comm: CPU 0/KVM Tainted: G U W 5.13.8-Unraid #1 Sep 23 10:08:55 Tower kernel: Call Trace: Sep 23 10:11:48 Tower kernel: CPU 1/KVM: page allocation failure: order:4, mode:0xdc0(GFP_KERNEL|__GFP_ZERO), nodemask=(null),cpuset=vcpu1,mems_allowed=0 Sep 23 10:11:48 Tower kernel: CPU: 3 PID: 16939 Comm: CPU 1/KVM Tainted: G U W 5.13.8-Unraid #1 Sep 23 10:11:48 Tower kernel: Call Trace: Sep 23 10:32:14 Tower kernel: CPU 5/KVM: page allocation failure: order:4, mode:0xdc0(GFP_KERNEL|__GFP_ZERO), nodemask=(null),cpuset=vcpu5,mems_allowed=0 Sep 23 10:32:14 Tower kernel: CPU: 7 PID: 16943 Comm: CPU 5/KVM Tainted: G U W 5.13.8-Unraid #1 Sep 23 10:32:14 Tower kernel: Call Trace: Sep 23 10:49:19 Tower kernel: CPU 3/KVM: page allocation failure: order:4, mode:0xdc0(GFP_KERNEL|__GFP_ZERO), nodemask=(null),cpuset=vcpu3,mems_allowed=0 Sep 23 10:49:19 Tower kernel: CPU: 5 PID: 16941 Comm: CPU 3/KVM Tainted: G U W 5.13.8-Unraid #1 Sep 23 10:49:19 Tower kernel: Call Trace: Sep 23 10:52:24 Tower kernel: CPU 5/KVM: page allocation failure: order:4, mode:0xdc0(GFP_KERNEL|__GFP_ZERO), nodemask=(null),cpuset=vcpu5,mems_allowed=0 Sep 23 10:52:24 Tower kernel: CPU: 7 PID: 16943 Comm: CPU 5/KVM Tainted: G U W 5.13.8-Unraid #1 Sep 23 10:52:24 Tower kernel: Call Trace: Sep 23 11:00:01 Tower kernel: mdcmd (41): set md_write_method 1 Sep 23 11:00:01 Tower kernel: Sep 23 11:00:01 Tower kernel: mdcmd (42): set md_write_method auto Sep 23 11:00:01 Tower kernel: Sep 23 11:00:19 Tower kernel: CPU 5/KVM: page allocation failure: order:4, mode:0xdc0(GFP_KERNEL|__GFP_ZERO), nodemask=(null),cpuset=vcpu5,mems_allowed=0 Sep 23 11:00:19 Tower kernel: CPU: 7 PID: 16943 Comm: CPU 5/KVM Tainted: G U W 5.13.8-Unraid #1 Sep 23 11:00:19 Tower kernel: Call Trace: Sep 23 11:02:40 Tower nginx: 2021/09/23 11:02:40 [error] 7009#7009: *62833 open() "/usr/local/emhttp/plugins/dynamix.system.stats/images/sys.png" failed (2: No such file or directory) while sending to client, client: 192.168.70.2, server: XXXXXXXXXXXXXXXXXXXXXXXXXXX.unraid.net, request: "GET /plugins/dynamix.system.stats/images/sys.png HTTP/2.0", host: "XXXXXXXXXXXXXXXXXXXXXXXXXXX.unraid.net", referrer: "https://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.unraid.net/Stats"

Attached is my diagnostics.

 

tower-diagnostics-20210923-1240.zip

Edited September 23, 2021 by jvlarc

[jvlarc]

So I've actually downgraded to 6.9.2 and the VM seems to have improved tremendously. However I'm still getting the CPU */KVM Tainted errors, how should I get it cleared?

[Squid]

6 hours ago, jvlarc said:

Tainted

FYI "tainted" doesn't particularly mean what it implies.

 

Tainted in the linux world simply means that the kernel isn't absolutely 100% stock and has a modification in it.  (Could be a compile flag, or code difference etc).  It's used as a flag to the actual Linux developers that the code isn't exactly what they submitted for inclusion.  Everything in Unraid has the tainted flag.

 

That being said, page allocation errors implies that there isn't enough contiguous memory left in the system to be able to run the VM.

[jvlarc]

On 10/4/2021 at 9:28 PM, Squid said:

FYI "tainted" doesn't particularly mean what it implies.

 

Tainted in the linux world simply means that the kernel isn't absolutely 100% stock and has a modification in it.  (Could be a compile flag, or code difference etc).  It's used as a flag to the actual Linux developers that the code isn't exactly what they submitted for inclusion.  Everything in Unraid has the tainted flag.

 

That being said, page allocation errors implies that there isn't enough contiguous memory left in the system to be able to run the VM.

Hi Squid, 

 

love your apps!

 

Does it mean I'll need to either reduce or increase my memory size for the error to solve this issue? As I swapped out a 16gb for an 8gb RAM stick when I first encountered this error

[Squid]

You need to increase your physical memory or decrease the memory to the VMs