diff options
| author | Chris Evich <cevich@redhat.com> | 2020-10-29 14:21:04 -0400 |
|---|---|---|
| committer | Chris Evich <cevich@redhat.com> | 2020-10-30 09:15:56 -0400 |
| commit | 0ebee0ce8e86dc327d0e3087271120d196544805 (patch) | |
| tree | a18c4726c7fe4703becac7c77229b7762922801d /contrib | |
| parent | 222d8075ab08265c6dce8cf0f26a60c9afb64705 (diff) | |
| download | podman-0ebee0ce8e86dc327d0e3087271120d196544805.tar.gz podman-0ebee0ce8e86dc327d0e3087271120d196544805.tar.bz2 podman-0ebee0ce8e86dc327d0e3087271120d196544805.zip | |
Cirrus: Workaround F32 BFQ Kernel bug
Signed-off-by: Chris Evich <cevich@redhat.com>
Diffstat (limited to 'contrib')
| -rwxr-xr-x | contrib/cirrus/setup_environment.sh | 10 |
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*) ;; |