On 04.03.20 20:38, Christian Borntraeger wrote: > > > On 04.03.20 20:19, Dietmar Eggemann wrote: >>> I just realized that this system has something special. Some month ago I created 2 slices >>> $ head /etc/systemd/system/*.slice >>> ==> /etc/systemd/system/machine-production.slice <== >>> [Unit] >>> Description=VM production >>> Before=slices.target >>> Wants=machine.slice >>> [Slice] >>> CPUQuota=2000% >>> CPUWeight=1000 >>> >>> ==> /etc/systemd/system/machine-test.slice <== >>> [Unit] >>> Description=VM production >>> Before=slices.target >>> Wants=machine.slice >>> [Slice] >>> CPUQuota=300% >>> CPUWeight=100 >>> >>> >>> And the guests are then put into these slices. that also means that this test will never use more than the 2300%. >>> No matter how much CPUs the system has. >> >> If you could run this debug patch on top of your un-patched kernel, it would tell us which task (in the enqueue case) >> and which taskgroup is causing that. >> >> You could then further dump the appropriate taskgroup directory under the cpu cgroup mountpoint >> (to see e.g. the CFS bandwidth data). >> >> I expect more than one hit since assert_list_leaf_cfs_rq() uses SCHED_WARN_ON, hence WARN_ONCE. > > That was quick. FWIW, I messed up dumping the cgroup mountpoint (since I restarted my guests after this happened). > Will retry. See the dmesg attached. New occurence (with just one extra debug line)