From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 200101] random freeze under load
Date: Sat, 27 Jun 2020 08:21:34 +0000 [thread overview]
Message-ID: <bug-200101-28872-82n499iHoL@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200101-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200101
--- Comment #4 from Garry Filakhtov (filakhtov@gmail.com) ---
Okay, have played a bit further with all of this. I have managed to get freezes
on linux-4.19.120-gentoo as well, after using CPU pinning together with RR
scheduling policy and priority to 1 for all vCPU threads.
After removing the commit 47c61b3955cf712cadfc25635bf9bc174af030ea it seems
like the system is indeed working without freezing. I will continue testing and
updating as I get more information.
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2020-06-27 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-200101-28872@https.bugzilla.kernel.org/>
2020-06-12 6:15 ` [Bug 200101] random freeze under load bugzilla-daemon
2020-06-27 8:21 ` bugzilla-daemon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-200101-28872-82n499iHoL@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox