summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com>2020-10-30 16:32:50 +0100
committerGitHub <noreply@github.com>2020-10-30 16:32:50 +0100
commitf794a4f03f76c4de7f2012d09ff65814612a2336 (patch)
treec2ffffb38e10d6c31b0c96fae1da48c77d70f654
parent228396a99dc88fc828f23d4072a46ca8de90282f (diff)
parent0ebee0ce8e86dc327d0e3087271120d196544805 (diff)
downloadpodman-f794a4f03f76c4de7f2012d09ff65814612a2336.tar.gz
podman-f794a4f03f76c4de7f2012d09ff65814612a2336.tar.bz2
podman-f794a4f03f76c4de7f2012d09ff65814612a2336.zip
Merge pull request #8188 from cevich/workaround_agent_stopped_responding
Cirrus: Workaround F32 BFQ Kernel bug
-rwxr-xr-xcontrib/cirrus/setup_environment.sh10
1 files changed, 10 insertions, 0 deletions
diff --git a/contrib/cirrus/setup_environment.sh b/contrib/cirrus/setup_environment.sh
index a3840d7e6..8ccbd95d9 100755
--- a/contrib/cirrus/setup_environment.sh
+++ b/contrib/cirrus/setup_environment.sh
@@ -85,6 +85,16 @@ case "$CG_FS_TYPE" in
*) die_unknown CG_FS_TYPE
esac
+if ((CONTAINER==0)); then # Not yet running inside a container
+ # Discovered reemergence of BFQ scheduler bug in kernel 5.8.12-200
+ # which causes a kernel panic when system is under heavy I/O load.
+ # Previously discovered in F32beta and confirmed fixed. It's been
+ # observed in F31 kernels as well. Deploy workaround for all VMs
+ # to ensure a more stable I/O scheduler (elevator).
+ echo "mq-deadline" > /sys/block/sda/queue/scheduler
+ warn "I/O scheduler: $(cat /sys/block/sda/queue/scheduler)"
+fi
+
# Which distribution are we testing on.
case "$OS_RELEASE_ID" in
ubuntu*) ;;