In this new systemd timegraph (systemd-time-graph-2.svg) , at the time khaled.service is run, the scheduler had to changed to [none]:
from rc.local Tue Nov 10 03:39:00 UTC 2020 [mq-deadline] none from myscript.sh Tue Nov 10 03:39:08 UTC 2020 [none] mq-deadline The difference between the first time-graph and the second is that khaled.service was moved to after cloud-config.service has *finished* starting-up. I think this basically confirms that something in cloud-config.service is doing (or triggering somehow) this change. ** Attachment added: "systemd-time-graph-2.svg" https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1903543/+attachment/5432873/+files/something.svg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903543 Title: Block device scheduler should be multiqueue for spinning disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1903543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
